> PB> What would cause my MS Exchange users'
> PB> messages to generate archive entries that frequently
> PB> (though not constantly) end in an '=20' or simply '='
> PB> when they are written out.
>
> Because Microsoft Exchange is broken; it thinks that spaces need to be
> escaped even in text/plain messages.
Spaces at the end of a line are supposed to be escaped if you are doing
quoted-printable encoding (which I think is the default setting)
> Try turning all MIME encoding off unless you are sending binary data.
I've seen things like config file listings destroyed by adding the ='s
at the ends where it would be better to just lose the blanks.
Has anyone tried adding perl code to undo quoted-printable before
passing on to the list? Perhaps this could be an option or a setting
could force it if there are no 8-bit characters after decoding.
Les Mikesell
les@mcs.com
Follow-Ups:
References:
|
|
