Description of problem: When mimedefang is started during system boot, I find the following messages in my maillog. After restarting mimedefang manually, everything works for me: Oct 26 16:06:30 tux mimedefang-multiplexor[2093]: Slave 1 stderr: auto- whitelist: open of auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile //.spamassassin/auto-whitelist.lock.tux.17594 for //.spamassassin/ auto-whitelist.lock: No such file or directory Somebody an idea how to fix this? Version-Release number of selected component (if applicable): mimedefang-2.57-5 How reproducible: Everytime, see above. Actual results: Error messages when mimedefang is started up during booting time. Expected results: No error messages.
Looks like a small bug, I'll fix by using this workaround soon: http://lists.roaringpenguin.com/pipermail/mimedefang/2006-August/030689.html http://lists.roaringpenguin.com/pipermail/mimedefang/2006-August/030691.html
I sent a small patch upstream which will be applied to 2.58 when it gets released. As nobody else using this package reported the problem to me, I'll try to wait for the update for now.
2006-11-07 David F. Skoll <dfs> * VERSION 2.58 RELEASED [...] * Sample init script sets HOME=/var/spool/MIMEDefang.
Fixed in 2.58-1 which should appear in the repositories soon. 21229 (mimedefang): Build on target fedora-development-extras succeeded. 21230 (mimedefang): Build on target fedora-6-extras succeeded. 21231 (mimedefang): Build on target fedora-5-extras succeeded.