[ mailman-Bugs-1433666 ] News to mail gateway: Outlook Express broke uuenc.attachment

[SourceForge.net]

Bugs item #1433666, was opened at 2006-02-17 08:02
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1433666&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: nntp/news
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Dâniel Fraga (danielfraga)
Assigned to: Nobody/Anonymous (nobody)
Summary: News to mail gateway: Outlook Express broke uuenc.attachment

Initial Comment:
When someone posts on my nntp server a message with an
uuencoded attachment using Outlook Express, the message
appears broken in mailman.

For example:

Original message:
news://news.abusar.org/drq50u$gmp$2@servicos.netuno.com.br

Mailman message (corrupted):

http://core.abusar.org/pipermail/u-br.lazer.humor/2006-February/000346.html?t

I think the problem is related to how mailman handles
the end of lines...

Thank you.


----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-02-17 17:22

Message:
Logged In: YES 
user_id=1123998

Are you talking only of archived messages or individual
received messages as well?

In the case of the archived message you point to, the
problem is that you have configured the archiver to obscure
email addresses so that every '@' character in the uuencoded
data is rewritten as ' em '.

The issue is compounded by Outlook Express, because when
Outlook Express sends a uuencoded attachment, it does not
actually encapsulate the uuencoded attachment in a separate
MIME part. If it did, Scrubber would store it separately and
put a link to it in the archived message, but in the Outlook
Express case, the 'attachment' is not an attachment at all,
but rather just a uuencoded file in the body of the message.
Thus, it is just more text subject to munging by email
address obscuring.

I was going to close this report with the above explanation,
but I am waiting to hear if you also have a problem with
individual messages or digests. I know my explanation is
correct for the archives because I took the uuencoded data
from your archive page and replaced all the ' em ' with '@',
and I was then able to uudecode the file into a valid jpeg.

So, do you have a problem with messages or digests from the
list, and if so, can you provide an example message for
analysis?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1433666&group_id=103