-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 21, 2007, at 11:04 PM, Stephen J. Turnbull wrote:
I would argue that Mailman's algorithm is bogus, as it violates POLA.
At the very least the subject header should be presumed to be prose to
be broken into approximately equal lines.
I
Barry Warsaw writes:
I agree that the current state isn't correct, but the right place to
fix this is in the email package, so the discussion really should be
moved to Python's email-sig.
I thought about that ... but I certainly hope that people who have
opinions about this will join,
On 5/22/07, Stephen J. Turnbull wrote:
I thought about that ... but I certainly hope that people who have
opinions about this will join, because this is not a standards issue
at root. It's about palliative care for those with sick MUAs.wink
So what are the symptoms we need to palliate?
Brad Knowles writes:
The problem is that the people who can fix this problem are over on
the list that Barry identified. Any discussion anywhere else is not
likely to go anywhere, at least not as far as Python Mailman are
concerned.
So, get your experts to go have the
I've noticed that on several Mailman lists I'm running, subject lines
sometimes get chopped after commas or semicolons. This doesn't
always happen, though. It's not just a matter of things being
chopped after the 78-or-so chars, either. Sometimes, it's after a single word.
Below are
Mike Ewall wrote:
I've noticed that on several Mailman lists I'm running, subject lines
sometimes get chopped after commas or semicolons.
Chopped seems to be the wrong term. Long subjects aren't chopped;
they are folded. See sec. 2.2.3 of RFC 2822
http://www.faqs.org/rfcs/rfc2822.html for an
Mark Sapiro writes:
case, it is done by the underlying Python email library, and all three
of the above folded subjects should unfold to essentially the same
thing (i.e., the MUA should remove the inserted crlftab)
AFAIK the standard implies but does not say that a single CRLF is to
be
