Sydney Bogaert said the following on 02/04/07 23:22: >> Seems that the problem has to do with the way the training aliases are >> configured. The documentation says that if we use the mysql uid in the >> signature we would be able have a single spam and ham >> training alias for >> the system. It also points out that we MUST specify the user root so >> that dspam doesn't bail out with an error and that the user will be >> changed internally. >> >> Well the problem has to do with that, dspam is actually trying to look >> up the user in the system and is not changing to the user id in the >> signature. See the logs below. >> > > Is the user 'root' an actual user in your configuration ? > e.g. is the user 'root' in the list of users returned by dspam_stats ? > If not, take any other user in the list, one that IS in the list.
Yeah, thanks it works fine now!!! There is just one think that is looking weird now, when I message is detected as spam the header X-DSPAM-Result always shows Innocent. I know it is spam because DPSAM has put a tag in the Subject line and the probability is 1 in 151 chance of being ham. Would you know if it could be a bug? Thanks Vini
