From: Harry Putnam <reader@newsguy.com>
Subject: Reports of corrupt mail on mail fetch
Date: Thu, 10 Jul 2003 09:00:13 -0700 [thread overview]
Message-ID: <m365ma1ieq.fsf@newsguy.com> (raw)
Running a fairly recent v5.10.3.
Lately I've been getting a message during mail/news fetch of corrupt
unrecognized mail format:
nnml: Reading incoming mail from directory...
Mail source (directory :path /home/reader/spool/ :suffix .in) error (Error, unknown mail format! (Possibly corrupted buffer ` *nnmail incoming*'.)). Continue? (y or n)
Doesn't occur on every fetch, or even most. But still fairly often.
Checking ~/.emacs-mail-crashbox*, there will be a file with 1-5 bytes
reported as size. 1-5 newlines inside. Deleting that file cures the
problem for a while.
The report doesn't seem to indicate what actual spool is involved.
Unless it means the Inc* file which I have turned off, and have had
it off for a very long time. Maybe I should turn it back on and see
if something unusual is coming down the pipe.
I thought maybe a renegade procmail recipe might do this. I change
procmailrc very often. But reviewing verbose procmail log output
I noticed nothing to catch my attention.
Is there some way I can force gnus to give more complete info? Or in
some way make a connection between actual incoming mail and those
newlines?
I guess setting debug on error until it happens again might get a
backtrace, so trying that for now.
reply other threads:[~2003-07-10 16:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m365ma1ieq.fsf@newsguy.com \
--to=reader@newsguy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).