-
Title
How to: test for open relay on an SMTP server. -
Description
How to: test for open relay on an SMTP server. -
Cause
This solution is provided as is and is not a part of any Quest Product and is provided as is to aid in the trouble shooting of issues with products that use SMTP relay to send email messages. -
Resolution
This is one of many ways to check that an SMTP server is able to relay messages. The following information is provided as is.
If running Windows 2008 and above telnet is not installed by default. It can be added by using the Add Features option in Server Manager and add the Telnet Client (Telnet server is not required).
Open a command prompt on the Spotlight on Messaging server and do the following.
1. Type - telnet <servername> 25 (<servername> should be the name of the SMTP server specified in Spotlight on Messaging).
2. type - helo
You should a response from the server like the one below.
response - 250 exchangeservername.domain.com Hello [10.5.83.181]
3. Type: - mail from: test@test.com (this should be the email address that was specified as the From address in the Spotligh Management Console)
You should a response from the server like the one below.
Response - 250 2.1.0 Sender OK
4. Type - rcpt to: youremailaddress@domain.com (this should be the email address of your mailbox so you can receive the test message being sent.
You should a response from the server like the one below.
250 2.1.5 Recipient OK
5. Type - data - and hit enter
You should a response from the server like the one below.354 Start mail input; end with <CRLF>.<CRLF>
5. Type the wor - hello - or - test - this is what will be contained in the body of the email and hit enter.
6 Type a period - . - and hit enter.
You should a response from the server like the one below.
Response - 250 2.6.0 3511e21f-1406-408b-b459-52fffbb59164@servername.domainname.com Queued mail for delivery
After seeing this last response from the server you should receive an email in your mailbox.
If there was any sort of error trying to send the message this shows there is an environmental issue with the SMTP server and should be investigated by the local administrator of that server.