Topic: SPam Assassin whitelist location

[idyll]

I need to enter my whitelists from a previous 6.0.1 installation.

What is the path on the 7.0 PR 1?

thanks

regards,

patrick

[raem]

idyll

/home/e-smith/db/spamassassin

[idyll]

Ray...thanks.

it seems /etc/mail/spamassassin is where the whitelist.cf should reside.

There is a reference to this list in the link you provided, but not a list, per say.

regards,

patrick

[raem]

idyll

>.... but not a list, per say.

If there was a server manager panel for the white list entries (which there is not at present) then the whitelist entries would go into the spamassassin db.
See below for the format.
You need to put them there manually, either directly editing the spamassassin db or by using the db.... command.

When you expand templates and restart spamassassin it will read the data into /etc/mail/spamassassin/local.cf

expand-template /etc/mail/spamassassin/local.cf
svc -t /service/spamd

There are templates in /etc/e-smith/templates/etc/mail/spamassassin/local.cf that relate to this.

# DO NOT MODIFY THIS FILE.
# This file is automatically maintained by the Mitel Networks SME Server
# configuration software.  Manually editing this file may put your
# system in an unknown state.
#
# updated: Sun Mar 19 10:23:09 2006
wbl.global=list|*domain.com.au|White|footytips@triumph.com.au|Black


I tried the above just now on a sme7 test server and the white/black list functionality is working.

[idyll]

I hand edited the db file and hope a contrib finds its way into the mix as inserting this many addresses is problematic.

I appreciate the pointers. Thanks.

regards,

patrick

[jfarschman]

Ray,

  That's good information, but I'm missing one thing.  How do I add using the db commands.  I don't know the keys.

db spamassassin set key type [prop1 val1] [prop2 val2] ...

Do you have an example to get me started?  Thanks.

[jfarschman]

Is it like this:

db spamassassin set wbl.global list *somedomain.com white

then;

# db spamassassin show
wbl.global=list
    *somedomain.com=white
wbl.global_to=list

I tried this and expanded the template, but it did not make an entry to /etc/mail/spamassassin/local.cf  That's probably best if I got the formatting messed up.

[jfarschman]

My apologies,

  It's late and I'm tired.  The proper method seems to be:

db spamassassin setprop wbl.global *@*vonage.com White
db spamassassin setprop wbl.global *domain2.com White
expand-template /etc/mail/spamassassin/local.cf
svc -t /service/spamd

[brianr]

svc -t /service/spamd

You are not advised to use "svc" as far as I know - better to use

/etc/rc.d/init.d/spamassassin restart

If I am wrong perhaps someone can correct it..

[raem]

jfarschman

You can put all the required entries into the one command eg

db spamassassin setprop wbl.global *@*vonage.com White *domain2.com White *domain3.com Black
(all on one line)

expand-template /etc/mail/spamassassin/local.cf
svc -t /service/spamd

[raem]

brianr

>...You are not advised to use "svc" as far as I know...

I believe it was the "service" command that is deprecated since around sme5.6. It did not always perform everything that was required of it in all circumstances on sme server.

The "svc" program controls services monitored by supervise.
ie
svc -t /service/xxxxx
is the correct way to do it now since sme6.

although
/etc/rc.d/init.d/spamassassin restart
or the shorter
/etc/init.d/spamassassin restart
still work but svc..... is now preferred/recommended.

See
http://cr.yp.to/daemontools/svc.html
&
http://cr.yp.to/daemontools/supervise.html

[cctmx]

thank you for this precieuses information, but to put only one address of the type:  would toto@toto.com in white list, which be the order exact?

thx  ;-)

[jfarschman]

CC,

  You'd do it the way I did it above:

db spamassassin setprop wbl.global *domain2.com White
expand-template /etc/mail/spamassassin/local.cf
svc -t /service/spamd


So you'd do it line by line altering only this part:

*domain2.com White

Be careful about the capital letters.

[morpheusx]

Are there any plans for a Web interface for this? Whitelisting domains etc is a commonly requested item, but requiring mulitple steps at the command line is going to be beyond the ability of many SME admins.

Also, the spam configuration options on the email filtering page are non-intuitive and could do with a redesign. For a start, if spam sensitivity is not set to 'Custom', the two custom fields should be greyed out.

[jfarschman]

Morpheus,

  Take a look at bugzilla.  There is a bug there where you should share your two cents.

http://bugs.contribs.org/show_bug.cgi?id=807