http://bugzilla.spamassassin.org/show_bug.cgi?id=3331





------- Additional Comments From [EMAIL PROTECTED]  2004-05-02 09:35 -------
I've worked up a patch that allows the original text (which is called
token text or ttext in the code) to be optionally kept in the
database, this only works for DBM.  The default value is off.

The new keep_token_text option can be turned on or off at any time.
While off token text will be deleted as tokens are encountered (rather
than wiping the whole database), while on token text will be added as
they are encountered, including for touches.

I've modified the SQL backend to return empty strings for token
text, BUT I HAVE NOT TESTED THIS CODE.

This does not require a new format.  I was considering using the
format field (see FORMAT_FLAG near the bottom of DBM.pm) to indicate
the presence of ttext in a packed token, but decided against it since
that would preclude an additional compact token format (the format
field is two bits).  The code relies on DB_File to provide a packed
string of the correct length.  If it's longer than it should be it
will be interpreted as token text (but this will only impact parts
that display token text retrieved from the database, such as dump and
backup).




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to