On Feb 6, 2007, at 9:06 PM, Michael Alger wrote:
Well, you could always build a script which sends ten (or however
many) emails from the address to be whitelisted, with special magic
text in them which a) ensures it's not marked as spam and b) can be
detected and removed after processing by dspam (rather than sent to
their mailbox).
On a more serious note, it's probably worth looking into exactly how
dspam whitelists senders. I have a feeling it goes by the entire
"From:" line rather than just the email address, which might explain
why there's currently no tools to simply add an email address to
the whitelist.
You can just insert the token right into the database with 10
innocent hits and no spam hits using mysql. There are bayesian
(weakens your training) and mail management (opens you up to
spoofing) reasons why it's a bad idea, but that is no reason not to
answer the question.
A whitelist token looks like this:
ronin-root# dspam_dump gfivetest "[EMAIL PROTECTED]"
17322439112541161595 S: 00000 I: 00050 P: 0.0100
From*entire from string
If the From string is "Some Name" <[EMAIL PROTECTED]> then the token is
From@"Some Name" <[EMAIL PROTECTED]>
NOTE that the raw From string will not always be what your client
displays, sometimes it helpfully shows the contents of your address
book, or reformats, so in case it doesn't go without saying, you have
to look at the raw source of the message, which most email clients
should let you do.
casino-root# dspam_dump user "From*gabrielle singleton
<[EMAIL PROTECTED]>"
3771600864741775287 S: 00000 I: 00050 P: 0.0001
NOTE also these were inserted in the database from different periods
in mail, the first when I had no full name set. Only one magic
whitelist From string token is set for each message dspam processes.
These live in the token database (dspam_token_data), get the crc for
the thing you want to insert:
casino-root# dspam_crc [EMAIL PROTECTED]
TOKEN: '[EMAIL PROTECTED]' CRC: 17322439112541161595
insert into the token data for the user you want to effect the
whitelist for with at least 10 innocent hits and 0 spam hits.
you can also use this to correct an address which has a spam hit or
hits that was uncorrected by retraining... this was a bug in the 3.2
branch with whitelisting, which is how I came to know so much about
whitelist tokens... "but i got 10 emails from so and so" =)
such as this one:
casino-root# dspam_dump gfivetest 'From*"Example P. User"
<[EMAIL PROTECTED]>'
9352389259902468861 S: 00003 I: 00131 P: 0.0180
You can find info on mysql INSERT or UPDATE anywhere on the web.
Gabrielle
