Kasper Sacharias Eenberg wrote: > On Thu, 2009-07-02 at 08:20 +0100, rich...@buzzhost.co.uk wrote: >> On Thu, 2009-07-02 at 08:28 +0200, Kasper Sacharias Eenberg wrote: >>> On Thu, 2009-07-02 at 05:32 +0100, rich...@buzzhost.co.uk wrote: >>>> On Wed, 2009-07-01 at 16:13 -0600, LuKreme wrote: >>>>> On 1-Jul-2009, at 06:47, rich...@buzzhost.co.uk wrote: >> So, to disable these rules and stop the Sorbs lookups from happening >> just how do we do it ? If we should not alter the score here do we just >> paste the above block into a file like custom_sorbs.cf and that will do >> it or will the built in rule take precedence? > > The /etc/mail/spamassassin ( or /etc/spamassassin in your case) is the > custom dir. Just put them in there. > > Anything you put into rules in /etc/mail/spamassassin will take > presedence over rules made with sa-update or installed with > Spamassassin. > > So putting these in /etc/... will disable SORBS lookups altogether. > > score RCVD_IN_SORBS_BLOCK 0 > score RCVD_IN_SORBS_DUL 0 > score RCVD_IN_SORBS_HTTP 0 > score RCVD_IN_SORBS_MISC 0 > score RCVD_IN_SORBS_SMTP 0 > score RCVD_IN_SORBS_SOCKS 0 > score RCVD_IN_SORBS_WEB 0 > score RCVD_IN_SORBS_ZOMBIE 0 > > Run 'man spamassassin' and read the 'CONFIGURATION FILES' chapter to get > a full understanding. >
Actually; you could save yourself some typing: score __RCVD_IN_SORBS 0 score RCVD_IN_SORBS_DUL 0 is all that is necessary to put into local.cf to disable the lookups for SORBS. This is because for multiple return lists like SORBS SA queries the list once (using eval:check_rbl()) and then each test checks the result and return code of the original (using eval:check_rbl_sub()), so if you disable the parent query; you disable all the dependent tests. If you do a "grep -Eh 'check_rbl\(' *" in your SpamAssassin updates directory; you'll be able to see all of these parent lookups, then do a "grep -Eh 'check_rbl_sub\(' *'" to see the lookups based on these. Cheers, Steve.