-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Justin Mason wrote: > Shelley Waltz writes: >> Spamassassin 2.63-1/amavisd-new-20030616-p8 >> >> I am trying to configure spamassassin such that any email originating >> from my domain is not spam tagged. I have tried in local.cf >> >> both these syntaxes. >> >> header LOCAL_RCVD Received =~ /.*\(\S+\.myhost\.mydom\.edu\s+\[.*\]\)/ >> header LOCAL_RCVD Received =~ /\S+\.myhost\.mydom\.edu\s+\(.*\[.*\]\)/ >> >> >> In each case only one rule will work for one particular received from >> header. I have these two styles(one from mozilla, and one from webmail) >> >> Received: from [192.168.1.10] (myhost.mydom.edu [192.168.1.10]) >> >> Received: from webmail.mydom.edu (localhost.localdomain [127.0.0.1]) >> >> Is there a rule which will work for both, or is there a simpler way to >> achieve this result, ie, to not filter locallly originating mail? > > use trusted_networks; this is what ALL_TRUSTED is for. > > --j.
Justin, The OP is using SA version 2.63 which, if not mistaken, doesn't have the trusted_networks settings in it. (I could be wrong) That being said, You should definitely look into upgrading to at the very least 2.64 as 2.63 is vunerable to DoS attacks in certain situations. (if memory serves) now, with regards to the rules, you could use meta rules to test for either the first or the second pattern. something like this (untested): [beware of line wraps] header __LOCAL_RCVD1 Received =~ /(?:\S+\.myhost\.mydom\.edu\s+\[.{,20}\])/ header __LOCAL_RCVD2 Received =~ /\S+\.myhost\.mydom\.edu\s+\(.{,20}\[.{1,15}\]\)/ meta LOCAL_RCVD (__LOCAL_RCVD1 || __LOCAL_RCVD2) score LOCAL_RCVD 0.01 (score as appropriate) HTH alan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEcSSzE2gsBSKjZHQRAtI6AKDt4HWxdQrpw4OgvvJcC91KO2uw5ACgkYTQ aDtvjU/csAmS3BW+2nB8sBU= =M+Fu -----END PGP SIGNATURE-----