>This RFC dates from 2001 - which is a centenary in IT-time! >As it is written, it's "a more conservative recommendation". >But in the meantime all of (serious) mail programs are able to handle it.
A mail app can do as it wants, but the mail relays will do as they please as well. This is a case of what you see is not what they will necessarily get. And while the RFC is from 2001, it is the RFC and if folks don't adhere to it, then they can't complain when their way of doing things doesn't work. > >I ask for this: >Make for sending mails the option-choice for >- to break automaticaly at 78 character >OR >- free flow of characters > >And the same option-choice for incoming mails. Again, just because the mail app supports it doesn't mean the relays won't force their own line breaks on you. Then you end up with very messy text. I know at work our MS exchange server has the ability to "remove" extra line breaks, and it does all the time. Unfortunately, it also looks pretty bad sometimes when it does this. I would say, you're compromise isn't a bad one, but I'll argue that you'll still end up with mail recipients that complain about your strange line breaks (not that you put them in, but the mail relays did). Wayne -- "Somebody's dead forever..." - Somebody Got Murdered -- Joe Strummer (1952-2002) OP LoftBed Preferred Builder: http://www.wbwoodworks.com/ Wayne's Music Calendar: http://ical.mac.com/wayneb/Music PowerMail AppleScript Archives: http://www.ctmdev.com/tools/ Music Currently playing:
