Date: Sat, 9 May 2009 18:40:03 GMT From: "Olli Hauer" <ohauer@gmx.de> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/134347: mail/spamd: spamlogd's whitelist expiration period is hardcoded Message-ID: <200905091840.n49Ie3jd007143@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/134347; it has been noted by GNATS.
From: "Olli Hauer" <ohauer@gmx.de>
To: bug-followup@FreeBSD.org, rs@bytecamp.net, ohauer@gmx.de
Cc:
Subject: Re: ports/134347: mail/spamd: spamlogd's whitelist expiration period
is hardcoded
Date: Sat, 09 May 2009 20:33:11 +0200
Hi,
is it possible that you have also spamlogd running?
spamd honors the times given (spamd.c line ~1132 variable whiteexp),
but if you have spamlogd running then the white times are pushed to
36 days (from grey.h) after the sending machine is whitelisted and
connects to your MTA.
See the following test.
# -- file /etc/rc.conf.local
obspamd_enable="YES"
obspamd_times="-G 1:6:2"
obspamd_flags="-5 -v -l127.0.0.1 -S0 -s0 ${obspamd_times}"
# 1st. connect
# spamdb
GREY|127.0.0.1|foo|sender@example.com|rcpt@example.com|1241892180|1241913780|1241913780|1|0
# 2nd. connect after one minute
# spamdb
GREY|127.0.0.1|foo|sender@example.com|rcpt@example.com|1241892180|1241892278|1241913780|2|0
# again after DB_SCAN_INTERVAL 60
# spamdb
WHITE|127.0.0.1|||1241892180|1241892278|1241899531|2|0
Now look at the timestamps from the white entry
# date -j -r 1241892180
Sa 9 Mai 2009 20:03:00 CEST
# date -j -r 1241892278
Sa 9 Mai 2009 20:04:38 CEST
# date -j -r 1241913780
Sa 9 Mai 2009 22:05:31 CEST
The whitelist time is around 2 hours.
//olli
--
Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905091840.n49Ie3jd007143>