|
|
Avoid wrapped text in messages from Mail to Outlook
even more worse is the bug that adds a "space" to the end of each line. Worse because Thunderbird that makes it "not line breaked" breaks URLs then. So all long urls I send around in office ... are not working. I reported this 3 times to apple, its still in "working on" state. And That since 10.4.1. *sigh*
Avoid wrapped text in messages from Mail to Outlook
Space-Newline is the sequence used by "format=flowed" to indicate a soft line break, that is, one that can be removed to re-flow the paragraph for the display.
Avoid wrapped text in messages from Mail to Outlook
I yelled at apple for the URLs. I just did (after 10.4.3) a new bug report with showing that even the angel brackets don't help to save the URL. I hope apple listens to me.
Avoid wrapped text in messages from Mail to Outlook
Specifically, from RFC 3676, Section 4.2 (Generating Format=Flowed) Apple is going against the following recommendation:
Regardless of which technique is used, a generating agent SHOULD NOT insert a space in an unnatural location, such as into a word (a sequence of printable characters, not containing spaces, in a language/coded character set in which spaces are common). If faced with such a word which exceeds 78 characters (but less than 998 characters, the [SMTP] limit on line length), the agent SHOULD send the word as is and exceed the 78-character limit on line length.Technically they are not violating the RFC since it says "SHOULD NOT" and not "MUST NOT" but it is highly annoying to have to use TinyURL all the time... I filed this bug under 10.2, so I'm not hopeful that they have any plans to fix it.
Avoid wrapped text in messages from Mail to Outlook
My understanding is that the relevant part of RFC 3676 is actually paragraph 4.3, in which it is written:
[Quoted-Printable] encoding SHOULD NOT be used with Format=Flowed unless absolutely necessary (for example, non-US-ASCII (8-bit) characters over a strictly 7-bit transport such as unextended [SMTP]). In particular, a message SHOULD NOT be encoded in Quoted-Printable for the sole purpose of protecting the trailing space on flowed lines unless the body part is cryptographically signed or encrypted.Apparently Mail.app does send 8-bit characters over a 7-bit transport, so technically its behavior is correct. Not that that's any confort to those who are on the receiving end of broken URLs (not Mail.app users, natch). I remember first hearing about this behavior over three years ago, so my bet is that you won't see it change in Mail.app, but will eventually see other email clients improve their handling of email sent from clients observing this requirement of RFC 3676. 2 cents. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.05 seconds |
|