Reverse DNS does not match SMTP Banner
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
1. The 220***************** is probably some sort of firewall, altering the SMTP transaction. Cisco devices usually do that.
2. Mismatched rDNS and PTR name are VERY common, probably occurs more often than not. Provided you have some sort of PTR in place that does not look like a home connection, that should be fine.
2. Mismatched rDNS and PTR name are VERY common, probably occurs more often than not. Provided you have some sort of PTR in place that does not look like a home connection, that should be fine.
Mismatched rDNS and PTR records are TOO common -- and the BIG mail vendors (Google [gmail], Microsoft [hotmail, outlook, msn], AOL [yes, they're still big -- don't know why, but they are!], and many others) are starting to crack down on this because of the spoofing that goes on to PURPORT to be from one domain, but really isn't.
*IF* you cannot fix this issue, then at least make sure your DMARC, DKIM, and SPF entries are enabled and correct. If you knock on Google's door, have no SPF, no DKIM, no DMARC, and your FCrDNS (Forward Confirmed rDNS) fails -- your mail will either be blocked altogether, or minimally dropped into recopients' Junk folders.
SMTP is one of the Internet's OLDEST protocols, and it openness to abuse is LEGENDARY. But the abuse is (and has been) out of control, and the big players are leveraging their market share to FORCE smaller players to play by the MODERN rules (ca. 2010 vs 1990!).
It appears to me that you're trying to "do the right thing" -- and that's not easy. Getting a mail server up and running properly is a hard enough task, but making it play well with others -- especially the "big boys" is another, separate but equally challenging task!
Good Luck
Dan
*IF* you cannot fix this issue, then at least make sure your DMARC, DKIM, and SPF entries are enabled and correct. If you knock on Google's door, have no SPF, no DKIM, no DMARC, and your FCrDNS (Forward Confirmed rDNS) fails -- your mail will either be blocked altogether, or minimally dropped into recopients' Junk folders.
SMTP is one of the Internet's OLDEST protocols, and it openness to abuse is LEGENDARY. But the abuse is (and has been) out of control, and the big players are leveraging their market share to FORCE smaller players to play by the MODERN rules (ca. 2010 vs 1990!).
It appears to me that you're trying to "do the right thing" -- and that's not easy. Getting a mail server up and running properly is a hard enough task, but making it play well with others -- especially the "big boys" is another, separate but equally challenging task!
Good Luck
Dan
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No response from asker. The solutions in these comments will resolve the issue.
Open in new window