Message120279
| Author |
jelie |
| Recipients |
eric.araujo, jelie, pitrou, r.david.murray |
| Date |
2010年11月02日.22:56:21 |
| SpamBayes Score |
0.0014004466 |
| Marked as misclassified |
No |
| Message-id |
<1288738583.25.0.147008491692.issue10284@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> Unless I'm mistaken, Content-Type should only apply to the body, not the
> headers. Either the headers use UTF-8 (RFC 3977), or they should be
> MIME-encoded. Everything else is undecodable.
Yes, of course. Such articles are not RFC-compliant. You're not mistaken when you mention that the Content-Type: header field applies to the body.
I was just answering about how the encoding could be guessed. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年11月02日 22:56:23 | jelie | set | recipients:
+ jelie, pitrou, eric.araujo, r.david.murray |
| 2010年11月02日 22:56:23 | jelie | set | messageid: <1288738583.25.0.147008491692.issue10284@psf.upfronthosting.co.za> |
| 2010年11月02日 22:56:21 | jelie | link | issue10284 messages |
| 2010年11月02日 22:56:21 | jelie | create |
|