CONFIGURING CC:MAIL OPTIONS
To configure the list of cc:Mail parameters as seen on your screen, do the following procedure:

  1. Select your default MIME encoding from the drop-down list.

    When encoding cc:Mail messages, CCOUT uses the MIME encoding information configured into Internet Exchange (see MIME table configurations for details). When a non-Macintosh file with an unknown or non-existent extension is encountered, it is encoded using the default binary encoding. You must choose the appropriate entry based upon the capabilities of those sites to which the gateway communicates most of the time. Base64 is preferable for communicating with MIME-capable sites. UUENCODE should be specified as the default encoding method if Internet Exchange will communicate with non-MIME compliant sites. However, since UENCODE/UUDECODE are not part of the MIME specification, their widespread use are being discouraged.

  2. Select your addressing separator from the drop-down list.

    The allowed entries are the dot (.) and underscore (_). When constructing Internet addresses for cc:Mail users without an explicit entry in the Directory Server, all spaces are usually converted to underscores. Since some sites prefer to use dots instead of underscores, this option allows the administrator to choose between the two. Following are some examples of how an email address for someone named John Doe is registered in the Post Office:

  3. John_Doe_at_Main_PO
      or
    John.Doe.at.Main.PO

    NOTE: If an existing separator is found in the name to be translated, this will be doubled. For example, if the separato in use is the underscore:


    John_Doe

    becomes

    John__Doe

    NOTE: Spaces are not valid in Internet mail addresses.

  4. Specify a value for the the Internet Return receipt header. Using the default value of Return-receipt-to, x-inex-return-receipt-to allows compatibility with the UNIX Sendmail program and the Lotus SMTPLINK product. However, there are problems involved with this approach. Sendmail uses the header to request notification of message delivery at the transport level, while SMTPLINK uses it to signify that the message has been opened (and possibly read) by the recipient.

    Choosing a different value will not only solve this problem but, will also ensure that the return-receipt function is portable only between the Internet Exchange cc:Mail connector that used the same value. Specify your desired Uuencode tag. By default, Internet Exchange generates MIME uuencode messages with x-uue in the Content-transfer-encoding header. However, it is reported that some email agents require x-uuencode in their header instead. Use this entry to change the name of the uuencode reader.

  5. Set the MIME Preamble File option. MIME messages contain an optional MIME preamble area, where a short message useful to non-MIME gateways and user agents can be stored. This section resides between the RFC822 headers and the first MIME body part. If this option is set to point to an existing file, the contents of this file will be used as the MIME preamble in outgoing messages. If this option is disabled or set to a non-existent file, no preamble is used.
  6. Set the Bounce Sender option. When a message is bounced, the user defined in this field receives a bounced notification message for undeliverable mail generated by the MTA. The default value, Postmaster (MAILER-DAEMON), is highly recommended.
  7. Specify the RFC 822 Header Placement option. This option determines where the RFC822 headers will be attached to an incoming message. It can be attached at the top or at the bottom of the message body.
  8. Enter your preferred value for the Tab expansions (spaces equivalent) option. The number of spaces used to replace a single tab. For example, if this parameter is configured to 8, eight spaces will be used instead of a tab for all incoming text messages. A value of zero indicates no tab expansion will be used.
  9. Enable the Force Native option. By enabling this option, inbound Macintosh attachments (in BinHex, MacMIME, or UUENCODED AppleSingle format) are stripped of their header and resource fork before being attached to messages in the cc:Mail Post Office. If this is not done, some applications (like Excel 4 for Windows) may refuse to open the resulting file.
  10. Enable the Force Apple option. By enabling this option, inbound non-Macintosh attachments are given a dummy header and converted into AppleSingle cc:Mail format before being attached to messages in the cc:Mail Post Office. The type and creator are obtained from the MIME table prepared with the Configure MIME box.
  11. Tick the check box if you wish to enable RFC1522 support. When this option is enabled, CCOUT encodes any message header containing non-ASCII as defined by RFC1522 (MIME part II, Message Header Extensions for Non-ASCII Text).
  12. Select your preferred encoding method from the drop-down list. This option allows the administrator to choose between Quoted-printable or Base 64 for encoding non-ASCII characters in message headers. We suggest that you use Quoted-printable if the gateway is to handle European characters, while Base 64 should be used on Japanese or any double-byte character set environments.
  13. Set the Scan outbound MAC.HQX files option. For outgoing messages, this option checks whether the message body contains files in BinHex format. If such files are found, it uses the information in the header to prepare the proper MIME headers.
  14. Set the Warning if empty message option. This option prompts empty outbound messages to trigger a warning to the local postmaster. The warning text is: Warning: Your message went out the cc:Mail environment with an empty message body. If you intentionally sent an empty message, disregard this warning. If you included a reply in an old header body part, it was purged. Key headers from the message that was sent follow.
  15. Set the Try reverse separator option. This option allows both address separators (dot/underscore) to be tried with incoming addresses during default address translation. This is useful if the local site changes its preferred separator and still wishes addresses with the old separator to be valid.
  16. Set the Include RFC822 headers option. In a normal operation, CCIN discards RFC822 headers after messages have been imported into cc:Mail. This option allows all such headers to be retained in messages as separate attachments.
  17. Set the Include MIME headers option. In a normal operation, CCIN discards MIME body part headers after they have been processed. This option allows all such headers to be retained in messages as separate attachments. This is not normally required, but it can be useful if the incoming message cannot be identified. A separate text item will be added for each MIME body part, which can result in a large number of MIME header text items.
  18. Set the Delete outgoing headers option. When a MIME message is imported into cc:Mail, and either RFC822 and/or MIME headers are included, extra text items are created containing these headers. When such messages are re-sent to the Internet, these text items are not useful and often confuse the recipient. Enabling this option automatically deletes these header attachments from outgoing messages.
  19. Set the Use Reply-to header option. This option makes use of the Reply-to: field by copying it to the From: field on all incoming mail. Otherwise, this information is lost as cc:Mail has no concept of Reply-to: fields. The use of this option will result in the loss of the original From: field, if this field is different from the Reply-to field.
  20. Set the Use Resent-from header option. If a Resent-From: header is present in the incoming message, it is used for the cc:Mail From: field instead of the From: header. This option allows messages forwarded through some UNIX mailers like Pine to be turned on or off as needed. Using this option will result in the loss of the original From: field, if this field is different from the Resent-From: field.
  21. Set the Use remote PO names option. This option determines whether outgoing cc:Mail addresses with no entry in the Directory Server appear as: user_at_Post_Office@host.domain or user@host.domain.
  22. The second format is much tidier. To ensure that replies to this message will be returned to the sender, there must be an entry in the gateway Post Office for the user. This is easily accomplished by using the Lotus ADE (Automatic Directory Exchange). If this is not the case, incoming messages to these addresses are bounced since cc:Mail has no way to route the messages internally to the correct recipient.

  23. Enable the Include cc:Mail names in addresses option. Turning off this option removes the cc:Mail user name from the Address field, leaving only the user's Internet address. The default is ON. For example: Name included: John_Doe@jade.net (John Doe) Name not included: John_Doe@jade.net
  24. Enable the Reject Down Stream PO to send option. Enabling this option prevents users at the downstream post office to send messages to the Internet. Thus, only users from local Post Offices can send messages to the Internet.
  25. Set the Permit users to send by default option. If send permission is not set for a user in the Alias Database and Directory Database, this option determines whether that user can send messages to the Internet.
  26. Set the Permit users to receive by default option. If receive permission is not set for a user in the alias database, this option determines whether that user can receive messages from the Internet.
  27. Enable the Copy bounces to postmaster option. Enabling this option directs all bounced messages to the local postmaster and to the original sender of the message. This can be useful in monitoring problems.
  28. Enable the Masking outbound cc:Mail mailing list option. If this option is enabled, CCOUT will ignore any mailing list entry when generating message headers. This means that if a message is addressed to a mailing list or to addresses external to the mailing list, only the mailing list recipients will be able to see the entire list of recipients, while the external recipients will not receive an indication that the message was also sent to a cc:Mail mailing list. This option is also useful for avoiding duplicate replies being sent to the same cc:Mail recipient if that recipient is also addressed in the cc:Mail mailing list.

  29. Enable the Mapping 'postmaster' from user alias option. Messages addressed to the Postmaster are sent by default to the local mail postmaster, which is defined in the Post Office setup screen. The Internet address field for the prospective postmaster in the Users setup screen must be set as postmaster. Enabling this option allows users to map postmaster to another user if no valid entry can be mapped from the user aliases, Internet Exchange uses the local mail postmaster name for mail delivery.
  30. After configuring the different options, click the Submit button.

NOTE: You are not required to fill up all the text boxes but, parameters with default value must be configured.