Blacklist and whitelists

[sven]

Only one idea: Because spamassassin's user preferences has also white- and blacklist options, i think this could also be stored in the spammassassin mysql table for each user.

What do you think about it?

[jonas]

This makes no sense. Bogofilter does not have any black/whitelisting feature. And adding this to the spamassassin table, it will blow up the database.

example: you get an mail from bar@… this domain foo.com is in the whitelist in the spamassassin table. maildrop will call spamassassin, spamassassin opens the mail and check if bar@… is whitelisted. So you are calling spamassassin into your memory without any success.

Using an perl script and maildrop it's faster and more flexible for new spamfilter software. (one white/blacklist for all spamfilter software)

[sven]

It's a pity because this should only be an add on for each user. I do not use Bogofilter - i think spamassassin and his plugins makes a good job (i hope so).

I do not think, that the database would blow up so much, because it's only a little feature - think about: What is spam to some people is not spam to everyone!

[jonas]

Yes, but CpVES supports Bogofilter _and_ spamassassin. So I need such a solution.

Inserting data to both tables is crazy and it's harder to program an backend and frontend, if you the same data on both tables. So the sa_wb_listing.pl makes an good job to prevent to much load on the cpu (not calling spamassassin if in whitelist).