Date: Fri, 21 Dec 2007 08:18:25 GMT From: Robin Gruyters <r.gruyters@services.betronic.nl> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/118926: spamd: issues with deletion and syncing from spam db Message-ID: <200712210818.lBL8IPNF004824@www.freebsd.org> Resent-Message-ID: <200712210820.lBL8K1RR059030@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 118926 >Category: ports >Synopsis: spamd: issues with deletion and syncing from spam db >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Dec 21 08:20:01 UTC 2007 >Closed-Date: >Last-Modified: >Originator: Robin Gruyters >Release: FreeBSD 5.5-RELEASE-p17 >Organization: Betronic Nederland B.V. >Environment: FreeBSD se-st-01 5.5-RELEASE-p17 FreeBSD 5.5-RELEASE-p17 #2: Thu Dec 4 15:54:43 CEST 2007 root@se-mt-01:/data/obj/data/src/sys/YIRDIS i386 >Description: The day before yesterday I have installed OpenBSD spamd from the ports (mail/spamd) on one of our MX servers and let it run for a few ours. When the deletion starts, I noticed some errors: Dec 20 17:09:02 se-st-01 spamd[50862]: queueing deletion of .21.82 [59.93.21.82] <eygmp@brandstudio.com> <donbentvelzen@betronic.n Dec 20 17:09:02 se-st-01 spamd[50862]: queueing deletion of .21.82 [59.93.21.82] <eygmp@brandstudio.com> <donbentvelzen@betronic.n Dec 20 17:09:02 se-st-01 spamd[50862]: queueing deletion of .21.82 [59.93.21.82] <eygmp@brandstudio.com> <donbentvelzen@betronic.n Dec 20 17:09:02 se-st-01 spamd[50862]: can't delete .21.82 [59.93.21.82] <eygmp@brandstudio.com> <donbentvelzen@betronic.n from spamd db (Unknown error: 0) Dec 20 17:09:02 se-st-01 spamd[50862]: can't delete .21.82 [59.93.21.82] <eygmp@brandstudio.com> <donbentvelzen@betronic.n from spamd db (Unknown error: 0) Dec 20 17:09:02 se-st-01 spamd[50862]: can't delete .21.82 [59.93.21.82] <eygmp@brandstudio.com> <donbentvelzen@betronic.n from spamd db (Unknown error: 0) .. And this one is quite weird as well: Dec 20 17:17:02 se-st-01 spamd[50862]: can't delete oo.co.jp <charlotte5_obote@yahoo.co.jp> <info@yirdis.nl>r~jG²¶jG²¶jG^A from spamd db (Unknown error: 0) Dec 20 17:18:03 se-st-01 spamd[50862]: queueing deletion of oo.co.jp Dec 20 17:18:03 se-st-01 spamd[50862]: queueing deletion of oo.co.jp <charlotte5_obote@yahoo.co.jp> <info@yirdis.nl>r~jG²¶jG²¶jG^A Dec 20 17:18:03 se-st-01 spamd[50862]: queueing add of oo.co.jp Dec 20 17:18:03 se-st-01 spamd[50862]: whitelisting oo.co.jp in /var/db/spamd .. I Also noticed these messages to pop up from time to time: Dec 20 17:10:02 se-st-01 spamd[50862]: bogus entry in spamd database Dec 20 17:10:02 se-st-01 spamd[50862]: scan of /var/db/spamd failed .. I have even tried the latest CVS/SVN release freebsdspamd http://svn.berlios.de/svnroot/repos/freebsdspamd/trunk, but no luck. Here some ldd output from spamd and spamdb: /usr/local/libexec/spamd: libcrypto.so.3 => /lib/libcrypto.so.3 (0x2807f000) libmd.so.2 => /lib/libmd.so.2 (0x28176000) libc.so.5 => /lib/libc.so.5 (0x28183000) /usr/local/sbin/spamdb: libc.so.5 => /lib/libc.so.5 (0x28077000) I have kept a copy of the 'so called bogus' spam db. So, if it need more debugging or digging through, just let me know. I have already contacted the port maintainer, Alex Samorukov, and he thinks it (could be)/is more FreeBSD specific. Kind regards, Robin Gruyters >How-To-Repeat: I have tried to reproduce it, but the only way to reproduce it, is to run (ob)spamd in greylisting mode and wait when the deletion starts. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200712210818.lBL8IPNF004824>