[dspam-users] invalid sigantures after upgrade to 3.6.4

Hi folks,

Last night I upgraded from 3.4.9 to 3.6.4. The upgrade went pretty well and
I could not detect any problems. I had pre-configured a new dspam.conf file
so I was already to go. I decided to take advantage of the
MySQLUIDInSignature feature so I could simplify my aliases in the near
future. * *This morning I had some problem reports. In some cases, if a
user wanted to retrain a message, it wouldn't work. That is the user would
click on 'As Innocent' and the screen would refresh and the message would
still be marked spam.

I poked around and found that in cases where the above happened, the
signature was a 'pre-MySQLUIDInSignature' signature. When I tried to
retrain the message on the command line with the 'old' signature, I would
get:

Unable to find a valid signature. Aborting.

I saw this in my apache error logs too. It looked to me like none of the
'old' signatures were being recognized by the dspam binary any more. If I
did a select in mysql, I could find the signature with no issue.

Well I went to dspam.conf and turned off MySQLUIDInSignature and restarted
the daemon. That seems to have fixed it, except I do have a report of a
retrained message not being delivered. :-(

I did some digging in the dspam-users archives and did not see this specific
issue come up before. If I'm mistaken please let me know.

I checked to see if my mysql v4.1 was susecptible to the bug and according
the tests, it is not. However, I could see that being the case here. So my
basic question is, could this behavior be attributed to the mysql 4.1 bug or
is there any reason the two signature schemes cannot co-exist?

--
Mike S
http://www.saneinc.net