Configuring Exchange Server Connection
QSS Exchange Anti-Spam Toolkit needs to have a valid connection to Exchange Server before any functions can be used. The Exchange Server Connection page will appear the first time the QSS Exchange Anti-Spam Toolkit web console is launched, or at any time if it cannot connect to Exchange.
To access the web console, use the Exchange Anti-Spam Toolkit shortcut on the start menu, or access the http://localhost/AntiSpamToolkit URL from a browser on the server.
Alternative URLs Required for SSL/TLS Access
If Require SSL is enabled in Exchange, the default URL shown above and the shortcut may not work.
Connecting to Exchange using a secure TLS connection is recommended and should always be used for remote access to QSS Exchange Anti-Spam Toolkit. Using the HTTP (not HTTPS) URL above is acceptable when accessing the console directly from the Exchange server. On a default installation of Exchange, insecure HTTP connections are enabled and Require SSL is not enabled.
Depending on how you have configured SSL/TLS in Exchange (e.g. for OWA), you may need to use a different URL to be able to access QSS Exchange Anti-Spam Toolkit without browser security warnings, or to access it at all.
The following URLs should be tried directly from a browser on the Exchange server to establish the access URL for QSS Exchange Anti-Spam Toolkit, depending on your Exchange configuration:
In the above URLs, <servername> should be replaced with the actual name of the Exchange server. The URLs using the actual server name (instead of localhost) should also be accessible remotely (i.e. from other machines on the network).
Special SSL/TLS configuration is not required for QSS Exchange Anti-Spam Toolkit. Configuring Exchange OWA and other Exchange services to enable SSL/TLS connections will also enable QSS Exchange Anti-Spam Toolkit to be accessed via TLS. If QSS Exchange Anti-Spam Toolkit can be accessed via any of the HTTPS URLs shown above without browser security warnings, then HTTPS is correctly enabled in Exchange.
Configuring Exchange Server Name
Once the web console can be successfully accessed, the Exchange server name can be configured. In most instances, the Exchange Server name should be pre-populated, however it should be checked.
The Exchange server name must be specified as the fully-qualified DNS name (FQDN) of the Exchange server, for example, servername.domain.local.
Configuring Service Account Credentials
QSS Exchange Anti-Spam Toolkit requires a domain account which is a member of the Exchange Organization Administrators group, to be able to read and modify Exchange Server anti-spam settings. The Service Account is also used by the QSS Sender Score Agent.
Account credentials, including the password, must be specified. The credentials you provide are stored securely in Windows Credential Manager. Credentials are not stored in any QSS Exchange Anti-Spam Toolkit settings files.
Click Save Changes once the server name and credentials have been updated. The Dashboard page should then be accessible using the link in the left navigation bar.