A non-text attachment was scrubbed... -- URL break
I've looked at the Whole Mailman FAQ and looked at archived message threads back 5-6 months and have not see a discussion or resolution on the problem I'm seeing with URL line breaks in my list archived messages. Basically if I set Non-digest options/"Scrub attachments of regular delivery message?" to No my archived messages, scrubber adds the non-test attachment was scrubbed URL, URL's are ok full line and clickable. Messages from the list have the attachment and life is good. The first example below. If I set Non-digest options/"Scrub attachments of regular delivery message?" to Yes my archived messages URL's have an extra = in the URL string at the end of line one and a line break making the URL 2 lines and non-clickable. The second example. Please, if somebody has seen this problem, has a resolution, or if the FAQ has the answer, let me know. ------------- next part -------------- A non-text attachment was scrubbed... Name: Official notice Spam Filtering Implementation Update 09030.pdf Type: application/octet-stream Size: 76382 bytes Desc: not available Url : <http://www.mn.us/pipermail/listname/attachments/20050901/4bb779ff/Officialn oticeSpamFilteringUpdate09030-0001.pdf>
-------------- next part -------------- A non-text attachment was scrubbed... Name: Official notice Spam Filtering Implementation Update 09030.pdf Type: application/octet-stream Size: 76382 bytes Desc: not available Url : <http://www.mn.us/pipermail/listname/attachments/20050901/2d8=> eb35e/OfficialnoticeSpamFilteringUpdate09030.pdf
-tw
-tw
Tim Willson wrote:
If I set Non-digest options/"Scrub attachments of regular delivery message?" to Yes my archived messages URL's have an extra = in the URL string at the end of line one and a line break making the URL 2 lines and non-clickable. <snip>
-------------- next part -------------- A non-text attachment was scrubbed... Name: Official notice Spam Filtering Implementation Update 09030.pdf Type: application/octet-stream Size: 76382 bytes Desc: not available Url : <http://www.mn.us/pipermail/listname/attachments/20050901/2d8=> eb35e/OfficialnoticeSpamFilteringUpdate09030.pdf
This was at some point a quoted-printable encoding. I don't know where the '>' at the end of the first line came from, but in quoted-printable speak the '=' at the end of the first line of
Url : <http://www.mn.us/pipermail/listname/attachments/20050901/2d8= eb35e/OfficialnoticeSpamFilteringUpdate09030.pdf
means "there is really no line-break here - join this line to the next".
I've looked at Mailman/Handlers/Scrubber.py, and it doesn't put angle brackets ('<', '>') around the urls. I don't know where they are coming from, but I don't think Mailman is doing it.
Likewise, Scrubber.py does not produce a quoted-printable encoded message. It produces a message with Content-Transfer-Encoding: 8bit.
So it looks like somewhere in the outgoing MTA path, an MTA is converting 8bit to quoted-printable which is changing
Url : http://www.mn.us/pipermail/listname/attachments/20050901/2d8eb35e/Officialno...
to
Url : http://www.mn.us/pipermail/listname/attachments/20050901/2d8= eb35e/OfficialnoticeSpamFilteringUpdate09030.pdf
and then somewhere further along, something is not correctly interpreting the quoted-printable encoding - perhaps the thing which is putting the angle brackets around the http://www.mn.us/pipermail/listname/attachments/20050901/2d8= part.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Fri, Sep 02, 2005 at 16:39:01, Mark Sapiro wrote:
Hi,
I'm seeing the same thing. It works OK as long as the body of the message is us-ascii, but if it contains characters like æøå (iso-8859-1) the message is printed in the archive as quoted printables (litteraly) and the link is mangled like reported by the OP.
The message is sent fine to the list, _unless_ msg_footer is empty. If it is empty the message mailed to list also contains quoted printables.
(If scrub_nondigest is set to no, archiving works perfectly fine with iso-8559-1 characters)
Anyone else seen this?
Lars
Tim Willson wrote:
If I set Non-digest options/"Scrub attachments of regular delivery message?" to Yes my archived messages URL's have an extra = in the URL string at the end of line one and a line break making the URL 2 lines and non-clickable. <snip>
-------------- next part -------------- A non-text attachment was scrubbed... Name: Official notice Spam Filtering Implementation Update 09030.pdf Type: application/octet-stream Size: 76382 bytes Desc: not available Url : <http://www.mn.us/pipermail/listname/attachments/20050901/2d8=> eb35e/OfficialnoticeSpamFilteringUpdate09030.pdf
This was at some point a quoted-printable encoding. I don't know where the '>' at the end of the first line came from, but in quoted-printable speak the '=' at the end of the first line of
Url : <http://www.mn.us/pipermail/listname/attachments/20050901/2d8= eb35e/OfficialnoticeSpamFilteringUpdate09030.pdf
means "there is really no line-break here - join this line to the next".
I've looked at Mailman/Handlers/Scrubber.py, and it doesn't put angle brackets ('<', '>') around the urls. I don't know where they are coming from, but I don't think Mailman is doing it.
Likewise, Scrubber.py does not produce a quoted-printable encoded message. It produces a message with Content-Transfer-Encoding: 8bit.
So it looks like somewhere in the outgoing MTA path, an MTA is converting 8bit to quoted-printable which is changing
Url : http://www.mn.us/pipermail/listname/attachments/20050901/2d8eb35e/Officialno...
to
Url : http://www.mn.us/pipermail/listname/attachments/20050901/2d8= eb35e/OfficialnoticeSpamFilteringUpdate09030.pdf
and then somewhere further along, something is not correctly interpreting the quoted-printable encoding - perhaps the thing which is putting the angle brackets around the http://www.mn.us/pipermail/listname/attachments/20050901/2d8= part.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/lsa%40business.auc.dk
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
-- Lars Anderson E-mail: lsa@business.aau.dk Faculty of Social Sciences Jabber: lsa@jabber.samf.aau.dk Aalborg University Voice: +45 96358225, Fax: +45 98153505 Denmark Office: Fib4-117
Lars Anderson wrote:
I'm seeing the same thing. It works OK as long as the body of the message is us-ascii, but if it contains characters like æøå (iso-8859-1) the message is printed in the archive as quoted printables (litteraly) and the link is mangled like reported by the OP.
The message is sent fine to the list, _unless_ msg_footer is empty. If it is empty the message mailed to list also contains quoted printables.
(If scrub_nondigest is set to no, archiving works perfectly fine with iso-8559-1 characters)
I see it too on a test system with Mailman 2.1.6. Thanks to your description of the triggering conditions, I can duplicate the problem.
It will be a few days before I have time to look at this further, but I'll report what I find to the list.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro wrote:
It will be a few days before I have time to look at this further, but I'll report what I find to the list.
See the post at <http://mail.python.org/pipermail/mailman-developers/2005-November/018288.htm...> for more information on this problem and a tentative patch to fix it.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sat, Nov 05, 2005 at 10:18:27, Mark Sapiro wrote:
Hi Mark,
I just applied the patch and as far as I can tell it has fixed the problem. :-)
Thank you very much for your help. We are going to use this feature of mailman a lot.
Best wishes Lars
Mark Sapiro wrote:
It will be a few days before I have time to look at this further, but I'll report what I find to the list.
See the post at <http://mail.python.org/pipermail/mailman-developers/2005-November/018288.htm...> for more information on this problem and a tentative patch to fix it.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
-- Lars Anderson E-mail: lsa@business.aau.dk Faculty of Social Sciences Jabber: lsa@jabber.samf.aau.dk Aalborg University Voice: +45 96358225, Fax: +45 98153505 Denmark Office: Fib4-117
participants (3)
-
Lars Anderson -
Mark Sapiro -
Tim Willson