34.4 SMTP/MIME Switches

--smtp

Enables the GWIA to process SMTP messages. See Section 30.1, Configuring Basic SMTP/MIME Settings.

--nosmtpversion

Suppresses the GroupWise version and copyright date information that the GWIA typically responds with when contacted by another SMTP host or a telnet session.

--imip

Converts outbound GroupWise Calendar items into MIME text/calendar iCal objects and converts incoming MIME text/calendar messages into GroupWise Calendar items.

--aql

Determines the address qualification level. It specifies which GroupWise address components (domain.post_office.user) must be included as the user portion of a GroupWise user’s outbound Internet address (userhost). Valid options are auto, userid, po, and domain.

This switch is valid only if your system is not configured to use Internet-style addressing. For more information, see Section 29.0, Managing Internet Domains, Addressing, and Access, Or you have configured the GWIA to ignore Internet-style addressing. For more information, see Section 30.3, Configuring How the GWIA Handles Email Addresses.

--aqor

The user part of a GroupWise user’s outbound Internet address (user@host) can and sometimes must include the full Groupwise address (domain.post_office.user_name@host) in order to be unique. The ‑‑aqor switch configures the GWIA to move any GroupWise address components, except the user_name component, to the right side of the address following the at sign (@). In this way, GroupWise addressing components become part of the host portion of the outbound Internet address. The ‑‑aql switch specifies which components are included.

For example, if the ‑‑aqor switch is used (in conjunction with the ‑‑aql-domain switch), Bob Thompson’s fully qualified Internet address (headquarters.advertising.bob@novell.com) is resolved to bob@advertising.headquarters.novell.com for all outbound messages.

If the ‑‑aqor switch is used with the ‑‑aql-po switch, Bob’s Internet address is resolved to bob@advertising.novell.com for all outbound messages.

If you use the ‑‑aqor switch to move GroupWise domain or post office names to be part of the host portion on the right side of the address, you must provide a way for the DNS server to identify the GroupWise names. You must either explicitly name all GroupWise post offices and domains in your system as individual MX Records, or you can create an MX Record with wildcard characters to represent all GroupWise post offices and domains. For information about creating MX Records, see details found in RFC #974.

For details about this setting, see Section 30.3, Configuring How the GWIA Handles Email Addresses.

--ari

Enables or disables additional routing information that is put in the SMTP return address to facilitate replies. This switch might be needed in large systems with external GroupWise domains in which the external GroupWise users have not been configured in your local domain. Options include Never and Always. Most sites do not need to use this switch.

--blockrulegenmsg

In the GroupWise Admin console, you can control whether or not rule-generated messages are allowed to leave your GroupWise system by selecting or deselecting the Rule-Generated Messages options available in each class of service defined for the GWIA. This switch allows you to be specific in the types of rule-generated messages that are blocked.

In order for this switch to take effect, senders must be in a class of service where rule-generated messages are allowed. For more information, see Creating a Class of Service.

--dia

GroupWise supports both Internet-style addressing (user@host) and GroupWise proprietary addressing (user_name.post_office.domain). By default, the GWIA uses Internet-style addressing. See Section 30.3, Configuring How the GWIA Handles Email Addresses. You can use this switch to disable Internet-style addressing.

--displaylastfirst

By default, users’ display names are First Name Last Name. If you want users’ display names to be Last Name First Name, you can use the ‑‑displaylastfirst switch. This forces the display name format to be Last Name First Name, regardless of the preferred address format.

--dontreplaceunderscore

By default, the GWIA accepts addresses of the format:

firstname_lastname@internet_domain_name

Even though this is not an address format that the GroupWise Admin console included in the Allowed Address Formats list in the GroupWise Admin console for configuring Internet addressing, you can use this switch to prevent this address format from being accepted by the GWIA. For more information, see Section 29.3.2, Allowed Address Formats.

--fd822

Specifies a return address for GroupWise replies. A message that has been received by a GroupWise user through the GWIA and is replied to has this return address form. These switches cause the GWIA to produce a return address of the form foreign domain.type:"user host." Foreign domain can be any foreign domain you have configured and linked to the GWIA.

You can use the same foreign domain name for both the ‑‑fd822 switch and the ‑‑fdmime switch. You can specify multiple foreign domain and kind pairs by placing them in quotes. If multiple foreign domain and kind pairs are used, the first domain/kind pair is the return address for replies to messages received through the GWIA. The second domain/kind pair is checked to see what message format is used for old replies in the system. Up to four pairs can be specified with an 80-character limit.

