convert_html_to_plaintext strips text from hotmail

Bug #266184 reported by Kalvos
2
Affects Status Importance Assigned to Milestone
GNU Mailman
New
Medium
Unassigned

Bug Description

Mailman version 2.1.5 installed on FreeBSD at pair
Networks.

I use the web configuration of mailman. It is set up
with convert_html_to_plaintext enabled.

Recent email via Hotmail has been coming in with no
body, even though the original email has text. The text
is present, and although ugly, the code looks average
for HTML mail.

The actual original email content (without headers) is
pasted below. No text is passed through Mailman.

You can see this archive at
 http://five.pairlist.net/pipermail/coco/
and the result in this message:
 http://five.pairlist.net/pipermail/coco/2005-January/012347.html

Any advice is appreciated if this is not a bug.

<html><div style='background-color:'><DIV class=RTE>
<P>OK, this is the hotmail
test.<BR>_Glen<BR><BR></P></DIV>>
<DIV></DIV>>
<DIV></DIV>>OK, the next message from me will come
from hotmail, as a
test.
<DIV></DIV>>-Glen
<DIV></DIV>> > >
<DIV></DIV>> > Well, the thing to do is, now that
we've got a
clue, go back to the
<DIV></DIV>> > original email agent and make a
couple of test
posts, & we'll see
<DIV></DIV>>who
<DIV></DIV>> > gets what now that we know to look
for it.
<DIV></DIV>>
<DIV></DIV>> > >>
<DIV></DIV>> > >> > -- John.
<DIV></DIV>> > >
<DIV></DIV>> > >Brought to you by the 6809,
the 6803 and their
cousins!
<DIV></DIV>> > >Yahoo! Groups Links
<DIV></DIV>> > >
<DIV></DIV>> > >
<DIV></DIV>> > >
<DIV></DIV>> >
<DIV></DIV>> > --
<DIV></DIV>> > Cheers, Gene
<DIV></DIV>> > "There are four boxes to be used
in defense of
liberty:
<DIV></DIV>> >&nbsp;&nbsp;soap, ballot, jury, and
ammo. Please use
in that order."
<DIV></DIV>> > -Ed Howdershelt (Author)
<DIV></DIV>> > 99.32% setiathome rank, not too
shabby for a WV
hillbilly
<DIV></DIV>> > Yahoo.com attorneys please note,
additions to this
message
<DIV></DIV>> > by Gene Heskett are:
<DIV></DIV>> > Copyright 2005 by Maurice Eugene
Heskett, all
rights reserved.
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>Brought to you by the 6809, the 6803 and
their cousins!
<DIV></DIV>>Yahoo! Groups Links
<DIV></DIV>>
<DIV></DIV>><*> To visit your group on the
web, go to:
<DIV></DIV>>&nbsp;&nbsp;&nbsp;&nbsp;
http://groups.yahoo.com/group/ColorComputer/
<DIV></DIV>>
<DIV></DIV>><*> To unsubscribe from this
group, send an email
to:
<DIV></DIV>>&nbsp;&nbsp;&nbsp;&nbsp;
<email address hidden>
<DIV></DIV>>
<DIV></DIV>><*> Your use of Yahoo! Groups is
subject to:
<DIV></DIV>>&nbsp;&nbsp;&nbsp;&nbsp;
http://docs.yahoo.com/info/terms/
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV></div></html>

