Help - RDNS_NONE
Posted: 14 Feb 2017 11:01
Hi folks,
Having a slight problem. When I setup EFA I added a configuration to stop every mail being marked rdns_none. Basically all our mail is handed over to us from one fixed internal server, however this server fails reverse lookup checks etc.
To get round this, I added the delivering server as a trusted network and internal network. This worked fine. For some reason, all of a sudden I am getting rdns_none against every mail again. I am trying to understand this.
Does rdns_none only relate to the final server - ie the one which hands the mail to EFA, or can it be caused by others further up the chain? I notice that the server at our ISP where the upstream server from my EFA (the one in my trusted/internal network) is failing rdns too - could this be it?
Thanks for any help you can provide.
Having a slight problem. When I setup EFA I added a configuration to stop every mail being marked rdns_none. Basically all our mail is handed over to us from one fixed internal server, however this server fails reverse lookup checks etc.
To get round this, I added the delivering server as a trusted network and internal network. This worked fine. For some reason, all of a sudden I am getting rdns_none against every mail again. I am trying to understand this.
Does rdns_none only relate to the final server - ie the one which hands the mail to EFA, or can it be caused by others further up the chain? I notice that the server at our ISP where the upstream server from my EFA (the one in my trusted/internal network) is failing rdns too - could this be it?
Thanks for any help you can provide.
RDNS_NONE was firing because my internal Exchange server (2013) has both ipv4 and ipv6 enabled. (It gets upset if you turn it off)