Discussion Locked

DNS for Separate Incoming/Outgoing Relays

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We currently have two separate email relays and twenty different email domains. One relay is for incoming email, one for outgoing. We have at least one company who is rejecting our mail because they say we have no reverse DNS entry. Their tech department said this is a standard sendmail check to block spam and anyone using sendmail will also block our email. The MX record for these domains point to our incoming email relay, not the outgoing. What DNS change would you recommend so sendmail won't reject our messages?

5 replies

by amberhaze

The way I have always handled such situations is to have the inbound listed as primary and the outbound listed as secondary in the MX record for the domain.. in this way, when dns is varified, it checks out.. but your inbound is still primary for anyone trying to send to you.... (although this also will permit you to use your outbound as a fallback if something goes wrong with your inbound... (something I just had to deal with myself in the last couple of days...)

by mm212

Thanks for the answer but that wasn't the problem. In case someone comes up against this, here's the rundown on the source of the problem and the solution:

When we added the new inbound email relay, the people doing the DNS changes just plugged the new IP in place of the old in DNS. What they should have done is created a new host with the new IP and pointed the MX record to the new host. What ended up happening is that outgoing was named (all names and IPs are fudged) outgoing.domainname.com with IP and the incoming was named incoming.domainname.com with IP . The MX record pointed to outgoing.domainname.com with IP . When the outbound email server sent a message, the recipient email server did a reverse lookup on and found outgoing.domainname.com. It then looked up outgoing.domainname.com and found . They didn't match so some domains were rejecting our email.

Here is what we needed to do to fix this:

Set a PTR record for to point to outgoing.domainname.com.

Set a PTR record for to point to incoming.domainname.com.

Set A records for incoming..com to point to .

Set MX records for our email domains to point to incoming..com.

We do not want an MX record pointing to outgoing.domainname.com as this would attract spammers trying to get around our spam filter.

by greybeard770

You do not want an MX record for your outbound mail server unless you want to receive mail there. Even if you make it the highest cost so it in theory doesnt get used, the evilest of the spammers will send their crap to that address because im some environments the highest cost is the weakest link.
Reverse DNS lookups ask your ISP what domain goes with an IP address. You may be the SOA for the domain but your ISP is the SOA for the IP address. Your situation os more complex than mine since you are sending mail from multiple domains and all from the same IP address. You need to talk to your ISP. They are the ones who need to make the DNS changes related to the IP address.

by mm212

Thanks for the answer but that wasn't the problem. See above for the source of the problem and the solution.

This discussion is closed to new replies.