6 messages in net.sourceforge.lists.courier-maildrop[maildropl] Re: maildrop 1.3.8 still ...
FromSent OnAttachments
Oliver CrowApr 3, 2002 7:35 pm 
Sam VarshavchikApr 3, 2002 7:56 pm 
David LaightApr 4, 2002 3:48 am 
Sam VarshavchikApr 4, 2002 6:11 am 
David LaightApr 4, 2002 2:20 pm 
Oliver CrowApr 4, 2002 3:58 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[maildropl] Re: maildrop 1.3.8 still adds a blank line before generated 'From 'Actions...
From:Oliver Crow (ocr@simplexity.net)
Date:Apr 4, 2002 3:58:19 pm
List:net.sourceforge.lists.courier-maildrop

Sam Varshavchik writes:

David Laight writes:

Seems to be that being unable to use a reasonably common MUA (mutt) is a serious bug.

Mbox files can contain an initial empty line, and mutt should be able to handle that.

I had a look to see if I could find a description of the mbox format. I was not able to find anything authoritative. However this man page indicates that an mbox message *begins* with a From_ line and *ends* with a newline. http://www.qmail.org/qmail-manual-html/man5/mbox.html

This article supports that interpretation. http://email.about.com/library/weekly/aa111300a.htm

The standard FreeBSD local mail delivery program mail.local does not write an initial newline character and does write one at the end of the message.

It seems that both mutt and qpopper have a problem with the initital blank line. Is there any particular reason to write an initial blank line, instead of a terminal one?

Oliver

The problem reported in the following message still exists in maildrop version 1.3.8

http://www.geocrawler.com/mail/msg.php3?msg_id=7814768&list=9569

The original poster reported the problem that "From " headers generated by maildrop 1.3.7 are preceeded by a blank line, which causes some MUA programs to complain. I can confirm this behavior in version 1.3.7 running under FreeBSD. For example it causes the POP daemon qpopper to fail to read affected mailboxes.

The patch provided by the original poster does indeed appear to fix the problem. It has not been applied in version 1.3.8 or to the current CVS source.