Aliet Santiesteban Sifontes wrote:
>Thank's Mark, how could I find the bad message,
You have to look through the digest.mbox file and find
Content-Disposition: headers. Typically, such a header might look like
Content-Disposition: attachment;
filename="Some_name.ext"
In your case, the value of the filename= will look garbled.
>I'm
>worried because If I can make the list work again, I
>have the risk this happens again, is there any patch
>for this??. I think that this can be a potencial dos
>attack to other lists on the net.
There is no patch that I know of. The actual error occurs in the Python
email library, not in Mailman. The code has changed between Mailman
2.1.5 and 2.1.6, but not in a way that I think would avoid the
exception.
You could try replacing the line
fnext = os.path.splitext(msg.get_filename(''))[1]
in /var/lib/mailman/Mailman/Handlers/Scrubber.py with
try:
fnext = os.path.splitext(msg.get_filename(''))[1]
except UnicodeDecodeError:
fnext = ''
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list
[email protected]
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/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