This switch lets you change your foreign domain names in your GroupWise system and still have replies work. For example, if your foreign domain is called faraway and you added a foreign domain called Internet, you could use ‑‑fd822-"internet.nonmime smtp.nonmime." This causes replies to have a return address of internet.nonmime.:"user@host." The GWIA would also recognize faraway. This switch also lets you migrate from one foreign domain to another.

Most administrators do not need to use this switch.

--fdmime

Specifies a return address for GroupWise replies. A message that has been received by a GroupWise user through the GWIA and is replied to has this return address form. These switches cause the GWIA to produce a return address of the form foreign_domain.type:"user host." Foreign_domain can be any foreign domain you have configured and linked to the GWIA. Type can be either mime or nonmime.

You can use the same foreign domain name for both the ‑‑fd822 switch and the ‑‑fdmime switch.

You can specify multiple foreign domain and kind pairs by placing them in quotes. If multiple foreign domain and kind pairs are used, the first domain/kind pair is the return address for replies to messages received through the GWIA. The second domain/kind pair is checked to see what message format is used for old replies in the system. Up to four pairs can be specified with an 80-character limit.

This switch lets you change your foreign domain names in your GroupWise system and still have replies work. For example, if your foreign domain is called SMTP and you add a foreign domain called Internet, you can use ‑‑fdmime-"internet.mime smtp.mime." This causes replies to have a return address of internet.mime:"user@host." The GWIA also recognizes SMTP. This switch also lets you migrate from one foreign domain to another.

Most administrators do not need to use this switch.

--group

Turns on group expansion. By default, the GWIA does not expand groups, which means that recipients listed in groups do not receive incoming Internet messages that are addressed to groups.

Use this switch to expand groups into individual email addresses of the group members, so that the recipients in groups do receive incoming Internet messages addressed to groups. See Section 30.3, Configuring How the GWIA Handles Email Addresses.

See also --nickgroup.

--keepsendgroups

When constructing the MIME for outgoing messages, discard all users that expanded out of system distribution lists. Instead include a reference to the distribution list. This results in a smaller MIME and Reply to All list for the recipient. This setting corresponds with the GWIA’s ‑‑keepsendgroups switch.

--msstu

Replaces spaces with underscores (_) in the email address of the sender for outbound messages. For example, john smith becomes john_smith.

It does not replace spaces in the addresses of recipients.

--nickgroup

Turns on group expansion only for groups that have nicknames. By default, the GWIA does not expand groups, which means that recipients listed in groups do not receive incoming Internet messages that are addressed to groups. If you use the ‑‑group switch, the GWIA expands all groups.

Use this switch to expand only nicknamed groups. This means that recipients listed in nicknamed groups do receive incoming Internet messages that are addressed to the nickname of the group, but they do not receive incoming Internet messages that are addressed to groups that do not have nicknames. For information about nicknames, see Section 53.8, Managing User Email Addresses. See also Section 30.3, Configuring How the GWIA Handles Email Addresses.

See also --group.

--nomappriority

Disables the function of mapping an x-priority MIME field to a GroupWise priority for the message. By default, the GWIA maps x-priority 1 and 2 messages as high priority, x-priority 3 messages as normal priority, and x-priority 4 and 5 as low priority in GroupWise.

--notfamiliar

Configures the GWIA to not include the user’s familiar name, or display name, in the From field of the message’s MIME header. In other words, the From field is address rather than "familiar_name" address.

--realmailfrom

Configures the GWIA to use the real user in the Mail From field instead of having auto-forwards come from Postmaster and auto-replies come from Mailer-Daemon.

--attachmsg

Configures the GWIA to maintain the original format of any file type attachment.

--charsetconfidencelevel

Sets the confidence level at which you want the GWIA to use the detected character set rather than the default character set when no character set is specified. The GWIA tries to detect the character set based on the presence or absence of certain characters in the text. The default confidence level is 25, meaning that if the detection process returns a confidence level of 25 or above, the GWIA uses the detected character set, but if the confidence level is less than 25, the GWIA uses the default character set. Valid values range from 0 to 100.

--dbchar822

Configures the GWIA to map inbound non-MIME messages to another character set that you specify. The mapped character set must be an Asian (double-byte) character set.

--defaultcharset

Specifies what character set to use if no character set is specified in an incoming MIME-encoded message.

--defaultnonmimecharset

