simon.king@??? said:
} the problem is caused by the way the maildir format stores messages to
} maintain backward compatibility with the berkley format, for example
} the berkley mailbox uses an initial From line to separate individual
} emails, for example...
} >From owen@??? Fri Jun 19 13:03:45 1998 X-UIDL:
} f7731238b0cf0767b4e0d1db55502f39 Return-path: <owen@???> etc
} etc
} the Maildir format preserves this part of the header, but as each
} mail is now an individual file it doesnt seem to be needed.
} We tested delivering to different smtp apps with and without this
} extra header line, Sendmail and Agent didnt seem to worry about it and
} mails worked ok, Exim seems to translate this extra line as being the
} start of the message body, and so it sends the actual header as part
} of the message body, the general opinion was that Exim was
} interpreting the rfc's more strictly.
Exim is correct here. You should *never* have the From_ line in the
header - its (part of) the envelope.
The attached code appears to be for the UW Imap daemon.
Reading the exim documentation would show that for exim's local maildir
delivery you need to set a few config options on the transport to ensure
fully correct behaviour, in particular:-
no_from_hack,
prefix = "X-From_: ${if def:return_path{$return_path}\
{MAILER-DAEMON}} ${tod_bsdinbox}\n",
suffix = ""
Basically the prefix and suffix should be set to empty strings and body
escaping of From_ lines should be switched off. We actually set the
prefix to be an X-From_: header as is generated by some pop daemons
(cucipop) because some of our customers like to be able to filter on that.
Please could bug reports be a little better focused - this one was hard
work.
Nigel.
--
[ Nigel.Metheringham@??? - Systems Software Engineer ]
[ Tel : +44 113 207 6112 Fax : +44 113 234 6065 ]
[ Real life is but a pale imitation of a Dilbert strip ]
--
*** Exim information can be found at
http://www.exim.org/ ***
