----- Original Message ----- From: "Randall Gellens" <[EMAIL PROTECTED]> To: "Michael Kolos" <[EMAIL PROTECTED]>; "Clifton Royston" <[EMAIL PROTECTED]> Cc: "Subscribers of Qpopper" <[EMAIL PROTECTED]> Sent: Thursday, October 11, 2001 7:59 PM Subject: Re: Implementing user quotas / Expiring Email
> At 10:52 AM -0400 10/11/01, Michael Kolos wrote: > >It is not such a rare occurance. > >I have had this problem for a while - usually we get about one user per week > >where I have to restore their mail spool from the .pop file. > > When Qpopper starts it checks for leftover mail in the temp drop; it > should be necessary to manually move the mail over. > Of course qpopper can't put the spool back from the temp drop, because the temp drop is over quota for the user. > > In my case, > >their spool file ends up with a bunch of characters at the beginning, making > >it even bigger. > > That indicates something is wrong. The temp spool should not be > getting corrupted. Are you sure you're using the latest version of > Qpopper? I think there was an early version, perhaps 2.53, that > could create a large temp spool full of junk under some circumstances. > It's not the temp spool that's having the problems. That's the copy that's not on a quota-enabled partition. It's the actual mail-spool that appears to have this problem. We are running 4.0.3 in standalone. Users only access the mail via pop, and procmail delivers incoming mail. I may have eggagerated the frequency that this happens. We've got about 10,000 mail boxes and this may happen a few times a month at most, probably once or twice. I haven't been able to figure out the source, but this idea of adding the X-UIDL headers could explain it. I don't see why the spool file gets corrupted as a result, however, unless qpopper meets with something weird when it goes overquota. if I turn on no-status, it basically means that no X-UIDL headers are added, and how exactly does that affect performance? Thanks, Michael