Specifies what character set to use if no character set is specified in an incoming message that is not MIME encoded. The default is US_ASCII.

--force7bitout

By default, the GWIA uses 8-bit MIME encoding for any outbound messages that are HTML-formatted or that contain 8-bit characters. If, after connecting with the receiving SMTP host, the GWIA discovers that the receiving SMTP host cannot handle 8-bit MIME encoded messages, the GWIA converts the messages to 7-bit encoding.

You can use the ‑‑force7bitout switch to force the GWIA to use 7-bit encoding and not attempt to use 8 bit MIME encoding. You should use this option if you are using a relay host that does not support 8-bit MIME encoding. See Section 30.1, Configuring Basic SMTP/MIME Settings.

--iso88591is

Configures the GWIA to map inbound MIME ISO-8859-1 messages to another character set that you specify.

--koi8

Configures the GWIA to map all outbound MIME messages to the KOI8 (Russian) character set.

--mime

Configures the GWIA to send outbound messages in MIME format rather than in RFC-822 format. If you’ve defined an RFC-822 non-GroupWise domain, users can still send RFC-822 formatted messages by using the RFC-822 domain in the address string when sending messages. For more information, see Section 5.8, Adding External Users to the GroupWise Address Book.

Removing the switch corresponds to enabling the Default Message Encoding: Basic RFC-822 setting in the GroupWise Admin console. See Section 30.4, Determining Format Options for Messages.

--noiso2022

Configures the GWIA to not use ISO-2022 character sets. ISO-2022 character sets provide 7-bit encoding for Asian character sets.

--nqpmt

Disables quoted printable message text for outbound messages. If this switch is turned on, messages are sent with Base64 MIME encoding, unless all the text is US-ASCII. If you use this switch you need to review the setting for the ‑‑wrap switch to ensure that message text wraps correctly. See Section 30.4, Determining Format Options for Messages.

--relayaddsignature

Appends the global signature to messages that are relayed through your GroupWise system (for example, messages from POP and IMAP clients) in addition to messages that originate within your GroupWise system. See Section 53.3, Adding a Global Signature to Users’ Messages.

--rt

Specifies the maximum number of threads that the GWIA uses when converting inbound messages from MIME or RFC-822 format to the GroupWise message format. The default setting is 4. The lowest valid setting is 1. There is no upper limit, but the larger the number of threads, the more resources are used, perhaps with little benefit unless a very large amount of data needs to be processed in a very small amount of time. See Section 30.4, Determining Format Options for Messages.

Multiple threading allows for more than one receive process to be running concurrently. A receive request is assigned to a single thread and is processed by that thread. If you anticipate heavy inbound message traffic, you can increase the number of threads to enhance the speed and performance of the GWIA. The number of threads is limited only by the memory resources of your server.

--st

Specifies the maximum number of threads that the GWIA uses when converting outbound messages from GroupWise message format to MIME or RFC-822 format. The default setting is 4. The lowest valid setting is 1. There is no upper limit, but the larger the number of threads, the more resources are used, perhaps with little benefit unless a very large amount of data needs to be processed in a very small amount of time. See Section 30.4, Determining Format Options for Messages.

Multiple threading allows for more than one send process to be running concurrently. A send request is assigned to a single thread and is processed by that thread. If you anticipate heavy outbound message traffic, you can increase the number of threads to enhance the speed and performance of the GWIA. The number of threads is limited only by the memory resources of your server.

--uueaa

Forces the GWIA to UUencode any ASCII text files attached to outbound RFC-822 formatted messages. This switch applies only if the ‑‑mime switch is not used. Without this switch, the GWIA includes the text as part of the message body. See Section 30.4, Determining Format Options for Messages.

--wrap

Sets the line length for outbound messages that do not use quoted printable or Base64 MIME encoding. This is important if the recipient’s email system requires a certain line length. See Section 30.4, Determining Format Options for Messages.

--flatfwd

Automatically strips out the empty message that is created when a message is forwarded without adding text, and retains the original sender of the message, rather than showing the user who forwarded it. This facilitates users forwarding messages from GroupWise to other email accounts. Messages arrive in the other accounts showing the original senders, not the users who forwarded the messages from GroupWise.

--delayedmsgnotification

Provides a notification message to users whose email messages cannot be immediately sent out across the Internet. This provides more noticeable notification to users than manually checking the Properties page of the sent item to see whether it has been sent.

See Section 30.1, Configuring Basic SMTP/MIME Settings.

