Mailing List Archive: Spamassassin using different local.cf's for different domains?

Spamassassin using different local.cf's for different domains?

Feb 11, 2004, 11:21 AM

Post #1 of 4 (892 views)

I've got a mailserver right now running 5 seperate domains for 5 seperate
organizations. I'd like to install Spamassassin into the mail pipeline (I'm
using qmail). Can Spamassassin be configured to use a different local.cf
depending on domain the message is going to? If this is possible, how would
I configure it? These different organizations will probably have very
different whitelist/blacklist entries. In addition, is it possible to have a
domain specific local.cf and then a sitewide local.cf for bad addresses that
are considered always spam by everyone? I've thought about running jails,
with totally seperate binaries of qmail and spamassassin, but that creates a
lot more overhead for me when a new organization want's their mail hosted on
this box (have to re-install/configure everything in a new jail). Any
thoughts?

Thanks!

--Jeremy

Re: Spamassassin using different local.cf's for different domains? [ In reply to ]

mkettler at evi-inc

Feb 11, 2004, 11:53 AM

Post #2 of 4 (865 views)

Permalink

At 01:21 PM 2/11/2004, Jeremy Olmen wrote:
> Can Spamassassin be configured to use a different local.cf
>depending on domain the message is going to?

No. The paths that SA will try to find local.cf are hard-wired in the code
itself.

Only user_prefs can be done on a "per call" basis... So theoretically you
could use "user_prefs" as a "domain_prefs".

Re: Spamassassin using different local.cf's for different domains? [ In reply to ]

jon at tgpsolutions

Feb 11, 2004, 12:12 PM

Post #3 of 4 (869 views)

Permalink

On Wed, 2004-02-11 at 10:21, Jeremy Olmen wrote:
> I've got a mailserver right now running 5 seperate domains for 5 seperate
> organizations. I'd like to install Spamassassin into the mail pipeline (I'm
> using qmail). Can Spamassassin be configured to use a different local.cf
> depending on domain the message is going to? If this is possible, how would
> I configure it?

If you're using qmail, you can use qmail-scanner to invoke SA. By
default, qmail-scanner invokes spamc with the user argument set to the
recipient, but can pretty easily hack it to only send the domain as the
user argument. Then spamc will use a different per-user pref per
domain. I don't run this setup myself, but it *should* work...

> These different organizations will probably have very
> different whitelist/blacklist entries. In addition, is it possible to have a
> domain specific local.cf and then a sitewide local.cf for bad addresses that
> are considered always spam by everyone?

The sitewide local.cf should do it, since the per-domain stuff is in the
user prefs.

- Jon

--
jon@tgpsolutions.com

Administrator, tgpsolutions
http://www.tgpsolutions.com

Re: Spamassassin using different local.cf's for different domains? [ In reply to ]

ryan.moore at perigee

Feb 11, 2004, 12:30 PM

Post #4 of 4 (866 views)

Permalink

We use amavid-new to enable sql preferences where our domain customers
can change the required_hits variable for their address/domain or
whitelist/blacklist people. All rules and the bayes database are
site-wide across all domains, but it has been working really well for us.

Ryan Moore
----------
Perigee.net Corporation
704-849-8355 (sales)
704-849-8017 (tech)
www.perigee.net

Jeremy Olmen wrote:
> I've got a mailserver right now running 5 seperate domains for 5 seperate
> organizations. I'd like to install Spamassassin into the mail pipeline (I'm
> using qmail). Can Spamassassin be configured to use a different local.cf
> depending on domain the message is going to? If this is possible, how would
> I configure it? These different organizations will probably have very
> different whitelist/blacklist entries. In addition, is it possible to have a
> domain specific local.cf and then a sitewide local.cf for bad addresses that
> are considered always spam by everyone? I've thought about running jails,
> with totally seperate binaries of qmail and spamassassin, but that creates a
> lot more overhead for me when a new organization want's their mail hosted on
> this box (have to re-install/configure everything in a new jail). Any
> thoughts?
>
>
> Thanks!
>
>
> --Jeremy
>
>

Mailing List Archive

Mailing List Archive

Attached Files: