I have a SA 3.4.6 instance that doesn't intend to be strange running on a machine with a local named. Pretty much everything works as one would expect.
However, I get infrequent falsing where the lookup of the peer MTA's
address fails, so I get a hit on RDNS_NONE. An example is
Received: from mail.netbsd.org (unknown [IPv6:2001:470:a085:999::25])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
(No client certificate requested)
and if I look that up, I get the name just as I'd expect. This happens
also with google and comcast servers. I would guess a message or two
per day over 100s of messages.
I wonder if something is being overly aggressive about timing out
lookups and I'm getting unlucky with packet loss, or if there's a bug
someplace else. I guess this is really a postfix question, as that
unknown was put in the Received: line by postfix.
I am also guessing that it isn't SA's place to redo the lookup.
So in closing, I wonder if anyone else is seeing occasional failures in
doing rDNS lookups at SMTP receive time.
signature.asc
Description: PGP signature
