 | | Re: Posting with MIME encoded FROM header —Todd Lehman
|
| | | (...) Hmm, I don't know. At first I want to say no it shouldn't -- because it's totally unreadable with that encoding. But OTOH, maybe yes it should, because maybe modern newsreaders are smart enough to decode that into 8-bit ISO characters on the (...) (25 years ago, 19-Jan-99, to lugnet.admin.general)
|
| | | |
| | | | | Re: Posting with MIME encoded FROM header —Fredrik Glöckner
|
| | | | (...) This was my first reaction as well. It has always been considered bad and ugly to post anything MIME encoded on news. But as you say yourself, this practice is becoming increasingly common, so you are probably going to be be confronted with it (...) (25 years ago, 19-Jan-99, to lugnet.admin.general)
|
| | | | |
| | | | | | Re: Posting with MIME encoded FROM header —Todd Lehman
|
| | | | | (...) Haven't encountered any problems yet (that have been reported, anyway) but I'll bet that if +128 characters aren't ISO-8859-1 encoded on the way out, the problem is going to pop up sooner or later. (...) I guess I'll need to stuff in an (...) (25 years ago, 19-Jan-99, to lugnet.admin.general)
|
| | | | | |
| | | | | | Re: Posting with MIME encoded FROM header — Todd Lehman
|
| | | | (...) (Just came across this old thread and realized this hadn't yet been fixed.) OK, I've just installed a filter which does this conversion based on the RFC 2047 specification. This eliminiates nasties like =?ISO-8859-1?Q?f=F2=...=20b=E2r?= in (...) (21 years ago, 27-May-03, to lugnet.admin.general, lugnet.admin.nntp)
|
| | | | |
