On 01Aug2014 07:51, Ulrich Lauther <ulrich.laut...@t-online.de> wrote:
On Thu, Jul 31, 2014 at 09:45:15PM -0400, Jon LaBadie wrote:
Do you have a remote client getting mail from that
mailbox which isn't configured to keep the mail on
the server?
no, I just retrieve mail from two providers using
/usr/bin/fetchmail -a -U -d 30 -L /var/log/fetchmail.log \
--auth password \
-m '/usr/bin/procmail -d %T'
procmail stores into /var/mail/<user> and the only other program
that - to my knowledge - accesses that file is mutt.
To prevent further losses, I now added a .procmailrc requesting
procmail to make a copy into another file.
I fetch my email like you (but using getmail) and deliver it to a mail folder
literally named "spool" in with my regular mail folders. This keeps it away
from the local mail spool, which can be subject to locking issues (never the
same on all systems:-) and special ownerships (eg group writable by the local
mail system).
Some things to check: is the freshly truncated mail spool the same file as
before you started mutt? When you start mutt, is the mail folder empty
immediately or only after you close mutt? Might there be some race condition
between mutt's access and some other process (though I imagine you've
considered that). Does the local mail system deliver to this spool file, or is
it only procmail?
Cheers,
Cameron Simpson <c...@zip.com.au>
The criterion of truth is that it works even if nobody is prepared to
acknowledge it. - Ludwig von Mises
