Notes.ini Entry



Name:

    MIMERecodeBodyAndHeaders

Syntax

    MIMERecodeBodyAndHeaders=0 / 1

Applies to:

    Servers

Add-on:


    First Release:

      8.5.2

    Obsolete since:


      Category:

        MIME

      Default:

        None

      UI equivalent:

        None

      Description:


      SPR# TPON7RBDY4 - Fixed an issue that would cause inbound mime messages to show encoded characters in header (From/To/cc/bcc) instead of actual text when using server feature to append disclaimers to outbound messages.

      This issue was caused by the fix for SPR AONL7BJKYM to encode subject and body in same character set in 8.5 when using disclaimers. In 8.5.2, the fix for AONL7BJKYM has been re-worked and is off by default.

      To enable the new and improved fix for AONL7BJKYM that encodes in the same character set without corrupting the header, set the notes INI MIMERecodeBodyAndHeaders=1.

      Problem
      In Lotus Notes, if the subject and the body of a MIME message have different character set encodings, these messages can appear garbled to recipients in a non-Lotus Domino environment. This occurs when disclaimers are added by the server, resulting in different encoding in the subject and body in the CD-MIME conversion.

      Cause
      In one particular case, the Notes client was set up to send messages in MIME format to Internet addresses. The subject line contained characters that could be encoded as ISO-8859-1. The body of the message contained characters that required ISO-8859-2 encoding. Notes' CD-MIME handled this correctly by encoding the subject and the body as ISO-8859-1.

      The problem appeared when a mail policy was introduced to add a disclaimer to the message. The multi-lingual field in the disclaimer was set to "Best match". When the server rewrote the message, it used two different encodings for the subject and the body.
      Resolving the problem

      This issue is now fixed in Lotus Notes and Domino 7.0.4.

      Fix details: SPR# AONL7BJKYM

      When the server rewrites MIME, it ensures that the subject and body has the same encoding. An alternate workaround is to have the disclaimer added by the client.

      From Domino 8.5.1 FP3, this fix will require the use of the notes.ini parameter MIMERecodeBodyAndHeaders=1. See Technote #1409550: Friendly name and Internet address are encoded when disclaimers and RFC822 phrasing are enabled.


      Problem
      When message disclaimers and the RFC822 phrase are enabled on your Lotus Domino SMTP server, and the user name contains non-ASCII characters, both the friendly name and the Internet address are encoded.

      Steps to reproduce:
      1. Enable message disclaimers on the outbound Domino SMTP server.
      2. Create an organizational mail policy to include a disclaimer. Do not enable the client to add disclaimers.
      3. Create a user "Jørgen Test".
      4. In the MIME > Advanced > Outbound Message Options, set RFC822 phrase handling to use CN as phrase.
      5. Restart the server.
      6. Open the Notes client with "Jørgen Test" as the user and send mail to an Internet address.
      7. Have the Internet recipient open and reply to the mail. The reply address will look like the following:
      "Jørgen Test" <jtest@testdomain.com>@some.server.com
      8. View the MIME stream of the message and you will see the From address similar to the following:

      The above address should be encoded as follows:
      =?windows-1252?Q?=22J=F8rgen_Test=22?= <jtest@testdomain.com>
      Since the outbound server does not see the domain portion of the address, it will add its own name as the domain.

      Symptom
      When recipients attempt to reply to a message, the reply address is incorrect. This can also happen on ReplyTo All as the incorrect encoding applies to all address fields.

      Resolving the problem
      This issue is fixed in Domino 8.5.1 FP3 and 8.5.2.