----- Original Message ----- From: "Michael Kolos" <[EMAIL PROTECTED]> To: "Subscribers of Qpopper" <[EMAIL PROTECTED]> Sent: Friday, August 09, 2002 9:17 AM Subject: Re: Filesystem quotas
> What is this "boundary condition" and when does it come up? > We have the temp dir on a non-quota filesystem, and on the spool dir users > have a hard quota 100k more than the soft quota. > Yet we still occasionnally end up with a user with a corrupted mail spool > because somehow it went over quota, and when qpopper copies the spool back, > it gets corrupted. > I have tried turning off the X-UIDL writing, but that hasn't helped. Imagine a user with a 5120k hard quota, and 4.9MB in their mailfile. QPopper copies that mailfile over to the non-quota filesystem to POP it out, and while the user is checking his/her email (and apparently NOT deleting it from the server) they receive a 200k email. Now there's 200k in their mailfile, only 4.8MB available. The POP session is over and QPopper copies the .pop file back into the mail spool. 0.2MB + 4.9MB = 5.1MB > 5.0MB: the user is now over quota, and the last 100k or so is lost. That was my concern. But frankly, I don't like my users leaving their mail on the server. But that's not an entirely practical requirement when some people have multiple machines/people checking the same box (which I recommend multiple boxes with aliases) or using webmail as their primary or only mail viewing agent. But, that's what happens. I haven't decided if it would be nicer to have quota systems installed in the local mail delivery agent or not, as it would require a separate database of user quotas. I think procmail can do that, but I'm only beginning to learn about it. -- Alan W. Rateliff, II
