On 12/17/2009 11:17 AM, RW wrote: >> If you're using file-based bayes, there's no good way to share >> > updates between one DB and the other. The information needed to make >> > such a merger successful isn't stored, because it is not needed for >> > any reason within SpamAssassin. The database merely stores the token, >> > it's spam count, it's nonspam count, and a last-seen timestamp. If >> > you look at the same token in 2 different databases, you can't really >> > merge these counts, because you don't know how many occurred since >> > your last merge. >> > I'm not saying it's a good idea, but it is possible provided that you > retained the result of the previous merge. It should be simple to > script too. > > Agreed I didn't mean to say that a merge is impossible, it's just not with the tools that SA comes with, and you need more info than just what's in the current database.
As you mentioned, you'd need a custom script (not wildly complicated for a good perl scripter, but beyond the bounds of someone with only crude scripting skills.) as well as historical copies of each database from the last merge. Setting up SQL would be much easier.
