Marc Mutz <mutz(_at_)kde(_dot_)org> schrieb/wrote:
The next hop doesn't support 8BITMIME. No problem. This is an
intelligent server that acts by the gateway model of rfc1652 and tries
to recode the offending body parts. Whooops... bounce. :-(
Am I missing something?
Yes, the proposed encapsulation.
The 8BITMIME server would only see an application/message-partial body
labelled as 8bit. It can recode it with quoted-printable or base64
(because that would be allowed for application/message-partial).
Only an EMIME MTA would see the enclosed EMIME entity directly. If it
wants to send it to a non-EMIME MTA (such as a 8BITMIME-only MTA), it
has to encapsulate it in the same way. This is very similar to message/
partial fragmentation (except that it uses application/message-partial
and that there's only one part).
Claus
--
http://www.faerber.muc.de/