Matt,
what OS are you running? Yes, I have a process too, and this one
doesn't lose mail :-).
head -1 /var/mail/user | strings > /var/mail/user.tmp
wc -l /var/mail/user (subtract 1)
tail -(above value) >> /var/mail/user.tmp
cp /var/mail/user.tmp /var/mail/user
One thing that is strange is that the quota command does not show the size
of the corrupt mailbox, but what the good mailbox size was. This puzzles
me because qpopper is not suid so the user really was writing the data
when the failure occured. Anyone have any suggestions on fixing this? Glad
it's not just me.
Regards,
Chris
On Wed, 5 Mar 2003, Matt Garretson wrote:
> Chris Miller wrote:
> > I've been having problems with qpopper corrupting mailboxes when a
> > user is at their disk quota. Here's the background;
>
>
> Yes, this happens to us on a weekly basis, too. I find that
> the mailbox can be pretty much reconstructed using a combination
> of the temp pop drop and part of the corrupted spool file. If
> you want, i can supply the exact steps i use to do this. There's
> a chance that a message or two might get lost in this process, but
> i don't sweat it too much anymore. Though it would be nice if
> the problem never came up in the first place.
>
> -Matt
>
