Re: allow initial blank lines in local mailboxes
On 13Oct2010 11:45, David Champion <dgc@xxxxxxxxxxxx> wrote:
| # HG changeset patch
| # User David Champion <dgc@xxxxxxxxxxxx>
| # Date 1286988263 18000
| # Branch HEAD
| # Node ID 95302d58ea75b010c99ed42b651e9d143b10e20e
| # Parent 0b159a8327b751def2ad8f0a89957e2288fe2abb
| allow initial blank lines in local mailboxes
|
| Some mailbox-creation tools erroneously append a blank line to a file
| before appending a UNIXv7-format mail message,
Including at least one script I've written myself recently:-(
| resulting in mailboxes
| that are intended to me valid "mbox" folders but are not. Notably old
| versions of Mailman do this, making archive files that cannot be read by
| mutt.
|
| This patch causes mutt to skip leading NLs and CRs when detecting magic.
Does it let mutt read the folder as well? I imagine so or you'd not have
found it useful, but...
On the topic of bad mbox files, my broken script mentioned above was
written because procmail does something strange for me. When I break my
mail filing rules the email all flows through to my $MAIL spool file,
which of course should be in mbox format. But it imoted the From_ line!
Exteremely annoying and damaging.
Does anyone know what might make procmail do this?
Cheers,
--
Cameron Simpson <cs@xxxxxxxxxx> DoD#743
http://www.cskk.ezoshosting.com/cs/
Stop assuming that systems are secure unless demonstrated insecure;
start assuming that systems are insecure unless designed securely.
- Bruce Schneier