James Cloos wrote on 27/05/2007 17:48: > I get this on startup with the current version of spampd:
F*** You are right. Sorry for not noticing this when I checked the fixed up patch. > Starting spam checking proxy daemon: spampd > util: cannot untaint path: "REF(0x8c6d024)/bayes" > util: cannot untaint path: "REF(0x8c6d024)" > util: cannot untaint path: "REF(0x8c6d024)" > pyzor: check failed: internal error > util: cannot untaint path: "REF(0x8c6d024)" > util: cannot untaint path: "REF(0x8c6d024)/auto-whitelist" > util: cannot untaint path: "REF(0x8c6d024)/auto-whitelist.lock.HOSTNAME.23429" > auto-whitelist: open of auto-whitelist file failed: \ > locker: safe_lock: cannot create tmp lockfile \ > REF(0x8c6d024)/auto-whitelist.lock.HOSTNAME.23429 \ > for REF(0x8c6d024)/auto-whitelist.lock: \ > No such file or directory > > (I replaced the host's name with HOSTNAME above.) > > Dropping back to 2.30-16 fixes it. > > The home directory looks to be called w/o a deref, yes? Exactly. > Thanks for packaging spampd; I find that it gets the job done better > than the alternatives for using spamassassin. I must admit that I don't use it myself anymore. It just didn't want to work with the SpamAssassin FuzzyOCR plugin, so I switched to using my amavisd-new (which already did the virus scanning) for SpamAssassin checks, too. Regards, Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
