MODIFYING PEER DOMAIN
To configure the different Peer Domain parameters, do the following:
- Enter the domain name of the peer that you want to configure (e.g. jade.net).
- Tick the Accept Mail option to allow IEMS to receive incoming mail from the peer domain.
- Tick the Transmit Mail option to allow the peer domain to send outgoing messages.
- Tick the Queue Mail Before Attempting Delivery option to force the SMTPC module to queue all messages destine for the peer domain for a certain period of time instead of delivering it immediately.
- Specify the Queue Run Interval. This field specifies the interval between consecutive queue runs.
- Specify the Re-try period. This field specifies the maximum number of hours before SMTPC attempts to deliver a delayed message.
- Specify the number of Maximum sessions. Some stacks experience troubles when handling too many outgoing SMTPC sessions. This option limits the number of outgoing simultaneous SMTP sessions per queue processor.
- Specify the number of Maximum number of messages per session. This parameter specifies the highest number of messages that can be sent using a single SMTP connection. When this number is increased, more messages can be sent to a remote SMTP server on each connection.
- Enter the maximum size (in bytes) of incoming messages for a particular domain in the Inbound field.
- Enter the maximum size (in bytes) of outgoing messages for a particular domain in the Outbound field.
- Tick the Keep IEMS Specific Anti-SPAM X-Header option if you want to keep the IEMS Specific Anti-SPAM
X-Header (if exist) in the message when SMTPC deliver it to next MTA. The is used to implement the Anti-SPAM MTA
Pass Through feature. By default, IEMS Specific Anti-SPAM X-Header will be stripped off for all domains.
- Tick the Convert Non-MAC File To MAC Format option if you want to convert all non-Apple attachments to Apple format by adding a header and an empty resource fork; and by encoding the attachments using any of the Apple encoding methods selected in the Apple attachment encoding section. This section should be checked if the peer domain and sub-domains are comprised largely of Macintosh users.
- Tick the Convert MAC File To Non-MAC Format option if the peer is a gateway to a network with a sizeable percentage of non-Macintosh recipients. This option strips Apple Notes mail attachments of their headers and resource forks (if there is any).
- Tick the Generate Non-MIME Mail Message option if the peer is not a MIME-compatible gateway. This is useful when communicating with older e-mail systems that do not understand MIME. In this case, either UUENCODE AppleSingle or UUENCODE MAC Binary II can be used to encode binary attachments. If the peer does not contain any Macintosh recipients, it is advised to select Convert MAC file to non-MAC format as well.
- Tick the Send Encapsulated NotesMail As File Attachment option if you want the message to contain body parts: the original mail body in plain text, file attachment (if there are any) contained in the original message and the NSF file attachment which contain all the NotesMail attributes inside.
- Tick the Send Only Encapsulated NotesMail option if you want the message to contain only one attachment, which is the NotesMail NSF file.
- Select a Native Attachment encoding method from the following:
- MIME
Specifies that non-Apple attachments are to be encoded using the MIME standard.
- UUENCODE
Specifies that non-Apple attachments are to be encoded using the older UUENCODE format.
- Select an Apple attachment encoding method from the following:
- MACMIME AppleSingle
Specifies that outgoing Macintosh attachments are to be encoded using the MACMIME AppleSingle standard.
- MACMIME AppleDouble
Specifies that outgoing Macintosh attachments are to be encoded using the MACMIME AppleDouble standard.
- MACMIME BinHex
Specifies that outgoing Macintosh attachments are encoded using the BinHex 4.0 standard specified in RFC-1741.
- UUENCODE AppleSingle
Specifies that outgoing Macintosh attachments are to be encoded using the AppleSingle standard, using UUENCODE instead of MACMIME.
- Base64 MAC Binary II
Specifies that outgoing Macintosh attachments are encoded using the MAC Binary II standard with the base-64 encoding scheme.
- UUENCODE MAC Binary II
Specifies that outgoing Macintosh attachments are encoded using the MAC Binary II standard with UNIX-style x-uue Content-Transfer-Encoding.
- After configuring the different options, click the Save button.