| Summary | Empty recipient and msg body when replying |
| Queue | IMP |
| Queue Version | 6.2.3 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | je (at) ktf (dot) rtu (dot) lv |
| Created | 11/20/2014 (3877 days ago) |
| Due | |
| Updated | 11/25/2014 (3872 days ago) |
| Assigned | 11/20/2014 (3877 days ago) |
| Resolved | 11/24/2014 (3873 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
get a question mark instead of letter "?", but as for the message
body, I think, you are wrong
completely relevant, since for reply messages the sender's name is
generally added to the reply message text.
So adding windows-1252 text to a utf-8 body is going to produce a
reply message body that contains garbage. That's why the header
charset determination is critical.
clamed(?) UTF8. So my previous comment if full of question marks
instead of UTF-8 characters from national table.
What I see is just < html lang="lv-LV"> in page source without
specifying one of three existing encodings - UTF-8, ISO8859-13 or
ISO8859-4 (now rearely used)
'=?utf-8?B?IklsZ2EginVwbGluc2thIg==?= <foo@example.com>'
MIME decoding the personal part leads to a string that is *NOT*
UTF-8, as claimed (it is windows-1252).
Additionally, the body text is *claimed* to be UTF-8, but it isn't.
a question mark instead of letter "?", but as for the message body, I
think, you are wrong - i opened it in hex viewer - letters like
?,?,?,?,?,? take two bytes. Win-1252 or, often more likely used,
win-1257, are one byte.
Janis
State ⇒ Not A Bug
'=?utf-8?B?IklsZ2EginVwbGluc2thIg==?= <foo@example.com>'
MIME decoding the personal part leads to a string that is *NOT* UTF-8,
as claimed (it is windows-1252).
Additionally, the body text is *claimed* to be UTF-8, but it isn't.
We do several tricks to try to work around these completely broken
messages, but there are no guarantees.
headers and body are in UTF-8, but the data is really windows-1252.
I am looking at the message in console with UTF-8 support and
everything is OK with text (it's in Latgalian).
Anything wrong with From: line?
Which makes sense because that message is broken. It claims the
headers and body are in UTF-8, but the data is really windows-1252.
New Attachment: example.tar.xz
Janis
placing it here.
Is it ok? I'll include reference to this bug in Subject.
Janis
State ⇒ Feedback
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ Empty recipient and msg body when replying
Type ⇒ Bug
Priority ⇒ 2. Medium
message form without receiver's address and without citation. By now I
found only one sender I am not able to reply to without additional
operations like entering e-mail address and copying the text I wish to
comment.
I can provide the full message, but do not wish to attach it here, as
it is personal to some degree.
Bug actually works also with the IMP 6.1.7