Notes Client 8.5.2 Forwarded Mail Corrupted
What causes Internet mail corruption from Notes 8.5.2?
We run Domino 8.5.2 and 6.5.4. SMPT mail goes via the 6.5.4 server.
My mail is on the 8.5.2 server. When I forward mail outside of the business to an Internet address (e.g. to a Gmail account) the message that arrives is incomplete and garbled. It is especially likely to happen if the message being forwarded is complex and contains layout and graphics (the sort of thing Amazon may send). It lookes perfect in the 8.5.2 client. If I Click forward and add a few lines of simple text then forward it to an external address it usually comes up with a message headed "Multilingual MIME Warning" which asks me to choose a font (this is a sure sign things aren't going well). Having sent the messsage, when opened from the Sent folder it is corrupted. Layout has gone haywire and 60 to 80% of the test added is simply missing. The message looks exactly the same when it arrives at its destination (as it does from the sent folder)
My problem has existed for some months, today a 2nd user reported the same thing. It's not just me now so now I'd better fix it!
Regards
Steve
We run Domino 8.5.2 and 6.5.4. SMPT mail goes via the 6.5.4 server.
My mail is on the 8.5.2 server. When I forward mail outside of the business to an Internet address (e.g. to a Gmail account) the message that arrives is incomplete and garbled. It is especially likely to happen if the message being forwarded is complex and contains layout and graphics (the sort of thing Amazon may send). It lookes perfect in the 8.5.2 client. If I Click forward and add a few lines of simple text then forward it to an external address it usually comes up with a message headed "Multilingual MIME Warning" which asks me to choose a font (this is a sure sign things aren't going well). Having sent the messsage, when opened from the Sent folder it is corrupted. Layout has gone haywire and 60 to 80% of the test added is simply missing. The message looks exactly the same when it arrives at its destination (as it does from the sent folder)
My problem has existed for some months, today a 2nd user reported the same thing. It's not just me now so now I'd better fix it!
Regards
Steve
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I spoke too soon. Problem persists.
ASKER
For the record: The problem was resolved by setting the following:
Thanks to all who excercised brain cells on this one.
Location Document - Mail TAB - Format for messages addressed to internet locations = MIME Format
NAB Entry for user - Format preference for incoming mail = Keep in senders' format
Server Configuration settings - MIME Tab - Conversion Options - Outbound = Create multi-part alternative including conversion and encapsulation
Problem now appears to be resolved. Thanks to all who excercised brain cells on this one.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
And how was my comment not part of the solution?
ASKER
One more thing:
Server - Messaging - Configuration - MIME - Conversion options - inbound
Do select "Use character set auto-detection if message has no character set information: = Yes" setting. This seems to need to be set to "No" in my environment.
Server - Messaging - Configuration - MIME - Conversion options - inbound
Do select "Use character set auto-detection if message has no character set information: = Yes" setting. This seems to need to be set to "No" in my environment.
ASKER
This is now being dealt with by Lotus as problem persists.
ASKER
SOLUTION
The version that works is "Release 8.5.2FP2|March 23, 2011" = 379 in fact any version we had except "Build V852_05192010|May 19, 2010" = 378 was fine. I didn't realise we had an unsupported version, it turned out that this was one of its problems. It seems if the version starts "Build" rather than "Release" it is pre-release and you can expect obscure problems.
I sent all the Notes users a message containing a buton to report their version to a central notes database which easily shows the mix of releases we are supporting aganst their Windows and Notes login names and computer name.
I know of no problems with 379.
The version that works is "Release 8.5.2FP2|March 23, 2011" = 379 in fact any version we had except "Build V852_05192010|May 19, 2010" = 378 was fine. I didn't realise we had an unsupported version, it turned out that this was one of its problems. It seems if the version starts "Build" rather than "Release" it is pre-release and you can expect obscure problems.
I sent all the Notes users a message containing a buton to report their version to a central notes database which easily shows the mix of releases we are supporting aganst their Windows and Notes login names and computer name.
I know of no problems with 379.
ASKER
In the NAB entry for person changed from "Keep in Senders format" to "Prefers Mime"
and in the Configutation document under MIME - Conversion Options - Outbound
changed from "Create multi-part alternative including conversion and encapsulation" to "from Notes to HTML"
Initial tests show results dramatically better if not quite perfect.