You can whitelist anything from *@panix.com, etc. I wouldn't recommend doing so, though. This would allow spammers to fake the @panix.com in their From: lines, allowing the spam to get in more easily.
On Wed, 6 Nov 2002, Ben Rosengart wrote: > Hello spam assassins, > Panix is about to deploy spamassassin on a fairly wide scale. > We'd like to find a way to protect mail originated inside Panix > from being flagged by SA, without the sender having to do anything > special. My approach to this so far has focused on the Received > header: > > header ORIGINATED_WITHIN_PANIX Received =~ /^from \S+ \(\S+ \[166\.84\.\S+\]\)/ > > The problem is that this only detects the topmost (last) Received > header. I'd like to be able to look at the next one down as well. > (I know that this raises security issues, and I'm willing to live > with them.) How can I write a test that will look at the two or > three or N topmost Received headers? > > -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000 ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
