Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Avoid wrapped text in messages from Mail to Outlook' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Avoid wrapped text in messages from Mail to Outlook
Authored by: gullevek on Nov 16, '05 07:02:26AM

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*

I wished Mail.app could do the "hard line break" way of Thunderbird and actually _ANY_ other Mail application. This tricky "flow" breaking in the background is a pain. Really. Thunderbird, mutt, etc, have just long long lines, not break, difficult to read and Outlook just breaks it down hard and it just looks stupid. Especially because you don't see the issue on your side. Its not Mail.app line breaks where it will put it, so you know what will happen. No it does it behind your back.

*sight* These are one of the small things that make life with a Mac really difficult.



[ Reply to This | # ]
Avoid wrapped text in messages from Mail to Outlook
Authored by: greed on Nov 16, '05 09:03:35AM

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.

It should NOT be sending long words broken in the middle, including URLs. Yell at Apple if it does. (For best protection of URLs in transport, surround with angle brackets. Still won't guarantee that some MUA or Exchange won't mess with it, though.)

Is your URL problem on transmit or receive? I haven't had anyone say that URLs I sent them are unusable--unless I've sent them to someone on the far side of an old Exchange server, which will re-wrap all text/plain messages. I've seen URLs displayed broken in Mail.app, but clicking on them re-assembles them correctly (or right-click and Copy Link).



[ Reply to This | # ]
Avoid wrapped text in messages from Mail to Outlook
Authored by: gullevek on Nov 16, '05 04:40:50PM

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.

Actually I encourage all who have the same URL issue to yell - file a bug report - at apple. The more they know, the more likely it is that it get fixed.



[ Reply to This | # ]
Avoid wrapped text in messages from Mail to Outlook
Authored by: jaysoffian on Nov 16, '05 05:50:24PM
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.

[ Reply to This | # ]
Avoid wrapped text in messages from Mail to Outlook
Authored by: Roquentin on Nov 17, '05 12:01:46AM
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.

[ Reply to This | # ]