Before changing your MX records, you should verify that your Spamphibian Gateway is setup and configured properly by testing it. The purpose of this test it to make sure that once mail starts arriving at your Spamphibian Gateway, the accepted mail will be properly delivered to the proper destination SMTP server.

Because you have not changed your MX records yet, you will have to use telnet to test that your Spamphibian Gateway is setup and configured properly.

Below is a sample telnet session that tests the Spamphibian Gateway:

# telnet localhost 25
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 spamphibian.metrosense.com ESMTP Service Ready (Spamphibian Gateway 1.0 51205 for Mac OS X)
helo test.com
250 spamphibian.metrosense.com Hello test.com [127.0.0.1]
mail from: <test@test.com>
250 OK
rcpt to: <gp@metrosense.com>
250 OK
data
354 Enter message, ending with "." on a line by itself
Subject: test
To: gp@metrosense.com
From: test@test.com
Date: Tue, 1 Nov 2005 17:44:28 -0800

test
.
250 OK
quit
221 spamphibian.metrosense.com closing connection
Connection closed by foreign host.

Alternatively, you can use an email client, such as Apple Mail or QuickMail Client. Configure your email client to send outgoing mail to the machine running Spamphibian Gateway. Make sure to send the message to a user at a domain you've configured Spamphibian Gateway to filter.

After performing this test, you should make sure that your destination mail server received the test message. Look at the "Received" headers in the message source to confirm that this message was processed by Spamphibian Gateway. You should have a "Received" header like:

Received: from [206.221.243.227] by spamphibian.metrosense.com 
	with ESMTP (Spamphibian Gateway 1.0 51208 for Mac OS X); Tue, 1 Nov 2005 17:44:28 -0800

In this case, "Spamphibian Gateway 1.0 51208" is running on spamphibian.metrosense.com

Note: If any connectivity issues arise from the above tests result in errors, please see "Chapter 9: Troubleshooting Guide".