--maxdeferhours

Specifies the number of hours after which the GWIA stops trying to send deferred messages. The default is 96 hours, or four days. You might prefer to receive an undeliverable notification sooner, perhaps in as little as 5 hours. A deferred message is any message that can’t be sent because of a temporary problem (host down, MX record not found, and so on). See Section 30.1, Configuring Basic SMTP/MIME Settings.

--msgdeferinterval

Specify in a comma-delimited list the number of minutes after which the GWIA retries sending deferred messages. The default is 20, 20, 20, 240. The GWIA interprets this list as follows: It retries 20 minutes after the initial send, 20 minutes after the first retry, 20 minutes after the second retry, and 240 minutes (4 hours) after the third retry. You might prefer for the fourth retry to occur sooner, perhaps in only 2 hours.

Thereafter, it retries according to the last retry interval until the number of hours specified in the Maximum Number of Hours to Retry a Deferred Message field is reached. You can provide additional retry intervals as needed. It is the last retry interval that repeats until the maximum number of hours is reached. See Section 30.1, Configuring Basic SMTP/MIME Settings.

--noesmtp

Disables ESMTP support in the GWIA.

--dsn

Enables Delivery Status Notification (DSN). The GWIA requests status notifications for outgoing messages and supplies status notifications for incoming messages. This requires the external email system to also support Delivery Status Notification. Currently, notification consists of two delivery statuses: successful and unsuccessful. See Section 30.2, Using Extended SMTP (ESMTP) Options.

--dsnage

The ‑‑dsnage switch specifies the number of days that the GWIA retains information about the external sender so that status updates can be delivered to him or her. For example, the default DSN age causes the sender information to be retained for 4 days. If the GWIA does not receive delivery status notification from the GroupWise recipient’s Post Office Agent (POA) within that time period, it deletes the sender information and the sender does not receive any delivery status notification. See Section 30.2, Using Extended SMTP (ESMTP) Options.

--p

Specifies how often, in seconds, the GWIA polls for outbound messages. The default,10 seconds, causes the GWIA to poll the outbound message folder every 10 seconds. See Section 30.1, Configuring Basic SMTP/MIME Settings.

--rd

Specifies the maximum number of threads used for processing SMTP receive requests (inbound messages). Each thread is equivalent to one connection. The default is 16 threads. Setting the receive threads to 0 stops messages from being received through the GWIA. There is no upper limit, but the larger the number of threads, the more resources are used, perhaps with little benefit. See Section 30.0, Configuring SMTP/MIME Services.

--sd

Specifies the maximum number of threads used for processing SMTP send requests (outbound messages). Each thread is equivalent to one connection. The default is 8 threads. Setting the send threads to 0 stops messages from being sent through the GWIA. There is no upper limit, but the larger the number of threads, the more resources are used, perhaps with little benefit. See Section 30.1, Configuring Basic SMTP/MIME Settings.

--killthreads

Configures the GWIA to quickly terminate any active send/receive threads when it restarts.

--smtpport (Linux only)

Changes the SMTP listen port from the default of 25. Use this switch only if the GWIA is receiving messages only from SMTP hosts that can be configured to connect to GWIA on a specified port.

--usedialup

Enables SMTP dial-up services.

--etrnhost

Specifies the IP address or DNS hostname of the mail server where your mail account resides at your Internet Service Provider. You should obtain this address from your Internet Service Provider.

--etrnqueue

Specifies your email domain as provided by your Internet Service Provider.

/dialuser (Windows Only)

Specifies the RAS Security user if you are using a Windows Remote Access Server (RAS) and the GWIA is not running on the same server as the RAS.

/dialpass (Windows Only)

Specifies the RAS Security user’s password if you are using a Windows Remote Access Server (RAS) and the GWIA is not running on the same server as the RAS.

--tc

Specifies how long the program waits for an SMTP command. The default is 2 minutes.

--td

Specifies how long the program waits for data from the receiving host. The default is 5 minutes.

--te

Specifies how long the program waits for the receiving host to establish a connection. The default is 5 minutes.

--tg

Specifies how long the program waits for the initial greeting from the receiving host. The default is 3 minutes.

--tr

Specifies how long the program waits for a TCP read. The default is 10 minutes.

--tt

Specifies how long the program waits for the receiving host to terminate the connection. The default is 5 minutes.

--mh

Specifies the IP address or DNS hostname of one or more relay hosts that you want the GWIA to use for outbound messages. Use a space to separate multiple relay hosts in a list.

