This is a part of excessive log:


@4000000057ffaef614a4dfbc CHKUSER accepted sender: from
<> remote <>
rcpt <> : sender accepted

@4000000057ffaef80ebb7624 spamdyke[29165]:
EXCESSIVE(middleman()@spamdyke.c:1965): child output file descriptor 5

@4000000057ffaef80ebb7df4 spamdyke[29165]:
EXCESSIVE(output_writeln()@log.c:102): wrote 37 bytes to network file
descriptor 1, buffer contained 37 bytes: 421 Timeout. Talk faster next

@4000000057ffaef80ebb85c4 spamdyke[29165]: TIMEOUT from:
to: (unknown) origin_ip: origin_rdns: auth:
(unknown) encryption: TLS reason: TIMEOUT

@4000000057ffaf03331f68f4 tcpserver: status: 4/100




From: spamdyke-users [] On Behalf
Of Sam Clippinger via spamdyke-users
Sent: Thursday, October 13, 2016 2:37 PM
To: spamdyke users
Subject: Re: [spamdyke-users] TLS reason: TIMEOUT


Looking at those log messages, I don't think TLS has anything to do with
this.  spamdyke's log message shows "encryption: (none)", which means TLS is
not in use.


When spamdyke logs TIMEOUT, it means the remote server held the connection
open too long without sending any data at all.  Usually that means the
software on the remote server is badly written and it's expecting a very
specific message before proceeding.  Since it isn't getting that message, it
just waits until it the connection times out.  There's an FAQ about this


Documentation on how to adjust spamdyke's timeouts is here:


By default, spamdyke doesn't enforce any timeouts, so another line in your
config file must be enabling them.  Perhaps simply increasing those values
will solve this?


If that doesn't help, I'd suggest using spamdyke's full logging feature to
capture one of these failed connections.  That will show exactly what's data
is being sent and how long it's taking.

-- Sam Clippinger





On Oct 12, 2016, at 2:31 PM, marek--- via spamdyke-users
<> wrote:

I read an old thread on this problem, but did not see a solution. 

# spamdyke -v

spamdyke 5.0.1+TLS+CONFIGTEST+DEBUG+EXCESSIVE (C)2015 Sam Clippinger, samc
(at) silence (dot) org

# uname -a

Linux mail.xxxxx.xx 2.6.18-308.13.1.el5 #1 SMP Tue Aug 21 17:10:06 EDT 2012
i686 i686 i386 GNU/Linux


In spamdyke.config


The problem is TLS TIMEOUT

2016-10-08 21:04:50.283975500 CHKUSER accepted sender: from
<> remote <>
rcpt <> : sender accepted

2016-10-08 21:05:51.280337500 spamdyke[13676]: TIMEOUT from: to: (unknown) origin_ip: origin_rdns: auth: (unknown) encryption: (none) reason: TIMEOUT


Add adress to whitelist_senders nothing change :(


I try also on spamdyke 4.3 before upgrade to 5.1 it's the same.

I don't any idea how to make to allow this mail. 


Any help will be appreciated

spamdyke-users mailing list


spamdyke-users mailing list

Reply via email to