Thanks. Once I have this all figured out, I will write up something and
put it on my homepage and post a link to it here.

> > >> A SHA1 hash is taken of the original token value, and the bottom 40
> > >> bits are used as the token from then-on.  There is a plugin call
> > >> which can be used to store raw token -> hash value data, but
> > >> otherwise the raw token information is lost after the message is
> > >> processed.
> > > 
> > > Where could I find more information about the plugin call that allows
> > > me to do this? 
> > 
> > perldoc Mail::SpamAssassin::Plugin
> 
> In particular:
> 
> http://spamassassin.apache.org/full/3.1.x/doc/Mail_SpamAssassin_Plugin.html#item_bayes_scan
> http://spamassassin.apache.org/full/3.1.x/doc/Mail_SpamAssassin_Plugin.html#item_bayes_learn
> 
> > You should also search the dev list from a couple of years ago at least.
> > Lots of discussion about the change and why it was done including, if
> > memory serves me correctly, a proof of concept plugin to save off the
> > token values.
> 
> by the way, a nice, working plugin that does this would be quite useful on
> the CustomPlugins wiki page, or contributed as an optional plugin...

+----------------------------------------+
| Stuart Robinson                        |
| Email: stuart at zapata dot org        |
| Homepage: http://www.zapata.org/stuart |
+----------------------------------------+

Reply via email to