bug demonstration 12345678911234567892123456789312345678941234567895123456789612345678971234567898112345678911234567892123456789112345678911234567892123456789 more text
If this works as expected, all the headers below the subject line should end up in the mail body.
I've been tracking this bug for a while, apparently mailman's header parsing chokes when you have a header that contains more than 80 (maybe 100?) characters in a row without a space.
This breaks horribly when you run spamassassin, due to headers like: X-Spam-Status: No, hits=2.0 required=7.0 tests=SUBJ_ENDS_IN_Q_MARK,TO_LOCALPART_EQ_REAL,X_NOT_PRESENT,RCVD_IN_VADUL,X_RCVD_IN_DUL_FH version=2.21
But it also breaks because outlook has a bug where Message-IDs listed in the References header aren't always separated by spaces.
I'm hoping that Barry or someone else can nail this quicker than I can find out which part of mailman may even be responsible for that (I'm still quite busy hacking on exim and spamassassin for sf.net right now)
Marc
Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key
On Sat, Jun 01, 2002 at 11:54:42PM -0700, Marc MERLIN wrote:
If this works as expected, all the headers below the subject line should end up in the mail body.
Son of a...
When I sent it to my mailman lists, it arrives in my mailbox as:
(...)
From: Marc MERLIN <marc_news@vasoftware.com>
To: mailman-developers@python.org
Message-ID: <20020602065442.GA12014@merlins.org>
Mail-Followup-To: mailman-developers@python.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
X-Sysadmin: BOFH
X-URL: http://marc.merlins.org/
X-Operating-System: Proudly running Linux
2.4.14-lvm1.0.1rc4-ext3-0.9.15-grsec-1.8.8-servers11/Debian woody
X-Mailer: Some Outlooks can't quote properly without this header
X-Mailman-Approved-At: Sun, 02 Jun 2002 07:02:13 -0000
Subject: [Test]
bug demonstration
12345678911234567892123456789312345678941234567895123456789612345678971234567898
112345678911234567892123456789112345678911234567892123456789
more text
X-BeenThere: test@list.merlins.org
X-Mailman-Version: 2.1b2+
Precedence: bulk
List-Help: <mailto:test-request@list.merlins.org?subject=help>
List-Archive: <http://lists.merlins.org/archives/test>
List-Unsubscribe: <http://www.merlins.org/lists/listinfo/test>,
<mailto:test-request@list.merlins.org?subject=unsubscribe>
List-Subscribe: <http://www.merlins.org/lists/listinfo/test>,
<mailto:test-request@list.merlins.org?subject=subscribe>
List-Post: <mailto:test@list.merlins.org>
List-Id: What could a test list be for? <test.list.merlins.org>
Sender: test-bounces+marc=merlins.org@list.merlins.org
Errors-To: test-bounces+marc=merlins.org@list.merlins.org
If this works as expected, all the headers below the subject line should
end up in the mail body.
(...)
I don't get it. I just synced my tree, it still does it, and on two different machines.
Can you guys try this subject line on your mm 2.1b2 servers? (it works with mailman 2.0)
Marc
Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key
At 11:54 PM 6/1/02 -0700, Marc MERLIN wrote:
If this works as expected, all the headers below the subject line should end up in the mail body.
I've been tracking this bug for a while, apparently mailman's header parsing chokes when you have a header that contains more than 80 (maybe 100?) characters in a row without a space.
Refer to the notes that I posted off and on over the last month, including a sample header that triggers the effect. I finally caught a header *before* it happened by being cc'd on a note that coincidentally triggered it, and posted it, and Barry confirmed he could replicate it.
What little time I've had to look at it has left me convinced it's email that's doing it...
Unfortunately, while I would normally have been trying to fix this, rather than just report it and wash my hands of it, I've recently been rendered functionally unable to do much of anything at work. Thanks to excellent and far sighted scheduling on the part of the upper brass, my #1 priority is to pack and move my office into storage. In about a month the bid on our new office space should go out, and the most forgiving estimates show us getting a place to sit down again and set up shop possibly as early as christmas...
On Sun, Jun 02, 2002 at 05:35:07PM -0400, Ron Jarrell wrote:
It's not just subjects that trigger it - I posted a X-Face header two weeks
I'm very aware of that, my initial post mentionned the X-Spam header from SA, and reference headers from buggy outlooks that forget to put a space between message-Ids in reference lines
On Sun, Jun 02, 2002 at 05:33:57PM -0400, Ron Jarrell wrote:
At 12:16 AM 6/2/02 -0700, Marc MERLIN wrote:
Ahah, and now it barfs on python.org too.
I don't get this bug, I really don't...
Yea. It's not simple line length. It also appears to really need a continuation header to trigger; I think it happened after you replied because *now*, thanks to the reformatting that went on on it's way into the pickle, it had continuation lines in it.
Mmh, that would make sense.
I still think it's email doing it - the header parser likes to unwrap lines with nl's, and rewrap them later, and I think it's getting confused and kicking out an extra NL.
Yep.
On Sun, Jun 02, 2002 at 05:30:30PM -0400, Ron Jarrell wrote:
Refer to the notes that I posted off and on over the last month, including a sample header that triggers the effect.
Actually I posted one too :-)
I finally caught a header *before* it happened by being cc'd on a note
I ended up sending my list mail to an alias saved on disk so that I could see the mail before and after mm.
Marc
Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key
On Sun, 2 Jun 2002 14:44:58 -0700, Marc MERLIN wrote:
On Sun, Jun 02, 2002 at 05:35:07PM -0400, Ron Jarrell wrote:
It's not just subjects that trigger it - I posted a X-Face header two weeks
I'm very aware of that, my initial post mentionned the X-Spam header from SA, and reference headers from buggy outlooks that forget to put a space between message-Ids in reference lines
It happened to me today. A message from a Mailman 2.0.11 mailing list, created by Mutt/1.2.5.1i.
The References: field had 5 message-ids separated by spaces only, making the line 254 characters long. The next line was a blank line (in which a Status field had been added), pushing the rest of the header info into the body (the mailing list info, which is why my filters could not sort the message).
I thought this problem was with my POP3 mailbox server I was using until the test message came through on this list.
-Paul
"RJ" == Ron Jarrell <jarrell@vt.edu> writes:
RJ> What little time I've had to look at it has left me convinced
RJ> it's email that's doing it...I suspect this as well. I'm way too busy to spend a lot of time on this right now (I'm closing on a new house tomorrow), but it would be great if someone could checkout the current cvs of the email (mimelib) package and try it with the current cvs of MM2.1. I've got no substantive unchecked in stuff, so if it doesn't work with this combination, then the bug's still lurking in there.
-Barry
participants (4)
-
barry＠zope.com -
Marc MERLIN -
Paul Dickson -
Ron Jarrell