| Stefan Ritt wrote: |
| Chris Green wrote: | The email I get has:
Subject:
=?ISO-8859-1?B?W0Jvb05FLUVMT0ddIE5ldyBzdWJtaXNzaW9uIHRvIENoYXJnZWQgQ3Vyc
mVudCBQaSBQbHVzIGZyb20gQ2hyaXMgR3JlZW4=?=
... which isn't particularly illuminating. |
This is the BASE64 encoding of the subject. It was discussed here and I implemented it according to RFC2047. |
Well not quite. According to the RFC the encoded word must not be longer than 75 characters! Indeed
shorter subjects are displayed by pine, but not longer ones as they do not follow RFC2047.
Below is the quote from the RFC.
| Stefan Ritt wrote: |
All subjects I receive look fine in Outlook and Thunderbird, but not under Pine, which apparently does not implement the RFC correctly.
|
Actually pine implements it correctly but not elogd 
The relevant text from the RFC
An 'encoded-word' may not be more than 75 characters long, including
'charset', 'encoding', 'encoded-text', and delimiters. If it is
desirable to encode more text than will fit in an 'encoded-word' of
75 characters, multiple 'encoded-word's (separated by CRLF SPACE) may
be used.
|