Hello,
Any progress with this issue?
regards,
David Davidov
On 06/18/2013 06:47 PM, David Davidov wrote:
Hi Sam,
I am a colleague of Theodor. This is a simple way to trigger the problem:
dave~$ telnet mx.example.com 25
Connected to mx.example.com
Escape character is '^]'.
220 mx.example.com ESMTP
mail from: test-sen...@mx.example.com
250 ok
rcpt to: test-r...@mx.example.com
250 ok
data
354 go ahead
.
250 ok 1370523483 qp 26283
mail from: test-sen...@mx.example.com
250 ok
rcpt to: test-r...@mx.example.com
250 ok
data
354 go ahead
.
250 ok 1370523502 qp 26625
The first message produces one log entry:
Jun 18 15:58:03 mx spamdyke[26194]: ALLOWED from:
test-sen...@mx.example.com to: test-r...@mx.example.com origin_ip:
213.145.98.39 origin_rdns: ws.example.com auth: (unknown) encryption:
(none) reason: 250_ok_1370523483_qp_26283
But for the second message we have two entries:
Jun 18 15:58:22 mx spamdyke[26194]: ALLOWED from:
test-sen...@mx.example.com to: test-r...@mx.example.com origin_ip:
213.145.98.39 origin_rdns: ws.example.com auth: (unknown) encryption:
(none) reason: 250_ok_1370523502_qp_26625
Jun 18 15:58:22 mx spamdyke[26194]: ALLOWED from:
test-sen...@mx.example.com to: test-r...@mx.example.com origin_ip:
213.145.98.39 origin_rdns: ws.example.com auth: (unknown) encryption:
(none) reason: 250_ok_1370523502_qp_26625
We use spamdyke ver. 4.3.1 locally compiled on Debian 6.0.7.
No header filtering. Here is our spamdyke.conf
---
greeting-delay-secs=0
reject-empty-rdns
log-level=info
idle-timeout-secs=300
ip-whitelist-file=/home/vpopmail/etc/spamdyke_whitelist.txt
recipient-whitelist-file=/var/qmail/spamdyke_recipient_whitelist.txt
dns-whitelist-entry=antirbl.example.com
graylist-level=always
graylist-dir=/var/qmail/graylist
graylist-min-secs=60
tls-certificate-file=/var/qmail/control/servercert.pem
tls-privatekey-file=/var/qmail/control/servercert.pem
local-domains-file=/var/qmail/control/rcpthosts
local-domains-file=/var/qmail/control/morercpthosts
dns-timeout-secs=3
rejection-text-empty-rdns=Refused. You have no reverse DNS entry.
Contact ab...@example.com for details.
rejection-text-ip-in-cc-rdns=Refused. Your reverse DNS entry contains
your IP address and a country code. Contact ab...@example.com for details.
rejection-text-unresolvable-rdns=Refused. Your reverse DNS entry does
not resolve. Contact ab...@example.com for details.
---
BRs,
David Davidov
On 01/-10/-28163 09:59 PM, Sam Clippinger wrote:
I'm very sorry it's taken so long to get back to you on this; I've been
buried at work and haven't had any time to investigate.
It definitely sounds like you've hit a bug. spamdyke does save the
addresses of all the recipients in order to print them all out in a loop,
but only when the header blacklist feature is enabled. It does this because
the recipient names have already gone by before the message header is sent,
so it must save the recipient addresses to print either ALLOWED or
DENIED once the header is finished.
But it should only do this once and I'm not seeing a way to trigger that
code more than once, though it certainly looks like that's what's happening.
So let me start with all the standard questions: what OS and version are
you on? What version of spamdyke are you using? Could you please post your
configuration file(s) (or send them to me directly)? Would you mind turning
on spamdyke's full logging feature (the full-log-dir option) and capturing
one of these sessions?
Needless to say this behavior isn't by design and it's not happening on any
of the servers I manage (and I use the header-blacklist feature on every
one). After spending a little while testing and tracking through the code I
can't reproduce this problem, so I suspect it's a combination of environment
and a specific configuration you're using. I'd love to track this down and
fix it!
-- Sam Clippinger
--
David Davidov | System Administrator | ICDSoft Ltd.
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
