[ mailman-Bugs-601082 ] personalized recip should be MIMEed
Bugs item #601082, was opened at 2002-08-28 03:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=601082&...
Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: personalized recip should be MIMEed
Initial Comment: If the list delivery is personalized, user's name is placed in To: header. When the user choose to register non-ascii character in the name, To: header contain non-ascii and breaks RFC(number?Idontknow). A quick and dirty patch is included. I hope Barry can inspect and revise it.
Comment By: Simone Piunno (pioppo)
Date: 2002-09-13 21:24
Message: Logged In: YES user_id=227443
If the address is coming from a web browser I believe you should be able to guess the encoding from the HTTP headers (at least for POST).
If the address is coming from the command line you could try to check KBCHARSET or you could just add an optional parameter (the list admin shouldn't be so clueless)
If the address is coming from an email you could allow non-ASCII only if properly encoded (so that you can deduce the encoding from the email)
In any case you should store the encoding valuesomewhere in the list database file, for later use.
Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 21:08
Message: Logged In: YES user_id=12800
Ouch, this is a tougher problem because you don't really know what character set the name is in. It may not be the charset for the user's preferred language at all.
I can see three approaches. First, you should never have funny characters in the real name component (use the encoded name instead). Second, there could be a a second entry box under the name asking for the charset of the name. It would default to us-ascii (or maybe just empty). I fear however that most people will be entirely clueless as to what the proper value would be. Third, if there are non-ascii characters in the name, I think we could just encode with utf-8 and be done with it -- you can't really guess much more about the proper encoding. I'm not sure the latter will work or will even be cross platform.
You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=601082&...