Re: [AMaViS-user] amavisd with spamc/spamd for load balancing

2006-12-08 Thread Melissa Evans

 I am not opposed to multiple amavisd-new servers, but I'm not sure how
 that would be implemented with our setup.  The messages are all
 delivered to one server, so how do you propose that we distribute the
 email among multiple servers?  We cannot just do it on a per-domain
 basis, because some of our larger domains will overwhelm a single
 server doing both spam and virus scanning.   Keep in mind that we have
 MANY end users that have their incoming and outgoing server set to
 this main server and it is not feasible to change those settings.

I didn't read the whole thread so I apologize if this is off-track 
but...

We have a load balancing switch in place to do this.  Mail comes into a 
single IP and the switch hands it off to multiple servers.  Currently, 
we have postfix and amavisd-new running on each server in the farm, but 
we are in the processing of considering breaking it up even further and 
putting amavisd-new onto a separate load balanced ip w/multiple servers 
doing just amavisd-new scanning.  We also have our LDAP backend, 
outgoing and incoming ips load balanced.

You could do this multiple ways depending on the size of your 
environment and needs.  If you only need one mail server but multiple 
amavisd-new servers, you could leave mail coming into the server IP and 
just load balance the amavisd-new servers on a different ip.  You could 
also convert your main ip (used by users) to a virtual ip and load 
balance servers behind it or go further and do the same for amavisd-new. 
You can also balance by protocol/port.

Not sure what your budget is... Foundry ServerIrons work for this.  New 
ones are a bit pricey but used ones can be found for a reasonable cost. 
Just be sure it has L3 functionality.

Melissa

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/


[AMaViS-user] @bypass_spam_checks_acl not working?

2006-12-07 Thread Melissa

I am attempting to bypass spam scanning for outgoing mail using 
@bypass_spam_checks_acl

According to the docs:

# don't run spam check for these RECIPIENT domains:
#   @bypass_spam_checks_acl = qw( d1.com .d2.com a.d3.com );
# or the other way around (bypass check for all BUT these):
#   @bypass_spam_checks_acl = qw( !d1.com !.d2.com !a.d3.com . );
# a practical application: don't check outgoing mail for spam:
#   @bypass_spam_checks_acl = ( !.$mydomain, . );
# (a downside of which is that such mail will not count as ham in SA bayes db)

However, when I include my recipient domains the mail is still scanned. In 
fact, I even tried uncommenting this line:

# @bypass_spam_checks_acl  = qw( . );  # uncomment to DISABLE anti-spam code

and the mail is still spam scanned...

It appears that this configuration variable is not doing anything at all in my 
environment.  I've tested this on similarly configured servers all running 
amavisd-new-2.4.2.  What am I missing? :)


Melissa

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/