On Sat, 9 Dec 2006, Peter M. Abraham wrote: > Is there a way to tell Spam Assassin (SpamAssassin 3.1.7) to skip > processing emails sent from our network (public IP addresses are > involved)? > > I do have TrustedNeworks set up, but I don't know if there is > another variable that must also be set up.
The best way is to avoid passing such messages to SA at all in the first place. Public IPs being involved is not that big a hurdle. What makes it difficult is allowing for roaming or dynamic-IP users. Basically you need to look at: (1) What is your MTA? Sendmail? Postfix? EXIM? (2) How is your MTA passing messages to SA? Procmail? Milter? Some other mechanism? (3) How do you identify your locally-originated messages? By IP ranges (private or public)? By authenticated user? Both? What does the Received header that *your* MTA adds to a locally-originated message look like? (4) How do you tell your MTA to recognize those messages? Source IPs? Substrings from the Received: header? (5) Once you've told your MTA how to recognize them, how do you tell it to bypass SA for those messages? -- John Hardin KA7OHZ http://www.impsec.org/~jhardin/ [EMAIL PROTECTED] FALaholic #11174 pgpk -a [EMAIL PROTECTED] key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 ----------------------------------------------------------------------- It is not the business of government to make men virtuous or religious, or to preserve the fool from the consequences of his own folly. -- Henry George ----------------------------------------------------------------------- 6 days until Bill of Rights day
