Lindsay Haisley writes:
I have one list subscriber here who is having some difficulty, probably with an errant spam filter at his ISP, and headers are being improperly modified somewhere, just above a quoted Return-Path header added by courier (">Return-Path:"). This doesn't seem to cause a problem with any other list subscribers, but I did a bit of checking up on the issue.
This quote is added by code in submit.C. Is this supported by RFC? According to RFC 2822 (3.6.6) RFC-legal headers in an email which is
2.2. Header Fields
Header fields are lines composed of a field name, followed by a colon
(":"), followed by a field body, and terminated by CRLF. A field
name MUST be composed of printable US-ASCII characters (i.e.,
characters that have values between 33 and 126, inclusive), except
colon.
The only character prohibited in header names is the colon.
Still, due to client breakage, I changed the code recently to use "Old-Return-Path".
pgpq2SSiiCO6z.pgp
Description: PGP signature
