Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Exchange serve configuration - require FQDN in SMTP address

Posted on 2006-10-26
5
Medium Priority
?
223 Views
Last Modified: 2010-03-06
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....Sender 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
0
Comment
Question by:MetraTechIT
  • 2
3 Comments
 
LVL 104

Accepted Solution

by:
Sembee earned 1000 total points
ID: 17829355
The reverse DNS option in Exchange is close to useless. It doesn't enforce anything, except write a line in the header that reverse DNS failed. I don't think I have it enabled on any of my sites.

You would have to use a third party tool that can do reverse DNS lookups and drop the connection if it doesn't match or isn't valid.

This will of course have an impact on all of your email - as you will need to implement it on all SMTP Connections to be of any use. That could mean you are dropping valid email messages. If you do deploy a solution, make sure that you create text in the NDR message that is sent back that explains why the connection was dropped.

Simon.
0
 

Author Comment

by:MetraTechIT
ID: 17833458
OK, so can anyone suggest the best solution for forcing FQDN in the SMTP from address?
0
 
LVL 104

Expert Comment

by:Sembee
ID: 17834654
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.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Suggested Courses

824 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question