Tickets :: Comment on [#3101] Wrong mime-encoding of subject header

* Your Email Address
* Spam protection	Enter the letters below: . ..__ \ /.__ .__ \| \|\| \ >< \| \[__) \|/\\|\|__// \\|__/\| \
Comment	>> This seems to me more like an excuse because you don't want to fix, > >> which is fine, but don't say that it is unfixeable... > > > > AAAAGGH! FUD! Please tell me exactly WHAT is broken? The fact > that we encode exactly as the RFC tells us we can? The fact that > every other mail reader handles the message correctly? So a > program that we have no control over is not handling the message > correctly? > > > > Furthermore, looking at the header text, this has absolutely > nothing to do with MIME encoding. it looks as if Outlook is broken > when it comes to handling RFC 2822 headers, specifically section > 2.2.3. in your example, we are splitting a line between two > non-encoded words. MIME encoding rules should not be used at all > when rebuilding the line in this case! Outlook apparently tries to > use MIME encoding wrapping rules to unwrap the line once it spots > MIME encoding _somewhere in the header_. I don't know for sure since > microsoft isnt showing us the code. but there is no doubt this is > wrong behavior. we are not going to "fix" anything BECAUSE THERE IS > NOTHING TO FIX! (despite your unsubstantiated claim we are using this > as an "excuse")
Attachment
Watch this ticket