Summary | Missing MIME-Version Header leads to render issues |
Queue | IMP |
Queue Version | FRAMEWORK_5_2 |
Type | Bug |
State | Not A Bug |
Priority | 1. Low |
Owners | |
Requester | rene.marth (at) hetzner (dot) de |
Created | 03/13/2017 (3035 days ago) |
Due | |
Updated | 03/16/2017 (3032 days ago) |
Assigned | |
Resolved | 03/14/2017 (3034 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
mails correctly?
mail client I know that makes garbage out of such a mail. Is it
really more important to rely on a RFC instead of solving the issue
for your users?
Bug: 12062for more of our thoughts on this.text RFC2822 messages. Period. There is no room for interpretation.
mails correctly? Of course the mails are not standard conform - but
you are the only mail client I know that makes garbage out of such a
mail. Is it really more important to rely on a RFC instead of solving
the issue for your users?
text RFC2822 messages. Period. There is no room for interpretation.
State ⇒ Not A Bug
text RFC2822 messages. Period. There is no room for interpretation.
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ Missing MIME-Version Header leads to render issues
Type ⇒ Bug
State ⇒ Unconfirmed
IMP. Yes, it is known that RFCs says that this is a required field.
However not all emails in real life have such a header and other mail
client vendors gives a reasonable fallback (if no header then assume
mime-version: 1.0)