The GroupWise Internet Agent includes the enhancements and new features listed below. Changes included in GroupWise 6.5 are indicated by (v6.5). Changes included in GroupWise 6.5 Support Pack 1 are indicated by (v6.5 SP1).
You can use SSL to secure connections between the Internet Agent and Post Office Agents (POAs). SSL options are configured on the Internet Agent object's Network Address page and SSL Settings page in ConsoleOne.
For more information, see "Securing Internet Agent Connections Via SSL" in "Internet Agent" in the GroupWise 6.5 Administration Guide.
You can now disable, enable, or require (force) SSL connections for POP and IMAP clients. If SSL is enabled, the POP/IMAP client determines whether or not an SSL connection is used. If SSL is disabled, no SSL connections are used. If SSL is required, only SSL connections are allowed.
SSL options are configured on the Internet Agent object's Network Address and SSL Settings pages in ConsoleOne.
For more information, see "Securing Internet Agent Connections Via SSL" in "Internet Agent" in the GroupWise 6.5 Administration Guide.
The Internet Agent supports SMTP host authentication for both outbound and inbound message traffic.
With outbound authentication, you can ensure that the Internet Agent is able to send messages to other SMTP hosts that require proper authentication credentials before they accept messages. In addition, you can limit the Internet Agent to sending messages only to hosts that require authentication.
With inbound authentication, you can require other SMTP hosts to supply proper authentication credentials (GroupWise username and password) before the Internet Agent accepts messages from them. This also applies to POP3/IMAP4 clients.
For more information about SMTP host authentication, see "Configuring SMTP Host Authentication" in "Internet Agent" in the GroupWise 6.5 Administration Guide.
If you use a relay host for outbound messages, you can use a route.cfg file to specify SMTP hosts that you want to directly send outbound messages to. Whenever a message is addressed to a user at a host that is included in the route.cfg file, the Internet Agent sends the message directly to the host rather than to the relay host.
The route.cfg file can also be used for other purposes, including:
For more information about the route.cfg file, see "Enabling SMTP Relaying" in "Internet Agent" in the GroupWise 6.5 Administration Guide.
The default number of SMTP threads has been increased from 2 send threads and 4 receive threads to 8 send threads and 16 receive threads. This applies to any new Internet Agent installation. It also applies to updated Internet Agent installations if the /copyonly startup switch is not being used.
The send and receive thread settings are configured on the Internet Agent object's SMTP/MIME Settings page in ConsoleOne.
For more information about the SMTP send and receive threads, see "Configuring SMTP/MIME Services" in "Internet Agent" in the GroupWise 6.5 Administration Guide.
Many organizations, such as Mail Abuse Prevention System (MAPS), Open Relay DataBase (ORDB), and SpamCop, provide lists of IP addresses that are known to be open relay hosts or spam hosts. You can use the real-time blacklists provided by these sites to protect your users from offensive spam.
You define blacklist sites through the Internet Agent object's Access Control Blacklists page in ConsoleOne.
For more information about using real-time blacklists, see "Blocking Unwanted E-Mail" in "Internet Agent" in the GroupWise 6.5 Administration Guide.
You can specify the number of hours after which the Internet Agent stops trying to send deferred messages. A deferred message is any message that could not be sent because of a temporary problem (host down, MX record not found, and so forth).
For the first hour of the specified time, the Internet Agent tries resending the message every 20 minutes. After the first hour, it tries resending the message every four hours. For example, if you specify 10 hours, the Internet Agent tries resending the message at 20 minutes, 40 minutes, 1 hour, 5 hours, and 9 hours. After the 10 hours has expired, it returns an Undeliverable status to the sender.
You configure this option through the Internet Agent object's SMTP/MIME Settings page in ConsoleOne.
For more information about the deferred message retry setting, see "Configuring SMTP/MIME Services" in "Internet Agent" in the GroupWise 6.5 Administration Guide.
In Verbose logging mode, the Internet Agent logs more information, such as:
Logging modes are configured on the Internet Agent object's Log Settings page in ConsoleOne.
For more information about logging, see "Using Internet Agent Log Files" in "Internet Agent" in the GroupWise 6.5 Administration Guide.
ConsoleOne creates a blocked.txt file that includes all the hosts that have been added to the Prevent Messages From exceptions list (Default Class of Service > SMTP Incoming > Prevent Messages From). This list is used to define the hosts or domains you do not want to receive messages from.
You can manually edit the blocked.txt file to add or remove hosts. To maintain consistency for your system, you can also copy the list to other Internet Agent installations.
The blocked.txt file is created in the domain\wpgate\gwia directory.
For more information about the blocked.txt file, see "Configuring SMTP/MIME Services" in "Internet Agent" in the GroupWise 6.5 Administration Guide.
When the Internet Agent restarts, it rereads all of its configuration files. This includes gwia.cfg, blocked.txt, gwauth.cfg, and route.cfg.
Changing Internet Agent information in ConsoleOne causes an automatic restart of the Internet Agent to ensure that it knows about the changed information. If you change the configuration files, you can use the new restart option (F6 - Restart) in the Internet Agent console to manually restart the Internet Agent so that it recognizes the changes.
For more information about the Internet Agent console, see "Monitoring Internet Agent Operations" in "Internet Agent" in the GroupWise 6.5 Administration Guide.