> > > > > > > > I am using Linux 2.0.18 on the mail server, and POP3D.
> >
> > Dump the pine pop3 server that comes with Slackware. Get qpopper off
> > ftp://ftp.qualcomm.com/quest/unix/servers/popper
>
> I got popper, and it didn't work under heavy loads. It corrupted
> many peoples mail files with junk at the top, and bad snmp headers
> in some mail files. This never happened until I put popper in.
> I had to take it out. But it did stop the /tmp/pop*.
I had both problems - qpopper corrupting files and Netscape causing left files
in /tmp with the standard Linux in.popd. (qpopper's locking is/was obviously
not compatible with sendmail's).
I found that the standard Linux in.popd was getting a signal (SIGPIPE) that
it wasn't expecting when the customer aborted his Netscape download of a
large file (wasn't expecting a > 1 Meg file, I guess). This signal causes
the daemon to exit unexpectedly. (Why this signal is generated, I didn't
explore too far).
I put in a fix as well as some other mods - you can get it and take a look in
ftp://ftp.scott.net/pub/linux/mail
It has a crude/short README.linux that I stuck my change notes in.
There are still, rarely, large files left, but this fixes the main problem.
Freely use at your own risk! :) Of course, all standard disclaimers apply
as to fitness for a particular purpose, etc...
Oh... anyone know why mail starts duplicating itself (same situation - user's
using Netscape, etc...). Different problem, but is triggered by a large mail
message and then usually causes the above problem. Man, I hate that Netscape
POP implementation.
Later!
Derric
-- Derric Scott Scott Network Services, Inc. P. O. Box 361353 derric@scott.net (205)987-5889 Birmingham, AL 35236