procmail
[Top] [All Lists]

Re: NULLs -- LOST EMAIL

1997-02-18 23:01:10
Responding To:  Philip Guenther <guenther(_at_)gac(_dot_)edu>
Original Date:  Tue, 18 Feb 1997 23:51:05 -0600
Message-ID:     <199702190551(_dot_)XAA29084(_at_)solen(_dot_)gac(_dot_)edu>

Actually, if it is an interaction with your mailreader, it is
mostly likely to happen when you _finish_ reading mail and your
mail reader is rewriting the mailspool to reflect what you deleted
from it. What mail program do you use?  How old/what version is it?

It is the standard Mail.app that comes with NeXTStep version 3.3

When I tell it to fetch the mail, it copies the entire spoolfile  
and leaves a size-zero file at /usr/spool/mail/luomat

Again, until today this never had any interference with my mail  
spool.  Usually it is the logfile which is corrupted, which is  
annoying but I can survive that.  Today was the first time that mail  
to my mailspool was lost (ie came in as NULLs).  The very weird  
thing was that there were 3 messages and the first one was OK and  
the second two were the ones which got lost/converted to NULLs



You may have nailed the problem. This is very sporadic, so I can
only guess that the problem is intermittent, but for the life of
me I can't find any common thread that might be the problem.

The final possibility is that some other program is writing to your
spool. You don't have some wonky version of the old /bin/mail lying
around that a shell script out of the past could be calling
directly?

The only time I use /usr/ucb/Mail is when I am sending a message such as

echo test | Mail -s subject whoever(_at_)wherever(_dot_)com

TjL




-- 
Tj Luoma (luomat(_at_)peak(_dot_)org) 
If you have a web page about NeXTStep|OpenStep, email me the URL!

EMAIL ADDRESS: Please use the PEAK address and not the NERC one

<Prev in Thread] Current Thread [Next in Thread>