Best approach for forcing whitelisting would be to modify DSPAM to allow whitelisting from the command line with parameters. This approach would ensure that all the different storage backends would be able to get updated whitelisting. But I don't think that it would be a wise idea to go that path (I mean the forced whitelisting).

Do others on the list see a huge benefit if we would have forced whitelisting possibility from the command line?


IMHO a whitelist feature in preferences would be more easy (I guess, but I'm not a programmer, that it should be easier to bypass dspam once preference are loaded, than update all stuffs in tokens) and more useful, many users here are asking for such a feature They also ask for some "unwhitelist" feature from the users automagicaly whitelisted, or at least a way to list them

In the meantime maybe adding blacklist could be appreciate too ;)

Regards.

!DSPAM:1011,486688d2150921699115446!


Reply via email to