[http://sourceforge.net/tracker/index.php?func=detail&aid=1108814&group_id=103&atid=100103]

Revision history for this message
Shub-users (shub-users) wrote :

It was hard to find examples of what you were talking about. Can I
assume that you mean messages like <http://five.pairlist.net/pipermail/
coco/2005-January/012348.html>?

In this case, what we need to do is to see the original, unedited, version

of the message as it was submitted to Mailman, so that we can try to
figure out what went wrong and why it was stripped to be "blank" but
then submitted to the system.

This may require that someone subscribe to Hotmail and send some test
messages, both directly to another account as well as to the mailing list,

so that we can see both the edited and the unedited versions of the
message.

Another problem is that this issue may be specific to the configurations
of particular people using Hotmail, and it may be difficult to find out
what options they have set/changed which result in this kind of
behaviour.

Revision history for this message
Kalvos (kalvos) wrote :

Hello,

Thanks for the response.

In my original post, there was a link the defectively
received message, and it is just like the one you found.

The other message was as sent through Yahoo and received by
Yahoo list members -- the content is pasted above. According
to the author, it is what he sent.

Pasted above is exactly what would have been received by
Mailman. The Yahoo Groups list is a member of our list (with
dupes turned off) so both groups can share posts.

Dennis

Revision history for this message
Shub-users (shub-users) wrote :

Pasting the content of the message body is not useful. There is MIME
structure outside of the message body that is not included, and it is this

MIME structure information that we need in order to find out what has
happened.

This is why I said that we needed to be able to look at the *COMPLETE*
message contents, both before and after processing by Mailman.

You can't just cut-n-paste the message body.

Revision history for this message
Kalvos (kalvos) wrote :
Download full text (5.5 KiB)

Hi,

Thanks again. I'm just a list administrator, so I need my
hand held.

The list members have been warned off HTML posting in the
meantime, so these are the only headers I've got. If they
don't help, I'll wait until we get another blank email with
a Hotmail return address and try to trace it back to the
original submission.

Here is the header of the original email (as sent to me by
another list member) before it goes from Yahoo Groups to the
Mailman list:

From glenvdb@h... Mon Jan 24 13:11:23 2005
Return-Path: <glenvdb@h...>
X-Sender: glenvdb@h...
X-Apparently-To: <email address hidden>
Received: (qmail 63953 invoked from network); 24 Jan 2005
21:11:22 -0000
Received: from unknown (66.218.66.172)
by m21.grp.scd.yahoo.com with QMQP; 24 Jan 2005 21:11:22 -0000
Received: from unknown (HELO hotmail.com) (65.54.247.12)
by mta4.grp.scd.yahoo.com with SMTP; 24 Jan 2005 21:11:22 -0000
Received: from mail pickup service by hotmail.com with Microsoft
SMTPSVC;
Mon, 24 Jan 2005 13:11:01 -0800
Message-ID: <BAY2-F12E39DA21AB595CF271B67BF850@p...>
Received: from 198.53.120.64 by by2fd.bay2.hotmail.msn.com
with HTTP;
Mon, 24 Jan 2005 21:10:01 GMT
X-Originating-Email: [glenvdb@h...]
X-Sender: glenvdb@h...
To: <email address hidden>
Bcc:
Date: Mon, 24 Jan 2005 14:10:01 -0700
Mime-Version: 1.0
Content-Type: text/html; format=flowed
X-OriginalArrivalTime: 24 Jan 2005 21:11:01.0201 (UTC)
FILETIME=[34DA8C10:01C50259]
X-eGroups-Remote-IP: 65.54.247.12
From: "Glen VanDenBiggelaar" <glenvdb@h...>
X-Originating-IP: [198.53.120.64]
Subject: RE: [Coco] [Color Computer] Re: Blank Emails
X-Yahoo-Group-Post: member; u=22654116
X-Yahoo-Profile: glenvdb

Complete "blank" (HTML stripped) email with all headers
shown by Eudora full-header mode, from the same poster as it
comes out of Mailman to the list members:

Return-Path: <email address hidden>
Delivered-To: bathory-maltedmedia:<email address hidden>
X-Envelope-To: <email address hidden>
Received: (qmail 3612 invoked by uid 3002); 24 Jan 2005
00:26:11 -0000
Delivered-To: bathory-maltedmedia:<email address hidden>
Received: (qmail 3605 invoked from network); 24 Jan 2005
00:26:10 -0000
Received: from five.pairlist.net (216.92.1.121)
  by qs281.pair.com with SMTP; 24 Jan 2005 00:26:10 -0000
Received: from five.pairlist.net (localhost [127.0.0.1])
 by five.pairlist.net (Postfix) with ESMTP
 id 6E36A1A7CF; Sun, 23 Jan 2005 19:26:05 -0500 (EST)
X-Original-To: <email address hidden>
Delivered-To: <email address hidden>
Received: from qs281.pair.com (qs281.pair.com [216.92.131.37])
 by five.pairlist.net (Postfix) with SMTP id 5E2BE1A7BB
 for <email address hidden>; Sun, 23 Jan 2005
19:26:04 -0500 (EST)
Received: (qmail 3596 invoked by uid 3002); 24 Jan 2005
00:26:04 -0000
Delivered-To: bathory-maltedmedia:<email address hidden>
Received: (qmail 3593 invoked from network); 24 Jan 2005
00:26:04 -0000
Received: from n8a.bulk.scd.yahoo.com (66.94.237.42)
 by qs281.pair.com with SMTP; 24 Jan 2005 00:26:04 -0000
Received: from [66.218.69.5] by n8.bulk.scd.yahoo.com with
NNFMP;
 24 Jan 2005 00:26:03 -0000
Received: from [66.218.66.27] by mailer5.bulk.scd.yahoo.com
with NNFMP;
 24 Jan 20...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.