Re: RCVD_IN_RP_CERTIFIED always -3
Kris Deugau <[email protected]>
| Newsgroups | gmane.mail.spam.spamassassin.general |
|---|---|
| Organization | Vianet Internet Solutions |
| Message-ID | <[email protected]> |
[email protected] wrote: > I found the related > configuration in 20_dnsbl_tests.cf: > > /# > ---------------------------------------------------------------------------/ > > /# Return Path Certified:/ > > /# https://www.returnpath.net/internetserviceprovider/certification// > > /# (replaces RCVD_IN_BSP_TRUSTED, RCVD_IN_BSP_OTHER, > RCVD_IN_SSC_TRUSTED_COI)/ > > /header RCVD_IN_RP_CERTIFIEDÂ Â Â Â eval:check_rbl_txt('ssc-firsttrusted', > 'sa-trusted.bondedsender.org.')/ > > /describe RCVD_IN_RP_CERTIFIEDÂ Â Sender in ReturnPath Certified - > Contact [email protected]/ > > /tflags RCVD_IN_RP_CERTIFIEDÂ Â Â Â net nice/ > > /reuse RCVD_IN_RP_CERTIFIED/ These were renamed/rebranded some time ago. Run sa-update to get current rules. Note that the live rules your system references should be under /var/lib/spamassassin on most systems. Some distribution packages will also ship a rules snapshot in /usr/share/spamassassin, however these should be considered more or less unusable unless you are trying to run SA in a very extremely security-restricted environment. > Regarding the SpamAssassin 4.x rules - are they backward compatible to 3.4.4? Pretty much, although rules that rely on new features won't work well or at all, and some rules will have poor performance as some of the code that extracts data they reference has been updated and refined. -kgd