Re: [spamdyke-users] Infinite loop of logged errors: unable to read from SSL/TLS stream

2020-06-25 Thread Quinn Comendant via spamdyke-users
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 >

Re: [spamdyke-users] Infinite loop of logged errors: unable to read from SSL/TLS stream

2020-06-25 Thread Quinn Comendant via spamdyke-users
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:

Re: [spamdyke-users] Infinite loop of logged errors: unable to read from SSL/TLS stream

2020-06-25 Thread Quinn Comendant via spamdyke-users
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:

[spamdyke-users] Infinite loop of logged errors: unable to read from SSL/TLS stream

2020-06-24 Thread Quinn Comendant via spamdyke-users
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,

Re: [spamdyke-users] SERVFAIL on dns-server-ip-primary does not fail-over

2019-03-13 Thread Quinn Comendant via spamdyke-users
enough, the message(s) may bounce. > Unfortunately there's no DNS code to indicate the server is > malfunctioning and shouldn't be used -- spamdyke expects it to stop > sending responses when that happens. > > > -- Sam Clippinger > > > > >> On Mar 11, 20

[spamdyke-users] SERVFAIL on dns-server-ip-primary does not fail-over

2019-03-11 Thread Quinn Comendant via spamdyke-users
We had an incident where both our local caching name servers stopped working. They returned SERVFAIL (see example below). They were set as the "dns-server-ip-primary" and our host-provided DNS server was set as the "dns-server-ip". Because the primaries were failing, I would expect spamdyke to

Re: [spamdyke-users] rotate between multiple dns-server-ip-primary

2019-03-11 Thread Quinn Comendant via spamdyke-users
On 28 Feb 2019 15:53:34, Quinn Comendant via spamdyke-users wrote: > Can spamdyke rotate between multiple dns-server-ip-primary servers, > to distribute the load evenly? Still wondering about this. I haven't seen any replies. Sam, can you clarify if this option exists?

[spamdyke-users] rotate between multiple dns-server-ip-primary

2019-02-28 Thread Quinn Comendant via spamdyke-users
Can spamdyke rotate between multiple dns-server-ip-primary servers, to distribute the load evenly? Because the documentation says "Depending on the number of nameservers and the values of dns-max-retries-primary and dns-max-retries-total, some nameservers may never be queried" it leads me to

[spamdyke-users] Too many links

2018-04-10 Thread Quinn Comendant via spamdyke-users
I noticed this Spamdyke error message: ERROR: unable to create directory /var/qmail/spamdyke/greylist/example.com/redacted/bounce.nytimes.com: Too many links Indeed this user's greylist directory is full: # sudo ls -dl /var/qmail/spamdyke/greylist/example.com/redacted/ | awk '{print $2}'

[spamdyke-users] Graylisting delivery failure notifications

2017-08-18 Thread Quinn Comendant via spamdyke-users
A client using our Spamdyke-enabled mail server has reported someone sending them an email received a "bounce" message notifying the sender that the messages has been graylisted (see the delivery failure notification below). They did receive the message (graylisting works well for us). This is

Re: [spamdyke-users] reject-sender=none in spamdyke/_ip_/ directory not working

2017-05-06 Thread Quinn Comendant via spamdyke-users
On Fri, 5 May 2017 10:15:36 -0500, Sam Clippinger via spamdyke-users wrote: > Ah, I should have asked. Yes, that option should work. Thanks Sam. BTW, I created a script to automate creating the custom sender configuration files using the _ip_ and _sender_ directory structures:

Re: [spamdyke-users] reject-sender=none in spamdyke/_ip_/ directory not working

2017-05-05 Thread Quinn Comendant via spamdyke-users
Update: I added `reject-sender=none` to /etc/spamdyke.conf and these errors started appearing in the log: 2017-05-05 06:33:46.873563500 ERROR: Unknown configuration file option in file /etc/spamdyke.conf on line 33: reject-sender I realize now this config option is only for spamdyke 5. I'm

[spamdyke-users] reject-sender=none in spamdyke/_ip_/ directory not working

2017-05-05 Thread Quinn Comendant via spamdyke-users
I've gotten this error: 2017-05-05 03:16:52.533029500 spamdyke[30324]: DENIED_SENDER_NO_MX from: bounces+1818979-7ef3-quinn=strangecode[.]c...@tz.changeyourflight.com to: quinn[@]strangecode[.]com origin_ip: 167.89.72.110 origin_rdns: o1678972x110.outbound-mail.sendgrid.net auth: (unknown)

Re: [spamdyke-users] Whitelist an IP for the DENIED_RDNS_MISSING error?

2015-08-05 Thread Quinn Comendant via spamdyke-users
On Wed, 5 Aug 2015 20:02:51 -0500, Sam Clippinger via spamdyke-users wrote: But to answer your question, yes! It is possible to turn off the rDNS filters for just that one IP. The feature you need is a configuration directory. Create a folder structure on the server like this:

[spamdyke-users] Whitelist an IP for the DENIED_RDNS_MISSING error?

2015-08-05 Thread Quinn Comendant via spamdyke-users
We're experiencing blocked email due to a DENIED_RDNS_MISSING error, although the domain PTR records do resolve: $ dig -x 64.34.221.10 +short mail.lassosoft.com. Error: 2015-08-05 18:56:56.452648500 spamdyke[5681]: DENIED_RDNS_MISSING from: donotre...@lassosoft.com to: u...@example.com