Exchange serve configuration - require FQDN in SMTP address
Posted on 2006-10-26
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
250 2.1.0 email@example.com....Sender OK
250 2.1.5 firstname.lastname@example.org
354 Please start mail input.
all bad, sender was not FQ
250 Mail queued for delivery.
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,