What I meant was this: could it be that spamdyke is actually doing what
it is supposed to do. Is spamdyke timing out a connection when it takes
to long and allowing connections when the connection is within the time
limit?
In other words, how do you know its not working properly?
On 11/4/2016 10:27 AM, [email protected] wrote:
what are you mean?
*From:*Eric Broch [mailto:[email protected]]
*Sent:* Friday, November 04, 2016 5:22 PM
*To:* [email protected]
*Subject:* Re: [qmailtoaster] Qmail reject email from several domain
Reason TIMEOUT
Could it be that the TIMEOUT is legitimate?
On 11/4/2016 10:17 AM, [email protected] <mailto:[email protected]> wrote:
Sadly TIMEOUT still occurs L
I add timeouted domain to whitelist _senders. And still TIMEOUT.
Bellow my spamdyke.conf file:
################################################################################
# TIMEOUTS
################################################################################
# Close the connection after SECS seconds, regardless of
activity. A value of
# 0 disables this feature.
# Default: 0
connection-timeout-secs=360
# Close the connection after SECS seconds of inactivity. A value
of 0 disables
# this feature.
# Default: 0
idle-timeout-secs=360
#dns-blacklist-entry=zombie.dnsbl.sorbs.net
#dns-blacklist-entry=dul.dnsbl.sorbs.net
#dns-blacklist-entry=bogons.cymru.com
dns-blacklist-entry=zen.spamhaus.org
dns-blacklist-entry=bl.spamcop.net
graylist-dir=/var/spamdyke/graylist
graylist-level=always
graylist-max-secs=2678400
graylist-min-secs=180
greeting-delay-secs=6
header-blacklist-entry=From:*>,*<*
idle-timeout-secs=60
ip-blacklist-file=/etc/spamdyke/blacklist_ip
ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
ip-whitelist-file=/etc/spamdyke/whitelist_ip
########local-domains-file=/var/qmail/control/rcpthosts
qmail-rcpthosts-file=/var/qmail/control/rcpthosts
qmail-morercpthosts-cdb
log-level=info
#log-level=excessive
log-target=stderr
max-recipients=50
#policy-url=http://my.policy.explanation.url/
rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
reject-empty-rdns
#reject-ip-in-cc-rdns
#################reject-missing-sender-mx
reject-sender=no-mx
reject-unresolvable-rdns
rejection-text-sender-no-mx
reject-recipient=same-as-sender
rejection-text-recipient-same-as-sender
sender-blacklist-file=/etc/spamdyke/blacklist_senders
sender-whitelist-file=/etc/spamdyke/whitelist_senders
tls-certificate-file=/var/qmail/control/servercert.pem
tls-privatekey-file=/var/qmail/control/servercert.key
tls-level=SMTP
*From:*Eric Broch [mailto:[email protected]]
*Sent:* Friday, November 04, 2016 4:31 PM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [qmailtoaster] Qmail reject email from several
domain Reason TIMEOUT
Settings change between spamdyke 4 and 5
I have a script (fixsd.sh):
<fixsd.sh>
#!/bin/sh
sed -i \
-e 's/reject-missing-sender-mx/reject-sender=no-mx/g' \
-e
's/rejection-text-missing-sender-mx/rejection-text-sender-no-mx/g' \
-e
's/reject-identical-sender-recipient/reject-recipient=same-as-sender/g'
\
-e
's/rejection-text-identical-sender-recipient/rejection-text-recipient-same-as-sender/g'
\
-e 's/local-domains-file/qmail-rcpthosts-file/g' \
-e 's/local-domains-entry=/#local-domains-entry=(Add these entries
to qmail-rcpthosts-file)/g' \
-e 's/morercpthosts/qmail-morercpthosts-cdb/'g
/etc/spamdyke/spamdyke.conf
</fixsd.sh>
If this doesn't work, can you refert to spamdyke 4 and let us know
if that works?
Eric
On 11/4/2016 9:09 AM, [email protected] <mailto:[email protected]> wrote:
I upgrade spamdyke to version 5.0.1 and nothing change. L
I expand to:
'idle-timeout-sec=360'
And still TIMEOUT
*From:*Eric Broch [mailto:[email protected]]
*Sent:* Friday, November 04, 2016 2:17 PM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [qmailtoaster] Qmail reject email from several
domain Reason TIMEOUT
It looks to me like it's spamdyke causing the problem. It's
certainly what the log suggests. What is your 'idle-timeout'
setting in /etc/spamdyke/spamdyke.conf
On 11/4/2016 4:31 AM, [email protected] <mailto:[email protected]>
wrote:
Hi,
From some time i have a problem with my qmail server. From
some time the server reject mail from several domain
REASON TIMEOUT. I don’t know why. This occurs only on
several big corporate domain like dhl.com man.eu
ergohestia.pl. First i suspect spamdyke. But i check it.
Enter white list etc. Ask on spamdyke forum and final look
at the spamdyke don’t block anything.
The excessive log file show only: “talk faster next time”
A part of log bellow:
@40000000581c48af3996f15c tcpserver: status: 2/100
@40000000581c48d908f1b21c spamdyke[4387]:
EXCESSIVE(middleman()@spamdyke.c:1965): child output file
descriptor 5 closed
@40000000581c48d908f1bdd4 spamdyke[4387]:
EXCESSIVE(output_writeln()@log.c:102): wrote 37 bytes to
network file descriptor 1, buffer contained 37 bytes: 421
Timeout. Talk faster next
@40000000581c48d908f1c5a4 spamdyke[4387]: TIMEOUT from:
[email protected] <mailto:[email protected]> to: (unknown)
origin_ip: 89.38.150.213 origin_rdns:
host213-150-38-89.static.arubacloud.fr auth: (unknown)
encryption: (none) reason: TIMEOUT
@40000000581c48d908f21b94 spamdyke[4387]:
DEBUG(find_username()@spamdyke.c:127): searching for
username between positions 9 and 35: RCPT
TO:<marekm@*****.com.pl <mailto:marekm@*****.com.pl>>
@40000000581c48d908f22364 DATA
@40000000581c48d908f2274c
@40000000581c48d908f22b34 spamdyke[4387]:
EXCESSIVE(find_username()@spamdyke.c:309): found username
in address: marekm
@40000000581c48d908f24a74 spamdyke[4387]:
DEBUG(find_domain()@spamdyke.c:361): searching for domain
between positions 15 and 35: RCPT TO:<marekm@*****.com.pl
<mailto:marekm@*****.com.pl>>
@40000000581c48d908f25244 DATA
@40000000581c48d908f25244
@40000000581c48d908f2562c spamdyke[4387]:
EXCESSIVE(find_domain()@spamdyke.c:529): found domain in
address: *****.com.pl
@40000000581c48d908f25dfc spamdyke[4387]:
DEBUG(find_address()@spamdyke.c:726): found username: marekm
@40000000581c48d908f27954 spamdyke[4387]:
DEBUG(find_address()@spamdyke.c:743): found domain:
*****.com.pl
@40000000581c48d908f2b3ec spamdyke[4387]:
DEBUG(filter_recipient_whitelist()@filter.c:2332):
searching recipient whitelist(s); recipient:
marekm@*****.com.pl <mailto:marekm@*****.com.pl>
@40000000581c48d908f2b7d4 spamdyke[4387]:
EXCESSIVE(output_writeln()@log.c:102): wrote 37 bytes to
network file descriptor 1, buffer contained 37 bytes: 421
Timeout. Talk faster next
@40000000581c48d908f2bfa4 spamdyke[4387]: TIMEOUT from:
[email protected] <mailto:[email protected]> to:
marekm@*****.com.pl <mailto:marekm@*****.com.pl>
origin_ip: 89.38.150.213 origin_rdns:
host213-150-38-89.static.arubacloud.fr auth: (unknown)
encryption: (none) reason: (empty)
@40000000581c48d908f2dee4 spamdyke[4387]:
EXCESSIVE(output_writeln()@log.c:102): wrote 37 bytes to
network file descriptor 1, buffer contained 37 bytes: 421
Timeout. Talk faster next
@40000000581c48e231636ccc spamdyke[4293]:
EXCESSIVE(middleman()@spamdyke.c:2097): read 33 bytes from
child input file descriptor 6, buffer contains 33 bytes,
current position is 0: 451 SPF lookup failure (#4.3.0
@40000000581c48e231637884 spamdyke[4293]:
EXCESSIVE(middleman()@spamdyke.c:2107): child input file
descriptor 6 indicates EOF, buffer contains 0 bytes,
current position is 0
@40000000581c48e231638054 spamdyke[4293]:
EXCESSIVE(middleman()@spamdyke.c:2108): child input file
descriptor 6 closed
@40000000581c48e231638824 spamdyke[4293]:
EXCESSIVE(middleman()@spamdyke.c:2989): child process
exited normally with return value 1
Any help will be appreciated
Marek
