Is there a LANG=UTF-8 or some such setting that you could maybe use?
Loren
Ross,
You're not the only one to run into the problem. I had converted out
database over to UTF8 and didn't think anything about it until about a
week later when the spam started pouring in. It still seemed to learn,
it just couldn't select (i.e. compare).
I figured maybe it was the upgraded
Andre Nicholson wrote:
This happens when scanning incoming messages and trying to sa-learn them
manually. The
errors cause no tokens to be available and thus bayes is ignored. Other than
reverting
to a backup of the database, is there something I can do or look at to fix
this? I've
never seen
Do not use 3.0 with PostgreSQL. It's known to have problems. Actually,
the problem you're seeing might be DBD::Pg related. Did you possibly
just install a new version? Make sure you are using the version listed
in sql/README.bayes.
I haven't noticed anything out of the ordinary after I made
