[This is a reply to
https://www.mail-archive.com/spamdyke-users@spamdyke.org/msg03900.html—I don't
have the original messages to this post probably won't thread correctly.]
When running `spamdyke --config-test` I experienced a `free(): invalid pointer`
error similar to Jeff's, but found the
I'm new to greylisting, and have just set up spamdyke on a mail server with a
few hundred users. Immediately my colleagues and I got annoyed with delayed
deliveries to our personal addresses ;P.
I'm wondering if it would be a reasonable solution to create a
`graylist-exception-rdns-file`
On Tue, 04 Nov 2014 08:05:22 -0700, BC wrote:
At the suggestion of others here, I turned OFF greylisting last year,
after having used it for years before that. My spam level didn't
increase one bit. I think the RBL sites are pretty good at
identifying spam originations, so I use
Sam,
The URLs for hunter_seeker and spamtrap you offered us in 2013 are broken:
http://www.spamdyke.org/releases/hunter_seeker/
http://www.spamdyke.org/releases/spamtrap/
Has this project moved?
And is this script still as effective as it was? I'd like to know its current
status before
And in case it helps, here's a snippet of output from the config test just
before it crashed; notice the two lines with weird characters:
…
INFO(graylist-level): Local domain has no domain directory; spamdyke will
create the directory when needed: unitylab.org
INFO(graylist-level): Local domain
On Tue, 04 Nov 2014 08:05:22 -0700, BC wrote:
At the suggestion of others here, I turned OFF greylisting last year,
after having used it for years before that. My spam level didn't
increase one bit. I think the RBL sites are pretty good at
identifying spam originations, so I use that
On Thu, 20 Nov 2014 14:35:50 -0600, Sam Clippinger wrote:
An interesting statistic to look at, I think, would be the number of
connections blocked by graylisting that don't eventually return with
a successful delivery.
Les did a better job of calculating this (40% deliveries were never
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:
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
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)
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
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:
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
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}'
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
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
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?
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
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:
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 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
>
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,
22 matches
Mail list logo
