Hi Sam,
first of all thanks for your time and inputs!
We tried your patch (attached) and it compiles fine but unfortunately
does now work as we need.
It exits immediately after "RCTP TO" but without any message regarding RBL:
Trying 195.10.84.201...
Connected to 195.10.84.201.
Escape
I'm very sorry it's taken me so long to get back to you about this!
If you're willing to edit the code, I suggest changing spamdyke.c. Change line
1615 (the first line of an if statement) to this:
if (
And change line 1644 (the call to filter_dns_rbl()) to this:
if
Thanks Sam for your answer,
anyway it is crucial for us to avoid letting the timeout expire after
"RCTP TO" message in case of RBL check. So, even developing a custom
patch, we need something to prevent clients keeping the connection open
after "554 Refused. Your IP address is listed in the
Unfortunately no, spamdyke isn't designed with the idea of different timeouts
for different reasons. It will always keep the connection open as long as
there is any chance the message could be allowed. For example, if your
configuration includes a recipient whitelist and the remote IP is
Hi,
some months ago we switch from rblsmtpd to spamdyke in order to have
more info in the log about blocked IP. But after switch to spamdyke the
number of concurrency incoming SMTP sessions was increased about 10 time.
This because with rblsmtpd we set a timeout of 10 seconds and spamdyke
