""Daryl C. W. O'Shea"" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:<[EMAIL PROTECTED]>... > Kelson wrote: > > [EMAIL PROTECTED] wrote: > >> User Sam and Joe has internet access via DSL with a dynamic ip > >> address. The mail going from [EMAIL PROTECTED] to [EMAIL PROTECTED] is > >> identified as SPAM because the sending ip address is the dynamic > >> dial up address. > > > The best solution would be to make your users send with SMTP-AUTH, > > and > > then tell whatever calls SpamAssassin to skip SA if it finds valid > > SMTP-AUTH info. > > > > I'd guess from your description, however, that you're running > > SpamAssassin on delivery and not on receipt, which will probably make > > this a bit more challenging. Though if you can check after the fact for > > valid SMTP-AUTH info, you can probably still make it work. > > If you can get Postfix to insert RFC 3848 style "with ESMTPA" tokens > or > Sendmail style "authenticated user" lines in the headers, SpamAssassin
> will automatically recognize that the user is authenticated (if they > authenticate) and not do the dynablock checks. If anyone knows how to > do this (I've never used Postfix), I'd like to document it on the wiki. I think, this is the best way to solve my problem. At first I'll try to use Nigels solution, to set whitelist-from in SA's local.cf I hope to find these informations to implement it as soon as posible. > If you use POP-before-SMTP, there's also the POPAuth plugin available > on > the wiki at: http://wiki.apache.org/spamassassin/POPAuthPlugin > > Also (like Kelson said), if you don't want to scan local-domain mail > at > all (NOT something I prefer myself), you can probably configure > amavisd-new or Postfix to skip mail from these users. POPAuth is not prefered, because a lot of clients use IMAP. Regards, Uwe -- SpamAssassin User Mailing list read-only via NNTP or SNMP at obelix.kiewel-online.de Online since March 01, 2006