Thanks, that's what I did. There clearly is something I don't understand about how denying reverse DNS works.
I whitelisted the IP and not the domain. My logic is. Someone
from anywhere could try to fake the "domain" so whitelisting that
might expose the server. The IP address belongs to Comcast
Business and is likely to never belong to anyone else. So even
thought that IP might eventually belong to someone else, it's not
likely to belong to a bad actor.
Gary
On 7/16/2021 11:42 AM, Eric Broch
wrote:
whitelist it in spamdyke--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
On 7/16/2021 8:28 AM, Gary Bowling wrote:
I have an issue with mail getting rejected from a specific domain. It's getting rejected due to Spamdyke and RDNS. Here's the line out of the log.
Jul 16 09:02:41 vm1 spamdyke[32358]: DENIED_RDNS_RESOLVE from: ***@**nd.com to: ***@**ion.com origin_ip: 50.**.**.98 origin_rdns: 50-**-**-98-static.**.comcastbusiness.net auth: (unknown) encryption: (none) reason: (empty)
From looking at the log. It says spamdyke is blocking it due to RNDS not resolving. But then on the same line it shows the "origin_rdns" and it looks like a valid reverse dns to me.
Why is this getting blocked?
Gary
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
