I've raised this point before, and following up the answers and taling to PSS
brought up more issues I'd like advice on.
If you set E2K up with the SMTP connnector working in default mode, any plain
text message you send out to an Internet address gets rendered into
"quoted-printable" form. If the end system is aware of this the result is good
- you keep the paragraph-based nature of the stuff you type in Outlook, in
distinction to how the Ex5.5 IMS breaks the text into arbitrary lines.
However, there are two issues from this:
- People who insist on using clients that can handle only plain text
- Systems like MajorDomo that expect plain text
In our environment (a University) the first could be bad - someone mails off a
text with
A = B + 7
in it and the recipient using mailx (yuk) sees
A =3D B + 7
We can maybe tell our users that we no longer support plain-text-only mail (but
it will be hard).
The MajorDomo issue could be worse, but we'll probably get by. But what do we
do with text-driven automatic systems that expect stuff like
Something Something = Something
???
And what will auto-responder systems do with the "=" added at the end of lines
broken for transmission?
We could set the SMTP connector to send out in UUEncode format - but mail
clients like Eudora Lite can't handle this, and moving off MIME is rather
silly. PSS tell us there's no way at all to turn quoted-printable encoding off
otherwise.
Other people must have a need to interwork with plain-text-only systems,
surely? What are you guys doing in these cases?? We are just on the point of
going live on E2K, and we are having to seriously consider junking it and
moving it to a Unix-based mail system because of this....
Thanks
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
