7 replies
by [_rick_>
What does the embedded start with:
Similar to this:
------ =_NextPart_000_01BA6275.348C1000
Content-Type: application/ms-tnef
Content-Transfer-Encoding: base64
Or similar to this:
begin 600 WINMAIL.DAT
This extra info would help indeterming what may be the cause.
Thanks
by bk1021
--=_alternative 004DB0A38...
--=_mixed 004DB0A38...
Content-Type: application/octet-stream; name="ipv.doc"
Content-Disposition: attachment; filename="ipv.doc"
Content-Transfer-Encoding: base64
by gilesguthrie
It sounds like your client isn't splitting the message into its components when you're trying to read it.
This often happens in Exchange/Outlook, when the cover memo (the body of the message) is sent in Rich Text format. The mail message consistsof the MIME headers, the plain-text cover memo, the rich-text cover memo (MIME-encoded) and the attachment (also MIME-encoded).
The solution to this is included in SP5 of Exchange I believe. Alternatively, you can request that the sender send their messages (not attachments) as plain text. We have had this problem with GroupWise 5.5 receiving messages from Exchange domains.
by bk1021
by [_rick_>
The problem is with the Lotus Domino SMTP configuration. If you know what version of Domino is being used, the best bet is to upgrade to 5.0.9, there were some wierd errors that surfaced with 5.0.5 through 5.0.7.
There are numerous articles on the various mime issues and Lotus Domino 5.0x. I believe the majority were fixed by the time 5.0.9 was introduced.
http://www-3.ibm.com/software/lotus/support/
I am unable to be more specific since I don't know the particulars of the Domino environment.
by bk1021
by bk1021
This discussion is closed to new replies.
Trending Software posts
Sort by Trending