no remote connects

[Dave Stern - Former Rocket Scientist <da...@umiacs.umd.edu>]

Now that I've got SA3.0.rc1 working, indeed, I like it a lot. As a 
test, I have the last rule in my procmailrc take everything that wasn't
filtered by my other procmail rules and SA(2.64) and forward it to 
another host running SA3.0rc1. Sure enough, the other machine catches
all the spam that the 2.64 host bled thru.

That's the good news. Now in our environment, aside from the fact that
users must explicitly  turn on SA via procmail rather than the MTA
running it, we're also running spamc. So on the old machine, in order
to have two iterations of SA, I presume I can only have one running the
2.64 spamd and all others that would care to beta test 3.0 would have
to explicitly call spamassassin rather than spamc. Even with earlier
versions of SA, I've noticed this to take a CPU penalty of nearly an
order of magnitude. But worse, the remote connects to test for SURBL, DNS
take a rather extreme amount of time and anyone running spamassassin (the
3.0 version of the script) directly will be really giving the CPU a workout. 
(OTOH, I recognize that perhaps it's these tests that give such a robust 
ratio of catching spam, nevertheless,) Is it possible to turn off all 
these checks ALA
use_dcc     0
use_pyzor   0
...

If so, which rules are they?

TIA

  =-=-=-=-=-=-=-=-=-=-  generated by /dev/dave -=-=-=-=-=-=-=-=-=-=-=-=
  David Stern                                    University of Maryland
            Institute for Advanced Computer Studies

Re: SURBL and whitelist

[Lucas Albers <ad...@cs.montana.edu>]

You just need to configure your MTA so it will exclude filtering for:
mail sent from authenticated users, and mail relayed from specific ip
addresses.
Their are a number of different ways to do this.
You cannot do this solely through sa, you need to confiugre the MTA you use.

I use Mimedefang+sendmail+sa for this sort of setup.

Like any other rule surbl works in conjunction with all the other rules,
so it would be stupid to ignore all the other rules and just use surbl.

Just comment out or rename the cf files you don't want to use.
Read the wiki.
--Luke

Paul Diaguila said:
> We have quite a few groups of users that want email sent internally to
> the users in their  domain to pass without being filtered, so set up the
> whitelist to allow it to pass.  Spammers of course spoof the domain and
> spam is delivered to the account.  Any way to set this up so SURBL can
> do it's magic but the email isn't scored with any other cf files?
>
> Has anyone tried  using SURBL without any other cf files?
>
> Speaking of SURBL..... Haven't had any complaints about spam since it's
> been installed....  thank you...thank you...thank you....
>
> Paul
>


-- 
Luke Computer Science System Administrator
Security Administrator,College of Engineering
Montana State University-Bozeman,Montana

SURBL and whitelist

[Paul Diaguila <pd...@hcs.net>]

We have quite a few groups of users that want email sent internally to 
the users in their  domain to pass without being filtered, so set up the 
whitelist to allow it to pass.  Spammers of course spoof the domain and 
spam is delivered to the account.  Any way to set this up so SURBL can 
do it's magic but the email isn't scored with any other cf files? 

Has anyone tried  using SURBL without any other cf files?

Speaking of SURBL..... Haven't had any complaints about spam since it's 
been installed....  thank you...thank you...thank you....

Paul