El día Sunday, November 22, 2015 a las 09:23:40PM +0000, RW escribió:
> normal delivery. Getting the internal/trusted networks right for this
> kind of mail is of often significantly more difficult than dealing with
> the normal case, and may be more trouble than it's worth on a
> network you don't control.
>
> A test email that's sent through a third-party mail service is much more
> representative as a test.
>
>
> > https://wiki.apache.org/spamassassin/Rules/RDNS_NONE
> >
> > RDNS_NONE checks more than just the PTR (reverse) DNS record.
> > It really should be named FCRDNS_NONE
>
> Then the wiki is wrong.
This is exactly what I said in my first mail: the description of
RDNS_NONE is just wrong; nearly all my incoming mails are flagged by
RDNS_NONE; for example the mail I'm right now replying to which came
from apache.org says this when I run it through 'spamassassin -D':
$ spamassassin -tD < /tmp/apache > /tmp/apache.o 2> /tmp/apache.d
$ fgrep RDNS_NONE /tmp/apache.d
nov 23 07:46:38.098 [1927] dbg: rules: ran header rule __RDNS_NONE ======> got
hit: "[ ip=140.211.11.3 rdns= "
nov 23 07:46:39.203 [1927] dbg: check:
tests=FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_HI,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RDNS_NONE
...
and 140.211.11.3 has a rDNS:
$ host 140.211.11.3
3.11.211.140.in-addr.arpa domain name pointer hermes.apache.org.
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎
+49-176-38902045
