David Champion wrote:
* On 2005.05.25, in <[EMAIL PROTECTED]>,
* "Ken A" <[EMAIL PROTECTED]> wrote:
But, if I put the temp drop on the same filesystem as the mail spool,
users can't check mail when they hit their hard quota. :-(
I'd like to have the temp drop on a different partition so quotas work,
but still use fast-update, since I'd like to keep disk i/o down as much
as possible. I'd appreciate any ideas.
Quotas have always been a problem for us. There have been enough issues
that we basically couldn't't use filesystem-based quotas, and that's
one of the inspirations for the "happymail" extensions we developed.
It's not a direct answer to you situation, but it obliquely provides a
workaround for I/O issues, if not to storage constraints.
http://home.uchicago.edu/~dgc/sw/qpopper/index.html
Disclaimer: we don't really use this anymore, as we've been hauled
kicking and screaming by upper management into carefree turnkey mail
appliance blissful all day long land. So I don't know how well this
works with current qpoppers -- it was developed on 4.0.5, and I don't
really maintain it anymore, since I can't defend that to mgmt and have
enough other projects for my free time. (If anyone who uses it is
interested in taking over, please let me know.)
Wow. That's very cool. I've been looking for a way to stop those 'check
every 1 minute' pop users. I think our support dept would be overwhelmed
with calls if users got "Please wait at least x minutes between checks".
I'd rather it just returned a fake "no new messages" response for x
minutes.
Thanks,
Ken Anderson
Pacific.Net
