On Wed, Jan 30, 2002 at 09:21:18AM -0600, Dan Yost wrote: > Hello everyone, > > Please forgive me if this question has already been answered, and feel free > to point me to the appropriate place for that answer--I've searched the > newsgroups, the web, Qualcomm's site, and just about everywhere else, but > all I can find is the same *question* with no acceptable *answer*...so here > it goes. > > I'm running Red Hat 7.0 and Qpopper 3.1. I have disk quotas turned on for > my POP users. Yesterday, I noticed that one user was getting an error > message in the maillog: > > ---snip--- > mypopuser at mydomain.com (x.x.x.x): -ERR [SYS/TEMP] Unable to copy mail > spool file, quota exceeded (122) > > > This definitely caught my attention because I just finished writing a whole > utility to send warnings when quota soft limits are breached, and I should > receive a copy of the warnings. I checked, and sure enough, the soft limit > was *almost* reached but not yet. After searching the Net, it seems clear > that this has to do with Qpopper doing a chown while copying the mail spool > file, and I've learned that soft limit grace periods are [somehow!] > ignored. Hence, the operation fails immediately instead of initiating a > grace period. This is definitely unacceptable.
Good guess, but not right. Remember, quota enforcement is happening "down" in the filesystem kernel level, where qpopper has no insight or control over what is happening. The problem is most likely that your hard limit is less than 2x the soft limit, so when qpopper needs to recopy the file to update it (note it actually says "copy mail spool file" in the message) there is not enough space to do so before it runs into the hard limit. The only solutions I've > seen put forth are to turn off quotas or put the spool temp files in a > partition that is not under quota restrictions. This is not entirely > unreasonable, but it is not possible right now in my setup. You can fiddle with the quota limits on your mail partition such that the hard limit is set slightly more than 2x the soft limit, and that will *sort of* work. I say "sort of", because the user can still end up running their mailbox up over the soft limit (due to that grace period) and again end up unable to pop their mail. The only really good way is to put the temp drop files on a separate partition with no quotas or with an independent quota from the mailspool partition. I did that last year as part of our long-delayed mail quota implementation and it has been working fine. HTH, -- Clifton -- Clifton Royston -- LavaNet Systems Architect -- [EMAIL PROTECTED] WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
