Richard Freeman <[EMAIL PROTECTED]> wrote: > Elias Oltmanns wrote: >> Richard Freeman <[EMAIL PROTECTED]> wrote: >>> Elias Oltmanns wrote: >>>>> /usr/bin/dspam --source=error --class=spam --user root < /tmp/msg.txt >>>> So, is there a virtual uid assigned to root in your database at all? >>>> >>> Where would it be stored if there were? >> >> Exactly where the virtual uids for all the other dspam users are stored >> too. > > Hmm - in my head then. Sure, I know about it... :) > >> >>> Note that this signature is not for the user root - I just had to >>> specify something otherwise it won't work. >> >> I realise that. However, it is absolutely crucial that the user >> specified on the commandline as argument to the user option should be >> known to dspam, i.e., there has to be a matching entry in the >> dspam_virtual_uids table. Dspam will switch to the uid given in the >> signature eventually, but you still have to start out with a known user. >> > > Ah, well, the fact that I don't have a dspam_virtual_uids table in my > database might be the source of the problem, then. I also do not have > virtual users enabled. The root user does exist in /etc/passwd > (unsurprisingly).
Firstly, is root listed as a trusted user in your dspam.conf? If so and the problem still exists, I wonder whether the automatic uid switching when retraining messages requires virtual users to be enabled at build time. Try that and add root as well as the user with the uid in your test signature to the table of virtual users. Also, make sure that MySQLVirtualTable, MySQLVirtualUIDField, and MySQLVirtualUsernameField are set apporpriately (and taht MySQLUIDInSignature is turned on, of course). Regards, Elias
