-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
[EMAIL PROTECTED] writes: > Justin Mason wrote: > > It's extremely trivial to add as a normal regexp rule: > > > > header MY_WHITELIST_1 Received =~ /\[111.222.11.22\]/ > > score MY_WHITELIST_1 -5 > > Mikael Hakman writes: > >> Wouldn't you all agree that blocking or letting through emails sent > >> from or relayed by specified IP addresses and subnets is quite a > >> basic functionality? In a sense it is more basic than doing the same > >> with DNS names and SMTP addresses because all those names ultimately > >> resolve to IP numbers. All communication (routing) on the Internet > >> is done by numbers not by names. > >> > >> Then why can't we have such a generic rule built-in into SA? > > As long as spammers don't know you trust 111.222.11.22, that works. > But if they do, it's trivial for them to forge a Received: header that > includes a whitelisted host. > > Ideally there'd be a way to only look at Received headers that were > added by the server you're running on, or (going back a bit at a > time) added by trusted perimeter hosts. (I think SpamAssassin should > always be running on a perimeter server, but that's another > thread...) see Matt Kettler's version ;) - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFCMJAAMJF5cimLx9ARAqbtAKCgQG9BSgC5QQLPWsQdcl3tg04g7gCfZg8Y GrInMYog/f9qHnaFw2+ZCGg= =Jkl0 -----END PGP SIGNATURE-----
