The following sections categorize and describe the switches that you can use to configure the Internet Agent’s SMTP/MIME settings:
The following switches enable SMTP and suppress version information display.
Enables the Internet Agent to process SMTP messages. See Section 46.1.1, Configuring Basic SMTP/MIME Settings.
Syntax: /smtp
Suppresses the GroupWise version and copyright date information that the Internet Agent typically responds with when contacted by another SMTP host or a telnet session.
Syntax: /nosmtpversion
The following switch enables iCal.
Converts outbound GroupWise Calendar items into MIME text/calendar iCal objects and converts incoming MIME text/calendar messages into GroupWise Calendar items.
Syntax: /imip
The following switches determine how the Internet Agent handles e-mail addresses:
Allows you to determine 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 (user@host). Valid options are auto, userid, po, and domain.
This switch is valid only if your system is not configured to use Internet-style addressing, as described in Section 45.0, Configuring Internet Addressing, or you have configured the Internet Agent to ignore Internet-style addressing, as described in Section 46.1.3, Configuring How the Internet Agent Handles E-Mail Addresses.
Syntax: /aql-option
Example: /aql-po
|
Option |
Description |
|---|---|
|
auto |
This option causes the gateway to include the addressing components required to make the user’s address unique. If a user ID is unique in a GroupWise system, the outbound address uses only the user_ID. If the post_office or domain.post_office components are required to make the address unique, these components are also included in the outbound address. The auto option is the default. |
|
userid |
This option requires the gateway to include only the user_ID in the outbound Internet address, even if the user ID is not unique in the system. If a recipient replies to a user whose user ID is not unique and no other qualifying information is provided, that reply cannot be delivered. |
|
po |
This option requires the gateway to include post_office.user_ID in every outbound address, regardless of the uniqueness or non-uniqueness of the user ID. |
|
domain |
This option requires the gateway to include the fully-qualified GroupWise address (domain.post office.user_ID) in every outbound address, regardless of the uniqueness or non-uniqueness of the user ID. This option guarantees the uniqueness of every outbound Internet address, and ensures that any replies are delivered. |
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_ID@host) in order to be unique. The /aqor switch instructs the Internet Agent to move any GroupWise address components, except the user_ID 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) would be 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 would be 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 46.1.3, Configuring How the Internet Agent Handles E-Mail Addresses.
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 and . Most sites do not need to use this switch.
Syntax: /ari-never|always
Example: /ari-never
In ConsoleOne, you can control whether or not rule-generated messages are allowed to leave your GroupWise system by selecting or deselecting the options available in each class of service defined for the Internet Agent. This switch allows you to be specific in the types of rule-generated messages that are blocked.
Syntax: /blockrulegenmsg-forward | reply | none | all
Example: /blockrulegenmsg-forward
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 Section 47.1.2, Creating a Class of Service.
GroupWise supports both Internet-style addressing (user@host) and GroupWise proprietary addressing (user_ID.post_office.domain). By default, the Internet Agent uses Internet-style addressing. See Section 46.1.3, Configuring How the Internet Agent Handles E-Mail Addresses.
You can use this switch to disable Internet-style addressing. With Internet-style addressing disabled, messages use the mail domain name in the Foreign ID field in ConsoleOne (Internet Agent object > GroupWise > Identification) for the domain portion of a user’s Internet address. The Internet Agent continues to support user and post office aliases in either mode.
Syntax: /dia
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.
Syntax: /displaylastfirst
By default, the Internet Agent accepts addresses of the format:
firstname_lastname@internet_domain_name
Even though this is not an address format included in the Allowed Address Formats list in ConsoleOne for configuring Internet addressing, as described in Section 45.1.5, Allowed Address Formats, you can use this switch to prevent this address format from being accepted by the Internet Agent.
Syntax: /dontreplaceunderscore
Specifies a return address for GroupWise replies. A message that has been received by a GroupWise user through the Internet Agent and is replied to has this return address form. These switches cause the Internet Agent 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 Internet Agent.
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 Internet Agent. 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 Internet Agent 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.
Syntax: /fd822-foreign_domain.type
Example: /fd822-Internet.nonmime
Specifies a return address for GroupWise replies. A message that has been received by a GroupWise user through the Internet Agent and is replied to has this return address form. These switches cause the Internet Agent 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 Internet Agent. 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 Internet Agent. 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 Internet Agent also recognizes SMTP. This switch also lets you migrate from one foreign domain to another.
Most administrators do not need to use this switch.
Syntax: /fdmime-foreign_domain.type
Example: /fdmime-Internet.mime
Turns on distribution list expansion. By default, the Internet Agent does not expand distribution lists, which means that recipients listed in distribution lists do not receive incoming Internet messages that are addressed to distribution lists.
Use this switch to expand distribution lists into individual e-mail addresses of the distribution list members, so that the recipients in distribution lists do receive incoming Internet messages addressed to distribution lists. See Section 46.1.3, Configuring How the Internet Agent Handles E-Mail Addresses.
Syntax: /group
See also /nickgroup.
Prevents the Internet Agent from expanding distribution lists on messages going to external Internet users so that the SMTP header does not become too large.
Syntax: /keepsendgroups
Instructs the Internet Agent to map spaces to underscores in user addresses for outbound messages. For example, john smith becomes john_smith.
Syntax: /msstu
Turns on distribution list expansion only for distribution lists that have nicknames. By default, the Internet Agent does not expand distribution lists, which means that recipients listed in distribution lists do not receive incoming Internet messages that are addressed to distribution lists. If you use the /group switch, the Internet Agent expands all distribution lists.
Use this switch to expand only nicknamed distribution lists. This means that recipients listed in nicknamed distribution lists do receive incoming Internet messages that are addressed to the nickname of the distribution list, but they do not receive incoming Internet messages that are addressed to distribution lists that do not have nicknames. For information about nicknames, see Section 14.7, Managing User E-Mail Addresses. See also Section 46.1.3, Configuring How the Internet Agent Handles E-Mail Addresses.
Syntax: /nickgroup
See also /group.
Disables the function of mapping an x-priority field to a GroupWise priority for the message. By default, the Internet Agent 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.
Syntax: /nomappriority
Instructs the Internet Agent to not include the user’s familiar name, or display name, in the field of the message’s MIME header. In other words, the field is address rather than "familiar_name" address.
Syntax: /notfamiliar
Instructs the Internet Agent to use the real user in the field instead of having auto-forwards come from Postmaster and auto-replies come from Mailer-Daemon.
Syntax: /realmailfrom
The following switches determine how the Internet Agent formats and encodes inbound and outbound e-mail messages:
For more information, see Section 7.4, MIME Encoding.
Instructs the Internet Agent to maintain the original format of any file type attachment.
Syntax: /attachmsg
Sets the confidence level at which you want the Internet Agent to use the detected character set rather than the default character set when no character set is specified. The Internet Agent 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 Internet Agent uses the detected character set, but if the confidence level is less than 25, the Internet Agent uses the default character set. Valid values range from 0 to 100.
Syntax: /charsetconfidencelevel-number
Example: /charsetconfidencelevel-35
Instructs the Internet Agent 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.
Syntax: /dbchar822-charset
Example: /dbchar822-shift_jis
Specifies what character set to use if no character set is specified in an incoming MIME-encoded message.
Syntax: /defaultcharset-charset
Example: /defaultcharset-iso-8859-1
For readability when the character set name includes hyphens (-), you can use an equal sign (=) as the delimiter between the switch and its setting.
Example: /defaultcharset=iso-8859-1
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.
Syntax: /defaultnonmimecharset-charset
Example: /defaultnonmimecharset-iso-8859-1
For readability when the character set name includes hyphens (-), you can use an equal sign (=) as the delimiter between the switch and its setting.
Example: /defaultnonmimecharset=iso-8859-1
By default, the Internet Agent 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 Internet Agent discovers that the receiving SMTP host cannot handle 8-bit MIME encoded messages, the Internet Agent converts the messages to 7-bit encoding.
You can use the /force7bitout switch to force the Internet Agent 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 46.1.1, Configuring Basic SMTP/MIME Settings.
Syntax: /force7bitout
Instructs the Internet Agent to map inbound MIME ISO-8859-1 messages to another character set that you specify.
Syntax: /iso88591is-charset
Example: /iso88591is-big5
Instructs the Internet Agent to map all outbound MIME messages to the KOI8 (Russian) character set.
Syntax: /koi8
Instructs the Internet Agent to send outbound messages in MIME format rather than in RFC-822 format. If you’ve defined an RFC-822 non-GroupWise domain, as described in Section 6.8, Adding External Users to the GroupWise Address Book, users can still send RFC-822 formatted messages by using the RFC-822 domain in the address string when sending messages. Removing the switch corresponds to enabling the Default Message Encoding: Basic RFC-822 switch in ConsoleOne. See Section 46.1.4, Determining Format Options for Messages.
Syntax: /mime
Instructs the Internet Agent to not use ISO-2022 character sets. ISO-2022 character sets provide 7-bit encoding for Asian character sets.
Syntax: /noiso2022
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 46.1.4, Determining Format Options for Messages.
Syntax: /nqpmt
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 14.3, Adding a Global Signature to Users’ Messages
Syntax: /relayaddsignature
Specifies the maximum number of threads that the Internet Agent uses when converting inbound messages from MIME or RFC-822 format to the GroupWise message format. The default setting is 4. See Section 46.1.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 Internet Agent. The number of threads is limited only by the memory resources of your server.
Syntax: /rt
Specifies the maximum number of threads that the Internet Agent uses when converting outbound messages from GroupWise message format to MIME or RFC-822 format. The default setting is 4. See Section 46.1.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 Internet Agent. The number of threads is limited only by the memory resources of your server.
Syntax: /st
Forces the Internet Agent 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 Internet Agent includes the text as part of the message body. See Section 46.1.4, Determining Format Options for Messages.
Syntax: /uueaa
Sets the line length for outbound messages that do not use quoted printable or Base64 MIME encoding. This is important if the recipient’s e-mail system requires a certain line length. See Section 46.1.4, Determining Format Options for Messages.
Syntax: /wrap-line_length
Example: /wrap-72
The following switches configure how the Internet Agent handles forwarded and deferred messages:
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 e-mail accounts. Messages arrive in the other accounts showing the original senders, not the users who forwarded the messages from GroupWise.
Syntax: /flatfwd
also /nodelayedmsgnotification
Specifies the number of hours after which the Internet Agent stops trying to send deferred messages. The default is 96 hours, or four days. A deferred message is any message that can’t be sent because of a temporary problem (host down, MX record not found, and so forth). See Section 46.1.1, Configuring Basic SMTP/MIME Settings.
Syntax: /maxdeferhours-hours
Example: /maxdeferhours-48
Specify in a comma-delimited list the number of minutes after which the Internet Agent retries sending deferred messages. The default is 20, 20, 20, 240. The Internet Agent 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. Thereafter, it retries every 240 minutes until the number of hours specified in the 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 46.1.1, Configuring Basic SMTP/MIME Settings.
Syntax: /msgdeferinterval-minutes,minutes...,minutes
Example: /msgdeferinterval-10,10,10,120
The following switches configure the Internet Agent’s Extended SMTP (ESMTP) settings:
Disables ESMTP support in the Internet Agent.
Syntax: /noesmtp
Enables Delivery Status Notification (DSN). The Internet Agent requests status notifications for outgoing messages and supplies status notifications for incoming messages. This requires the external e-mail system to also support Delivery Status Notification. Currently, notification consists of two delivery statuses: successful and unsuccessful. See Section 46.1.2, Using Extended SMTP (ESMTP) Options.
Syntax: /dsn
The /dsnage switch specifies the number of days that the Internet Agent 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 Internet Agent 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 46.1.2, Using Extended SMTP (ESMTP) Options.
Syntax: /dsnage
The following switches configure the Internet Agent’s SMTP send/receive cycle and threads:
Specifies how often, in seconds, the Internet Agent polls for outbound messages. The default,10 seconds, causes the Internet Agent to poll the outbound message directory every 10 seconds. See Section 46.1.1, Configuring Basic SMTP/MIME Settings.
Syntax: /p-seconds
Example: /p-5
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. See Section 46.1.1, Configuring Basic SMTP/MIME Settings.
Syntax: /rd-number_of_threads
Example: /rd-20
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. See Section 46.1.1, Configuring Basic SMTP/MIME Settings.
Syntax: /sd-number_of_threads
Example: /sd-12
Instructs the Internet Agent to quickly terminate any active send/receive threads when it restarts.
Syntax: /killthreads
Changes the SMTP listen port from the default of 25. Use this switch only if the Internet Agent is receiving messages only from SMTP hosts that can be configured to connect to Internet Agent on a specified port.
SMTP dial-up services can be used when you don’t require a permanent connection to the Internet and want to periodically check for mail messages queued for processing. The following switches can be used when configuring dial-up services. For more information about dial-up services, see Section 46.1.7, Configuring SMTP Dial-Up Services.
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. See Enabling Dial-Up Services.
Syntax: /etrnhost-address
Example: /etrnhost-172.16.5.18
Specifies your e-mail domain as provided by your Internet Service Provider. See Enabling Dial-Up Services.
Syntax: /etrnqueue-email_domain
Example: /etrnqueue-novell.com
Specifies the RAS Security user if you are using a Windows Remote Access Server (RAS) and the Internet Agent is not running on the same server as the RAS.
Syntax: /dialuser-username
Example: /dialuser-rasuser
Specifies the RAS Security user’s password if you are using a Windows Remote Access Server (RAS) and the Internet Agent is not running on the same server as the RAS.
Syntax: /dialpass-password
Example: /dialpass-raspassword
The following switches specify how long SMTP services waits to receive data that it can process. After the time expires, the Internet Agent might give a TCP read/write error. Leave these switches at the default setting unless you are experiencing a problem with communication.
Specifies how long the program waits for an SMTP command. The default is 2 minutes.
Syntax: /tc-minutes
Example: /tc-3
Specifies how long the program waits for data from the receiving host. The default is 5 minutes.
Syntax: /td-minutes
Example: /td-2
Specifies how long the program waits for the receiving host to establish a connection. The default is 5 minutes.
Syntax: /te-minutes
Example: /te-2
Specifies how long the program waits for the initial greeting from the receiving host. The default is 3 minutes.
Syntax: /tg-minutes
Example: /tg-2
Specifies how long the program waits for a TCP read. The default is 10 minutes.
Syntax: /tr-minutes
Example: /tr-2
Specifies how long the program waits for the receiving host to terminate the connection. The default is 5 minutes.
Syntax: /tt-minutes
Example: /tt-2
The following switch configures whether or not the Internet Agent uses a relay host.
Specifies the IP address or DNS hostname of one or more relay hosts that you want the Internet Agent 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 46.1.1, Configuring Basic SMTP/MIME Settings.
Syntax: /mh-address
Example: /mh-172.16.5.18
The Internet Agent supports SMTP host authentication for both inbound and outbound message traffic. The following switches are used with inbound and outbound authentication:
Ensures that the Internet Agent accepts messages only from remote SMTP hosts that use the AUTH LOGIN authentication method to provide a valid GroupWise user ID and password. The remote SMTP hosts can use any valid GroupWise user ID and password. However, for security reasons, we recommend that you create a dedicated GroupWise user account for remote SMTP host authentication.
Syntax: /forceinboundauth
NOTE:Using the --forceinboundauth switch overrides the Prevent Message Relaying setting for the GWIA in ConsoleOne for POP and IMAP users. To completely prevent message relaying when using the --forceinboundauth switch, you must also specify the --disallowauthrelay switch.
Ensures that the Internet Agent 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 directory and use the following format:
domain_name authuser authpassword
For example:
smtp.novell.com remotehost novell
You can define multiple hosts in the file. Make sure you include a hard return after the last entry.
If you use this switch, you need to include your Internet Agent as an entry in the gwauth.cfg file to enable status messages to be returned to GroupWise users. You can use any GroupWise user ID and password for your Internet Agent’s authentication credentials. However, for security reasons, we recommend that you create a dedicated GroupWise user account for your Internet Agent.
Syntax: /forceoutboundauth
The following switches determine how the Internet Agent handles undeliverable messages:
Specifies where to send problem messages. Problem messages can be placed in the Internet Agent problem directory (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 directory for the Internet Agent. The send option specifies to send the message as an attachment to the Internet Agent postmaster defined in ConsoleOne (Internet Agent object > ). 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 46.1.6, Determining What to Do with Undeliverable Messages.
Syntax: /badmsg-move|send|both|neither
Example: /badmsg-both
Forwards undeliverable messages to the specified host. See Section 46.1.6, Determining What to Do with Undeliverable Messages.
Syntax: /fut-host
Example: /fut-novell.com
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 46.1.6, Determining What to Do with Undeliverable Messages.
Syntax: /mudas-KB
Example: /mudas-16
Multiple unsolicited messages (sometimes called a mailbomb or spam) from the Internet can potentially harm your GroupWise messaging environment. At the least, it can be annoying to your users. You can use the following switches to help protect your GroupWise system from malicious, accidental, and annoying attacks:
Prevents spammers from using GroupWise accounts to authenticate to the Internet Agent and use it as a relay host for their spam. It has no effect on normal GroupWise account usage. 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.
Syntax: /disallowauthrelay
Sets the number of messages that can be received from a single IP address in a given number of seconds before the Internet Agent 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 the sender’s IP address is blocked from sending any more messages. The IP address of the sender is also displayed in the Internet Agent console. You can permanently restrict access to your system by that IP address through settings on the Access Control page in ConsoleOne (Internet Agent 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 Section 47.2.4, Mailbomb (Spam) Protection.
Syntax: /mbcount-number
Example: /mbcount-25
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 e-mail. The default value is 10 seconds. See Section 47.2.4, Mailbomb (Spam) Protection.
Syntax: /mbtime-seconds
Example: /mbtime-60
Prevents delivery of messages if the sender’s host is not authentic. When this switch is used, the Internet Agent 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 Section 47.2.4, Mailbomb (Spam) Protection.
If this switch is not used, the Internet Agent accepts messages from any host, but displays a warning if the initiating host is not authentic.
Syntax: /rejbs
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 Section 47.2.5, Customized Spam Identification.
Syntax: /xspam
Lets you define the addresses of blacklist sites (free or fee-based) you want the Internet Agent to check for blacklisted hosts. If a host is included in a site’s blacklist, the Internet Agent does not accept messages from it.
Syntax: /rbl-blackholes.mail-abuse.org,bl.spamcop.net
This switch corresponds to the Blacklist Addresses list (Internet Agent object > Access Control > Blacklists). For details about this setting, see Section 47.2.1, Real-Time Blacklists.