Issue 854102: Message.get_filename() problem - Python tracker (original) (raw)

Created on 2003-12-04 15:26 by nemethe, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (4)
msg19275 - (view)	Author: Ervin Németh (nemethe)	Date: 2003-12-04 15:26
There are obviously e-mails with non-standard encodings (who wants to join me hating pine?) See attached backtrace. A local patch of - return unicode(newvalue[2], newvalue[0] or 'us-ascii') + try: + return unicode(newvalue[2], newvalue[0] or 'us-ascii') + except LookupError: + return unicode(newvalue[2], 'us-ascii', 'replace') solved the problem here.
msg19276 - (view)	Author: Barry A. Warsaw (barry) *	Date: 2004-05-10 14:50
Logged In: YES user_id=12800 Please attach a sample test case to illustrate the problem.
msg19277 - (view)	Author: Ervin Németh (nemethe)	Date: 2004-05-12 14:28
Logged In: YES user_id=768522 Barry, sorry but it is 6 month since the report. The mail causing the problem is long lost. You could try contacting Gregor Maier who commented on mailman bug 803729 recently. He is at http://sourceforge.net/users/maiergre/
msg19278 - (view)	Author: Barry A. Warsaw (barry) *	Date: 2004-10-02 21:04
Logged In: YES user_id=12800 This will be fixed in email 3.0/Python 2.4.