Re: [Mailman-Users] Subject Lines Wrapped After Commas, (LikeThis?)
Mike Ewall wrote:
Thanks for clarifying the terms for me and for explaining how the subject line behavior works. Unfortunately, this isn't the first "feature" of Mailman that I see as a bug. I don't know about other email readers, but in Eudora, only the part of the subject before the fold shows up in the table of contents, making this feature rather annoying.
It is the underlying Python email library that folds the Subject: header and determines where to fold. You could argue that it shouldn't give preference to foldable whitespace following a comma or semicolon in the unencoded value of the subject as these aren't syntactically significant in a subject, and that may be valid, but it is still folding in a standards compliant manner.
I would argue that Eudora is much more at fault here for not unfolding the subject before presenting it in its TOC.
What does Eudora do with RFC 2047 encoded Subject: headers such as the example in section 8 of the RFC (http://www.faqs.org/rfcs/rfc2047.html>.
I'd very much prefer to have things folded without regard to commas, as in your examples below.
If Eudora would unfold the header before putting as much as fits into the subject field of its TOC, this wouldn't be an issue. From my point of view, you're asking that Mailman, which is already standards compliant, alter its behavior to compensate for a non-compliant MUA.
Is there any way to configure Mailman not to fold at higher-level syntactic breaks?
No. I think that this would require modifying the Header module in the Python email library.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 5/21/07, Mark Sapiro wrote:
I would argue that Eudora is much more at fault here for not unfolding the subject before presenting it in its TOC.
I use Eudora myself. I don't see any such problems.
If Eudora would unfold the header before putting as much as fits into the subject field of its TOC, this wouldn't be an issue. From my point of view, you're asking that Mailman, which is already standards compliant, alter its behavior to compensate for a non-compliant MUA.
Eudora won't un-fold a subject line that has already been folded, regardless of how wide you make your window. That's a Eudora problem, and there's nothing that anyone anywhere else in the Universe can do to fix it.
Eudora is going away. Qualcomm has decided to kill it. They're supposedly working on importing most of the most important features into Thunderbird, but that project is apparently a very long way away from fruition. I'm going to have to find a new MUA pretty soon, and it most likely won't be Thunderbird, and it certainly won't be Thundora. Pretty much all other Eudora users are in that same boat.
-- Brad Knowles <brad@shub-internet.org>, Consultant & Author LinkedIn Profile: <http://tinyurl.com/y8kpxu> Slides from Invited Talks: <http://tinyurl.com/tj6q4>
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
On 5/21/07 4:54 PM, "Mark Sapiro" <msapiro@value.net> wrote:
I would argue that Eudora is much more at fault here
Eudora was also the primary source of resistance to the List-* headers, with its interesting habit of displaying all headers except those in its list of "boring" headers. Manipulating that list, in the time frame in which the List-* headers appeared, was not easy for the users on any platform (less hard on Mac than on Windows).
On the screen size I had at the time they appeared, the List-* headers caused me to have to scroll to see the useful part of any mailing list message longer than a couple of lines.
(My usage of Eudora is down to sending test messages and sending some template-based messages. And searching messages older than a half decade or so.)
--John
participants (3)
-
Brad Knowles -
John W. Baxter -
Mark Sapiro