Thank you, Sam. For so much work on this update, a measly 0.0.1
version bump belittles it.
On 5/1/2015 11:36 AM, Sam Clippinger via spamdyke-users wrote:
spamdyke lives!
spamdyke version 5.0.1 is now available:
http://www.spamdyke.org/
This version fixes a ton of bugs, including a number
Wow. So for example, the starting linefor my smtpd-run file looks like
this:
exec /usr/local/bin/softlimit -m 2 /usr/local/bin/tcpserver
-4v -R -l "$LOCAL" \
and I can simply change it to this:
exec /usr/local/bin/tcpserver -4v -R -l "$LOCAL" \
with impunity?
On 6/20/2015 5:12
Using FreeBSD here.
In addition to my normal IPv4 connection, I have an IPv6 tunnel set up
via Hurricane Electric. Also use unbound as my local DNS cache
resolver for resolving both IPv4 & IPv6 addresses and it has been
doing both for over a year now.
spamdyke doesn't seem to like the IPv6
Now that I've set log-level=excessive, I can see these two errors that
spamdyke is spitting out a lot:
May 4 13:54:52 Xeon_Right spamdyke[18726]:
ERROR(undo_softlimit()@spamdyke.c:3226): data segment hard limit is
less than infinity, could lead to unexplainable crashes: 34359738368
May 4 1
That is what I figured. Thanks, Sam.
On 5/5/2016 6:30 AM, Sam Clippinger via spamdyke-users wrote:
Right now, spamdyke has no support for IPv6 at all, so it can't
understand that nameserver line. However, the only consequence
should be that error message -- it shouldn't have any trouble
ski
A, the ulimit limits. I'd forgotten about those and was focusing
on the "softlimit" word in the error.
Thanks, Sam.
On 5/5/2016 6:35 AM, Sam Clippinger via spamdyke-users wrote:
You're correct that those messages are related to limits, but not
the ones softlimit can set. Those messages
I've got 127.0.0.1 in my "blacklist_ip" file and the system seems to
be working fine.
On 8/9/2016 4:02 AM, Faris Raouf via spamdyke-users wrote:
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 fi
I'm building out a new server box and figured it is time to revisit my
configuration files, including spamdyke.conf. In 2014 I included some
dns-blacklist-entry="entries...".
But in 2015/2016 my configuration didn't include any.
What say the congregants about the efficacy of RBL usage with
While installing spamdyke on my latest FreeBSD build machine, I saw
this notice:
Message from spamdyke-5.0.1_1:
===> NOTICE:
The spamdyke port currently does not have a maintainer. As a result, it is
more likely to have unresolved issues, not be up-to-date, or even be
removed in
the futu
On 10/3/2016 6:58 AM, Faris Raouf via spamdyke-users wrote:
dns-blacklist-entry=b.barracudacentral.org
Comment out the above and try it again.
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spam
It hasn't risen to the level of DDOS, yet, but I'm getting many
hundreds of these messages per night (and it is now continuing during
the day).
They look like this:
Hi. This is the qmail-send program at purgatoire.org.
I tried to deliver a bounce message to this address, bu
Thank you very much. I'll look into that.
On 11/7/2016 9:13 AM, Gary Gendel via spamdyke-users wrote:
This doesn't look like it's email originating from your system.
Instead, it looks like spamdyke has accepted the message and then
qmail is doing the rejection. My guess is that it passes thr
Well, I have spamdyke-qrv installed and turned on in spamdyke.conf,
but am still getting stuff like this (maillog):
Nov 8 21:48:51 33a45916-5b78-11e6-a0e5-0cc47a6975be spamdyke[17138]:
ALLOWED from: filenkokir...@shopon.net to: sergushk...@bk.ru
origin_ip: 10.0.1.15 origin_rdns: (unknown) a
On 11/9/2016 6:27 AM, Sam Clippinger via spamdyke-users wrote:
I don't understand how you have your jails configured -- is qmail in
a different jail from spamdyke? I'm just wondering, if the message
is originating locally, why does spamdyke see the origin IP as
10.0.1.15 instead of 127.0.0.1
On 11/9/2016 6:27 AM, Sam Clippinger via spamdyke-users wrote:
Do you have 10.0.1.15 whitelisted because it's the local IP? Or is
it configured in your /etc/tcp.smtp as a relay client? Either
setting would cause spamdyke to allow these messages.
Thanks, Sam. That was the issue (both place
Will spamdyke compile with TLS using the LibreSSL libraries?
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
https://spamdyke.org/mailman/listinfo/spamdyke-users
bably work fine.
-- Sam Clippinger
On May 26, 2018, at 2:42 PM, BC via spamdyke-users
mailto:spamdyke-users@spamdyke.org>>
wrote:
Will spamdyke compile with TLS using the LibreSSL libraries?
___
spamdyke-users mailing list
spamdyke-use
On 9/28/2020 7:51 AM, Philip Rhoades via spamdyke-users wrote:
You need to block by header contents as it offers more wildcards:
https://www.spamdyke.org/documentation/README.html#HEADERS
From:*
Hmm . . I thought I had tried that - oh well, I will give it a shot!
I use this technique s
18 matches
Mail list logo