spam-use-whitelist(see Blacklists and Whitelists), but uses the BBDB as the source of whitelisted addresses, without regular expressions. You must have the BBDB loaded for
spam-use-BBDBto work properly. Messages whose senders are not in the BBDB will be sent to the next spam-split rule. This is an explicit filter, meaning that unless someone is in the BBDB, their messages are not assumed to be spam or ham.
Set this variable to
tif you want to use the BBDB as an implicit filter, meaning that every message will be considered spam unless the sender is in the BBDB. Use with care. Only sender addresses in the BBDB will be allowed through; all others will be classified as spammers.
spam-use-BBDB-exclusivecan be used as an alias for
spam-use-BBDBas far as
spam.elis concerned, it is not a separate back end. If you set
spam-use-BBDB-exclusiveto t, all your BBDB splitting will be exclusive.
Add this symbol to a group's
spam-processparameter by customizing the group parameters or the
gnus-spam-process-newsgroupsvariable. When this symbol is added to a group's
spam-processparameter, the senders of ham-marked articles in ham groups will be added to the BBDB.
Instead of the obsolete
gnus-group-ham-exit-processor-BBDB, it is recommended that you use
(ham spam-use-BBDB). Everything will work the same way, we promise.