[ ] Rewrite Notes Addresses: Mark this checkbox if you want the Mail Connector to strip sub-domain addresses and leave just the single-domain addresses. If you enable this feature, you must also specify:
|
• |
Internet Domains: Enter one or more domains, separated by commas. For example, specify the Internet Domain internetdomain.com for the Mail Connector to replace jsmith@server.internetdomain.com with jsmith@internetdomain.com. |
[ ] Rewrite Notes Common Names: Mark this checkbox if you want the Mail Connecter to convert Notes-style common names in calendar items to a "friendlier" form—for example, to convert John Smith/domain1/domain2 to John Smith.
[ ] Remove ’Friendly Names’ from Exchange to Domino Messages: Mark this checkbox if you want the Mail Connector to replace "friendly" (display) Exchange email addresses with SMTP addresses in messages sent from Exchange to Domino.
These limits let CMN enforce certain compatibilities between the Notes and Exchange environments.
Maximum Subject Line Length: The longest message Subject line CMN will permit, in number of characters. If a Subject line exceeds this length, the Mail Connector will truncate the line and insert ellipsis (...). The default of 1975 is the maximum allowed by a local Microsoft Exchange, and should be plenty in most local-Exchange environments. But if coexisting with Office 365, this limit should be set much lower, to 255.
Maximum Number of MIME Parts: The maximum number of MIME bodies CMN will allow in multipart messages. CMN will bounce a message with more than this number of MIME bodies. The default limit of 5000 is very high. But if coexisting with Office 365, this limit should be lowered to 250.
|
NOTE: Verify any shared resources that will be referenced by Notes active mail content are included in the CMN.ntf template file. Active mail content that references shared resources not included in CMN.ntf will appear to an Exchange recipient as a database with empty cells or other missing parts. |
|
• |
Active Mail Processing Performed: Mark any number and any combination of checkboxes to indicate the types of active content you want CMN to process: |
|
• |
Attachment Options: Mark either, neither or both checkboxes to indicate how CMN should handle active-mail attachments: |
|
• |
Send Notes Alternative Text to Recipients: Determines whether CMN will retain and send any in-line attached HTML and/or plain-text renderings of active-mail content. |
|
• |
Strip Extra Notes Attachments: Determines whether CMN will remove any extra attached plain-text renderings of active-mail content. |
|
• |
Attachment Name: Enter the filename you want CMN to assign to active-mail attachment files. |
|
• |
Input Template File: Use the Browse button ([...]) to specify the path (including filename) of the CMN template file. This file provides the information necessary for CMN to properly process the Notes .OND attachment and produce the active-mail attachment file. The default is set to CMN.ntf. |
|
• |
Messages File: The path (including filename) of the .xml file containing the CMN notification messages. The other values on this screen are saved in the file you specify here, and the CMN Mail Connector pulls your preferred message from this file. |
|
IMPORTANT: Any new information or changes entered in this screen will be saved to the Messages File only when you save the configuration file—by selecting Save Configuration File on the File menu. If you exit the Management Console without saving the configuration, any new information or changes entered in this screen (or any other screen) will be lost. |
Repeat this process for as many message types as you want to customize.
|
1 |
In the folder tree to the left of the Description, Plain Text Message and HTML Message fields, select the message you want to view or customize. When you select the message in the folder tree, the fields show the associated current values for: |
|
• |
Description (uneditable, FYI only): A name and/or brief description of the circumstances that would cause this message to be sent. |
|
• |
Plain Text Message: The message, in plain-text format, that CMN will insert into plain-text emails to notify recipients. |
|
• |
HTML Message (does not apply, and appears grayed-out and uneditable, for NDR-type messages and some other message types): The message, in HTML format, that CMN will insert into HTML emails to notify recipients. |
|
• |
Delivery Action (applies only to the Subject strings of SenderResponses, as selected in the folder tree at left): A combo box to specify how CMN will handle the selected SenderResponse: |
|
• |
Hard Bounce Message (NDR): CMN rejects the message, and the sending server determines what to do. |
|
• |
Insert Instructional Text for Recipient: CMN inserts a text string (as specfiied above, typically instructions) into the message it relays to the recipient, and the sender is not notified. Note: CMN will ignore this Insert Instructional Text option for these message types that require a Soft Bounce: |
|
• |
Soft Bounce Message (Friendly Message to Sender): CMN rejects the message, and sends a notification to the sender explaining the reason. |
|
NOTE: The Delivery Action can be specified only for Subject strings (both a Remark and a Subject can be configured for each SenderResponse). |
|
2 |
To customize either or both the Plain Text Message and HTML Message fields: Click your cursor into the text box, and use familiar text-editing features to add, delete and/or edit the text box contents. |
|
• |
Insert Variable...: Calls a pop-up list of defined variables (for the date, time, message sender, etc.) from which you may select one to insert inline into the text of a Plain Text Message or HTML Message (see above). A message may, for example, cite the proposed date and time of a meeting invitation, which will vary with every instance of the message. |
|
• |
Use Default Message: Restores the default message values into the Plain Text and HTML Message fields above. Any custom message data that may already appear in the fields will be lost. |
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center
