Hi Sam,
Thanks for the thorough reply.
On 25 Jun 2020 14:50:55, Sam Clippinger via spamdyke-users wrote:
> If tls_read() encountered an error in the
> OpenSSL library and didn't actually read any data, spamdyke's main
> loop would see data waiting and call tls_read() again. That could
>
2.8M lines in 34 seconds? Yikes! Sounds like an infinite loop.
It's been a while since I've looked at that code (and I apologize I don't have
time to go through it in detail), but that error message is only printed from
one place in spamdyke's code. It runs when a TLS/SSL session is active
On 24 Jun 2020 23:36:44, Quinn Comendant via spamdyke-users wrote:
> I thought it was a fluke, since I had never seen this in the decade+
> I've been managing this server.
Actually, there were a few single instances of this error outside of the 34
seconds when it blew up. I found four:
Hi Bucky,
On 25 Jun 2020 07:12:27, Bucky Carr via spamdyke-users wrote:
> Do you need to use 'softlimit'?
Yes, using softlimit to restrict process memory limit is useful, and in fact
necessary to prevent this remotely-exploitable vulnerability in qmail:
I know next to nothing, so this may not help. Do you need to use
'softlimit'? When I quit using it a bunch of troubles went away.
On 6/24/2020 10:36 PM, Quinn Comendant via spamdyke-users wrote:
exec /usr/bin/softlimit -m 9900 \
/usr/bin/tcpserver -R -l $HOSTNAME -x $TCP_CDB
Hello all,
Recently, I checked the smtp log files of my qmailtoaster server, and found
millions of the following error message written to the smtp log:
spamdyke[4875]: ERROR: unable to read from SSL/TLS stream: A protocol or
library failure occurred,