The relay host can be part of your network or can reside at the Internet service provider’s site. This switch is typically used in firewall integration if you want one server, the specified relay host, to route all mail. See Section 30.1, Configuring Basic SMTP/MIME Settings.

--forceinboundauth

Ensures that the GWIA accepts messages only from remote SMTP hosts that use the AUTH LOGIN authentication method to provide a valid GroupWise user name and password. The remote SMTP hosts can use any valid GroupWise user name and password. However, for security reasons, we recommend that you create a dedicated GroupWise user account for remote SMTP host authentication.

--forceoutboundauth

Ensures that the GWIA sends messages only to remote SMTP hosts that are included in a gwauth.cfg text file. The remote SMTP hosts must support the AUTH LOGIN authentication method.

The gwauth.cfg file must reside in the domain\wpgate\gwia folder and use the following format:

domain_name authuser authpassword

For example:

smtp.novell.com remotehost novell

You can define multiple hosts in the file. Ensure that you include a hard return after the last entry.

If you use this switch, you need to include your GWIA as an entry in the gwauth.cfg file to enable status messages to be returned to GroupWise users. You can use any GroupWise user name and password for your GWIA’s authentication credentials. However, for security reasons, we recommend that you create a dedicated GroupWise user account for your GWIA.

--badmsg

Specifies where to send problem messages. Problem messages can be placed in the GWIA problem folder (gwprob), they can be sent to the postmaster, or they can be sent to both or neither. The values for this switch are move, send, both, and neither.

The move option specifies to place problem messages in the gwprob folder for the GWIA. The send option specifies to send the message as an attachment to the GWIA postmaster defined in the GroupWise Admin console (GWIA object > GroupWise > Administrators). The both option specifies to move the message to gwprob and send it to the postmaster. The neither option specifies to discard problem messages. The default when no switch is specified is move. See Section 30.6, Determining What to Do with Undeliverable Messages.

--fut

Forwards undeliverable messages to the specified host. See Section 30.6, Determining What to Do with Undeliverable Messages.

--mudas

Controls how much of the original message is sent back when a message is undeliverable. By default, only 2 KB of the original message is sent back. The value is specified in KB (8=8KB). See Section 30.6, Determining What to Do with Undeliverable Messages.

--disallowauthrelay

Prevents spammers from using GroupWise accounts to authenticate to the GWIA and using it as a relay host for their spam. It has no effect on normal GroupWise account usage in a GroupWise client or WebAccess. However, it does prevent users who access their GroupWise mailboxes from a POP or IMAP client from sending messages to users outside of the GroupWise system, because the GWIA identifies this activity as relaying.

--mbcount

Sets the number of messages that can be received from a single IP address in a given number of seconds before the GWIA denies access to its GroupWise system. It provides a form of system security to protect your system from mailbombs.

For example, with ‑‑mbcount set to 25 and ‑‑mbtime set to 60 seconds, if these limits are exceeded then the sender’s IP address is blocked from sending any more messages for the remainder of that 60 second window. The IP address of the sender is also displayed in the GWIA console. You can permanently restrict access to your system by that IP address through settings on the Access Control tab in the GroupWise Admin console (GWIA object > Access Control). By default, the mailbomb feature is turned off. To enable this feature, you must specify a value for mailbomb count and mailbomb time. See Mailbomb (Spam) Protection.

--mbtime

Specifies the mailbomb time limit in seconds. This switch works with the ‑‑mbcount switch to block access to your GroupWise system from unsolicited inundations of email. The default value is 10 seconds. See Mailbomb (Spam) Protection.

--rejbs

Prevents delivery of messages if the sender’s host is not authentic. When this switch is used, the GWIA refuses messages from a host if a DNS reverse lookup shows that a PTR record does not exist for the IP address of the sender’s host. See Mailbomb (Spam) Protection.

If this switch is not used, the GWIA accepts messages from any host, but displays a warning if the initiating host is not authentic.

--xspam

Flags messages to be handled by the client Junk Mail Handling feature if they contain an x-spam-flag:yes in the MIME header. See Customized Spam Identification.

--rbl

Lets you define the addresses of blacklist sites (free or fee-based) you want the GWIA to check for blacklisted hosts. If a host is included in a site’s blacklist, the GWIA does not accept messages from it.

This switch corresponds to the Blacklist Addresses list (GWIA object > Access Control > Blacklists). For details about this setting, see Real-Time Blacklists.