Re: [spamdyke-users] Still using 4.3.1

Thanks Sam. That's put my mind at ease. To my knowledge, there are no security issues in version 4.3.1. I've since fixed several bugs that can cause crashes, but nothing I can imagine could be a security risk. There have been recent bugs in OpenSSL and glibc; those libraries should

[spamdyke-users] Still using 4.3.1

Dear all, Forgive me for asking this question - I'm not a coder. I've noticed that a few systems I look after use Spamdyke 4.3.1, compiled back in 2012 or 2013. Are there any security issues with this version? Would any of the various vulnerabilities found in certain ancillary

Re: [spamdyke-users] RBL DNS query numbers

Thanks Sam! From: spamdyke-users [mailto:spamdyke-users-boun...@spamdyke.org] On Behalf Of Sam Clippinger via spamdyke-users Sent: 17 January 2016 19:49 To: spamdyke users Subject: Re: [spamdyke-users] RBL DNS query numbers I think you're exactly right --

Re: [spamdyke-users] Help getting TLS to work please

> Behalf Of Alessio Cecchi via spamdyke-users > Sent: 10 March 2016 08:00 > > Hi, > > if you use spamdyke fixcrio is no more necessary. > -- Ah, that's what I thought. The notes I have say that spamdyke takes care of the bare LFs. But because I could not remember if I added it to the tcpserver

Re: [spamdyke-users] Help getting TLS to work please

> From: spamdyke-users [mailto:spamdyke-users-boun...@spamdyke.org] On > Behalf Of Alessio Cecchi via spamdyke-users > For me works fine with: > > tls-level=smtp-no-passthrough > tls-certificate-file=/var/ssl/wildcard.pem > > and in /var/ssl/wildcard.pem there is a chain like this: > >

[spamdyke-users] Help getting TLS to work please

Dear all, I'm stuck with a qmail installation that doesn't support TLS, so I'm trying to get Spamdyke to deal with it on incoming connections. Unfortunately I've not managed to get it to work - I get the following error in the maillog when testing: ** unable to start SSL/TLS

[spamdyke-users] Sensible greeting delay?

Dear all, Recently I've noticed that massive numbers of (presumably botnet) senders are blocked by the earlytalker filter when greeting-delay-secs=11 but only a fraction as many if I set it to 10 or less. I'm guessing that the current main botnets are set to start talking after 10 seconds

Re: [spamdyke-users] ip-in-rdns-keyword - are hyphens supported?

Aha! Thanks Gary. I'd missed the vital "the dots in the examples below can be any single character" when reading this. Thank you! From: Gary Gendel [mailto:g...@genashor.com] Sent: 06 May 2016 16:24 To: Faris Raouf ; spamdyke users

Re: [spamdyke-users] can't block envelope sender

Hi Sam, I just had a chance to have a go with the tests, and just as you expected it was down to the rDNS of the sender being whitelisted. I don't know how many times I'd checked, and missed seeing it :) Unfortunately I can't remember why I whitelisted it :( It belongs to an ESP. If they

Re: [spamdyke-users] can't block envelope sender

Yup! That would be great. I just think it would be useful to know it is happening, and where to look, sort of thing. From: spamdyke-users [mailto:spamdyke-users-boun...@spamdyke.org] On Behalf Of Sam Clippinger via spamdyke-users Sent: 25 July 2016 14:50 To: spamdyke users

Re: [spamdyke-users] spam with rDNS resolving to "localhost"

.0.1 but block it for all other IPs. -- Sam Clippinger On Aug 9, 2016, at 5:02 AM, Faris Raouf via spamdyke-users <spamdyke-users@spamdyke.org <mailto:spamdyke-users@spamdyke.org> > wrote: Dear all, We're having problems with spam being allowed in from IPs with rDNS re

[spamdyke-users] can't block envelope sender

Dear all, I'm having a bit of an issue trying to block messages based on the envelope sender. Basically it doesn't seem to work at all, so I'm obviously doing something wrong. All the other types of blacklists and whitelists seem to work just fine. I understand the difference between the "From"

Re: [spamdyke-users] can't block envelope sender

Thanks Sam. That's brilliant and hugely helpful. I'll try to do this this evening, and failing that over the weekend. I will also check the whitelists again in case I missed something. Yes, ms2 is the edge server and that's where the sender is backlisted, although I've just added it to

[spamdyke-users] spam with rDNS resolving to "localhost"

Dear all, We're having problems with spam being allowed in from IPs with rDNS resolving to "localhost". This gets past the reject-empty-rdns filter. Initially I thought these IPs has no rDNS - using dnsstuff, I get no result (normally meaning no rDNS). But using host or dig I see the IPs

Re: [spamdyke-users] Localhost relaying denied

ritten the next time Plesk saves a change. -- Sam Clippinger On Oct 3, 2016, at 7:58 AM, Faris Raouf via spamdyke-users <spamdyke-users@spamdyke.org <mailto:spamdyke-users@spamdyke.org> > wrote: Dear all, I'm absolutely confounded by a problem I'm having after upgr

[spamdyke-users] Localhost relaying denied

Dear all, I'm absolutely confounded by a problem I'm having after upgrading five systems from Spamdyke 4.3.1 to 5.0.1 On two of them, webmail (running locally, connecting from 127.0.0.1 to 127.0.0.1 port 25 via smtp, no authentication) works fine and can send messages. On the other