CONFIGURING THE PEER DOMAIN ATTRIBUTES
To configure the different Peer Domain parameters, do the following:
-
Enter the domain or sub-domain that has the specified capabilities (e.g. ima.com).
-
Tick the
Accept Mail
option. When this option is enabled, it allows the peer domain currently selected to receive incoming mail.
-
Tick the
Transmit Mail
option. When this option is enabled, it allows the peer domain currently selected to send outgoing messages. If this option is disabled, the Output Channel will bounce any message destined to this host back to the original sender.
-
Tick the
Queue mail before attempting delivery
option. When this option is enabled, it tells the SMTPC module to queue the messages before any of them is delivered.
-
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
Convert non-MAC file to MAC format
option. This option, when enabled, converts 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. This option should be activated 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. This option should be enabled 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 this option is enabled, the message will 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 this option is enabled, the message will contain only one attachment, which is the NotesMail NSF file.
-
Select a Native Attachment encoding method. Tick the
MIME
radio button to specify that non-Apple attachments are to be encoded using the MIME standard. Ticking the
UUENCODE
radio button
will specify that non-Apple attachments are to be encoded using the older UUENCODE format.
-
Select an Apple attachment encoding method.
-
Tick the
MACMIME AppleSingle
radio button to
specify that outgoing Macintosh attachments are to be encoded using the MACMIME AppleSingle standard.
-
Tick the
MACMIME AppleDouble
radio button to specify that outgoing Macintosh attachments are to be encoded using the MACMIME AppleDouble standard.
-
Tick the
MACMIME BinHex
radio button to specify that outgoing Macintosh attachments are encoded using the BinHex 4.0 standard specified in RFC-1741.
-
Tick the
UUENCODE AppleSingle
radio button to specify that outgoing Macintosh attachments are to be encoded using the AppleSingle standard, using UUENCODE instead of MACMIME.
-
Tick the
Base64 MAC Binary II
radio button to specify that outgoing Macintosh attachments are encoded using the MAC Binary II standard with the base-64
encoding scheme.
-
Tick the
UUENCODE MAC Binary II
radio button to specify 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 Add
button.