From: Matus UHLAR - fantomas <uh...@fantomas.sk> Date: Thu, 21 Feb 2013 16:36:18 +0100 >On 2/21/2013 9:03 AM, Jeff Mincy wrote: >>Well, I trust the network not to lie. This is more of an omission.... On 21.02.13 10:26, Kevin A. McGrail wrote: >Your Clinton-esque logic likely doesn't apply here ;-). The land of >RFC's works to avoid this type of logic in a language I call >RFC-eeze. as long as I understan Jeff's original mail, the issue is that his ISP stopped providing DNS information in the Received: headers. SA does not do lookups on the IPs in Received: (there's iirc one exemption related to a buggy software) and if it's not there, it assumes the rDNS does not exist, while it does.
Actually the ISP added a completely new hop, and that hop is not adding rDNS to the received header. I had to add the new hop to trusted_networks and internal_networks. The new hop looks like it is scanning the messages using Cloudmark: X_CMAE_Category: ... X-CNFS-Analysis: ... X-CM-Score: ... X-Scanned-by: Cloudmark Authority Engine >>I could always whine to Rcn about it, maybe they'll fix it. >I think that's a good move to at least try! It truly sounds more >like a DNS error that they might know be are is occurring. if the error repeats, I assume Jeff's guess is correct and the ISP just turned rDNS lookups off. Or neglected to turn on the lookups in the first place... -jeff
