Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Reverse DNS SMTP banner mismatch

Posted on 2013-01-23
14
Medium Priority
?
54 Views
Last Modified: 2016-07-01
Hello,

I have an Exchange 2010 server install.  The hub transport is on the same server as the mailbox. I have a sendconnector configured with the proper FQDN.

I have two receive connectors.. a default and a client.

The default receive connector  has FQDN   mydomain.local

In my reading Microsoft recommends not changing the FQDN in the default receive connector.  

So my question is how do I get my receive connector to report the proper FDQN.?

I assume I use some kind of exchange cmdlet to set this option but I'm new to these cmdlets and their functions.

any help would be appreciated..
0
Comment
Question by:magnav30
  • 5
  • 4
  • 2
  • +1
12 Comments
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 2000 total points
ID: 38812516
Don't change anything.
That is the expected behaviour on the automated tests because Exchange announces one thing for inbound email and another for outbound. Outbound is the only valid which the automated tests cannot test for.

Simon.
0
 
LVL 23

Expert Comment

by:Suliman Abu Kharroub
ID: 38812522
0
 

Author Comment

by:magnav30
ID: 38813134
Simon,

My emails are being flagged as spam?  which they weren't before I converted to exch2010.

Sulimanw,


I think your link is the correct way to change the fqdn.  When I run the set-receiveconnector command and I try to set a banner.  I get an error that the says default receive connector is not found on my server.  (Except it says it can't find it on one of my old exchange 2003 servers?  Why would a set-receiveconnector command be looking @ an old exchange server?  The default receive connector is on my new Exch2010 box.

I still have yet uninstalled the 2003 servers.
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 38813385
Simon is 100% correct - the FQDN on the Receive Connector doesn't need to be changed.

No-one cares what your Receive Connector is called because when they send mail to you, they don't need to check if you are a spammer - only your SEND connector FQDN is important and that is set correctly.

Alan
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 38814595
It should also be noted that changing the FQDN on the Receive Connector can stop other things from working. The Microsoft guidance for the FQDN is that it should be either null, the server's NETBIOS name, or the server's FQDN, not some other FQDN.

Simon.
0
 

Author Comment

by:magnav30
ID: 38815753
yes.. I understand.. So we are to ignore the mxtoolbox reverse smtp banner mismatch error?

This doesn't make any sense?  this all worked when I had Windows 2003.  I passed the reverse dns mismatch test back when I had exchange 2003?

My send connector has the proper FQDN... yet my sending emails are going to junk for many .

My received mail header shows that the email was received from the proper mx record but also shows my .local mail server info as well as originating local ip address.  This seems odd to me?  Why would the header show all that information?  Is that just how SMTP works.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 38815937
Exchange 2003 sent and received using the same SMTP virtual server.  Exchange 2007 on uses different connectors for sending and receiving which is why the mxtoolbox test worked on Exchange 2003 but doesn't work for Exchange 2007 onwards.

Alan
0
 

Author Comment

by:magnav30
ID: 38816077
Thanks Alan.. that helps me understand lots.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 38816113
You are welcome.  On my server I see the following from MXToolbox:

MXToolbox Output
Yet I don't have any problems sending or receiving.
0
 

Author Comment

by:magnav30
ID: 38816157
I'm thinking I need to look into a SPF configuration as well..??
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 38816199
You can - but that should be the subject of another question as this one is about Reverse DNS / SMTP Banner Mismatch.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 41684598
Comment https:#a38812516 should be accepted as the correct answer.

Alan
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

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

Steps to fix “Unable to mount database. (hr=0x80004005, ec=1108)”.
Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses

578 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