MetraTechIT
asked on
Exchange serve configuration - require FQDN in SMTP address
Good morning:
We are currently running an Exchange 2003 server and I wanted to force messages created by some of our automated tools to use the FQDN or fail. For example, you can telnet on port 25 and send a message as follows:
telnet ... 25
ehlo
250 OK
mail from:rscholl
250 2.1.0 rscholl@metratech.com....S ender OK
rcpt to:rscholl
250 2.1.5 rscholl@metratech.com
data
354 Please start mail input.
subject:<test>
all bad, sender was not FQ
.
250 Mail queued for delivery.
quit
221 Closing connection. Good bye.
The question is: Does enabling the reverse DNS resolve the issue? Is there a more elegant method? What else is affected in the process?
Thanks in advance,
ray
We are currently running an Exchange 2003 server and I wanted to force messages created by some of our automated tools to use the FQDN or fail. For example, you can telnet on port 25 and send a message as follows:
telnet ... 25
ehlo
250 OK
mail from:rscholl
250 2.1.0 rscholl@metratech.com....S
rcpt to:rscholl
250 2.1.5 rscholl@metratech.com
data
354 Please start mail input.
subject:<test>
all bad, sender was not FQ
.
250 Mail queued for delivery.
quit
221 Closing connection. Good bye.
The question is: Does enabling the reverse DNS resolve the issue? Is there a more elegant method? What else is affected in the process?
Thanks in advance,
ray
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Its a standard anti-spam technique, so any tool of that type should be able to do it. I believe that GFI Mail Essentials can do that test, as can ORF from Vamsoft.
Simon.
Simon.
ASKER