a firewall or a load
balancer? Is your qmail patched to invoke an external spam scanner or anything?
-- Sam Clippinger
> On Mar 3, 2021, at 11:22 AM, Alessio Cecchi via spamdyke-users
> wrote:
>
> Hi,
>
> when a specific company send an email to us we receive the mess
you're trying to do, take a look at the header blacklist feature. You
should be able to block those spam messages with: From:*.sicotti.nl*
-- Sam Clippinger
> On Feb 13, 2021, at 4:28 PM, Shane Bywater via spamdyke-users
> wrote:
>
> Hi,
>
> Recently I started receiving s
That should do it.
-- Sam Clippinger
> On Oct 12, 2020, at 3:57 AM, Alessio Cecchi via spamdyke-users
> wrote:
>
> Hi,
>
> since many commercial DNSBL are providing access to their RBL with a "key"
> (es. 1234abcd.zen.dq.spamhaus.net.) we need to hide
commands
it tested. If you could figure out the correct command to compile, we should
be able to update the configure script to use it. It might just be a case of
libcrypto.so being in an unexpected folder; it's possible just adding the -L
flag or setting LIBRARY_PATH might fix it.
-- Sam
versions 4 and 5, I made a
lot of changes and the changelog mentions tls_read() specifically. This could
be a bug I've already fixed.
I hope that helps, good luck!
-- Sam Clippinger
> On Jun 24, 2020, at 11:36 PM, Quinn Comendant via spamdyke-users
> wrote:
>
> Hello all,
>
oduce must larger (and much more
informative) crash messages.
-- Sam Clippinger
> On Mar 30, 2020, at 7:51 PM, Webtao via spamdyke-users
> wrote:
>
> Hi Sam,
>
> First of all, thank you for managing spamdyke :-)
>
> Lately, I updated my Centos 6.5 and suddenly got th
else is interested in picking up the torch, I'd be happy to help
migrate the project to Github (or similar) and consult if desired.
-- Sam Clippinger
> On Mar 29, 2020, at 2:32 AM, Philip Rhoades via spamdyke-users
> wrote:
>
> Sam,
>
> I am gradually getting organised to
sists long 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, 2019, at 6:58 PM, Quinn Comendant via spamdyke-us
I have no idea -- I've never used LibreSSL. As long as they've only updated
the internal library code and not changed the API, it'll probably work fine.
-- Sam Clippinger
On May 26, 2018, at 2:42 PM, BC via spamdyke-users
wrote:
>
> Will spamdyke compile with TLS using the Li
sponse. I suggest using the
full-log-dir option to capture the entire transaction to a file so you can see
exactly what each side is sending and where the connection is being broken.
-- Sam Clippinger
On Jun 3, 2018, at 1:41 PM, Eric Broch via spamdyke-users
wrote:
> can you h
e
message, the header blacklist filter could block it. Hopefully that would work
for you.
-- Sam Clippinger
On Oct 15, 2017, at 3:26 PM, mohaa via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> Marcin, of course i did and both do not match my situation
> If you mean "it is n
.net twice, the logs
on that server should show it. I'd trust your logs, not the message headers.
-- Sam Clippinger
On Aug 22, 2017, at 2:00 PM, Pablo Murillo <p...@rednetgroup.com> wrote:
> Hi
>
> I´m a little confuse
> We have 4 MXs, the names are mx1.serversur.net to mx4, e
t the incoming spam looks like.
-- Sam Clippinger
On Aug 18, 2017, at 12:02 PM, Pablo Murillo (rednet) via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> Hi
>
> Which are the valid headers to filter ?
>
> I think, the obviuos ones are: FROM SUBJECT
> REPLY-TO
>
&
ts in the queue long enough to send a warning to the
user? I suppose you could fix it by either reducing the overall graylisting
time on your server or by turning off graylisting for messages from their
domain (using a configuration directory).
-- Sam Clippinger
On Aug 18, 2017, at 11:24 AM,
will match a
glob pattern, they'll only match a list of specific addresses.
Sorry!
-- Sam Clippinger
On May 19, 2017, at 3:30 PM, Amitai Schleier via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> I use spamdyke's graylisting feature for all incoming mail. I still generall
thing like this would probably be to
allow spamdyke to run custom commands/scripts that perform additional checks.
That would make it much easier to add one-off filters.
-- Sam Clippinger
On May 9, 2017, at 3:33 PM, Pablo Murillo (rednet) via spamdyke-users
<spamdyke-users@spamdyke.org&
Ah, I should have asked. Yes, that option should work.
-- Sam Clippinger
On May 5, 2017, at 8:57 AM, Quinn Comendant via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> Update: I added `reject-sender=none` to /etc/spamdyke.conf and these errors
> started appearin
no DNS records at all. I don't see any way that return address could
work.
https://mxtoolbox.com/SuperTool.aspx?action=a%3atz.changeyourflight.com=toolpage
-- Sam Clippinger
On May 5, 2017, at 3:24 AM, Quinn Comendant via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
closed-recipients" with the
header blacklist filter, if that's really how it appears in the message
headers. Blocking emails with no "To" line in the header isn't something
spamdyke can do right now, sorry!
-- Sam Clippinger
On Apr 18, 2017, at 9:36 PM, Philip Rhoades via s
or: I haven't tested these suggestions or even attempted to compile
them. Good luck!
-- Sam Clippinger
On Mar 24, 2017, at 10:19 AM, Alessio Cecchi via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> Thanks Sam for your answer,
>
> anyway it is crucial for us to avo
session.
Your only option is to set a lower idle timeout, anything else would require a
major refactoring of spamdyke's code. Sorry!
-- Sam Clippinger
On Mar 10, 2017, at 4:11 AM, Alessio Cecchi via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> Hi,
>
> some months ago
a guess -- are there any
errors in any of the logs that might provide more information?
-- Sam Clippinger
On Mar 6, 2017, at 1:58 PM, turgut kalfaoğlu via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> Hi there. I recently enabled spamdyke, but when someone uses the horde
It looks like your /usr/local/psa/var/log/maillog file is just a symlink to
/var/log/maillog (not /var/log/messages). Are spamdyke's log messages
appearing there?
-- Sam Clippinger
On Mar 5, 2017, at 11:43 PM, turgut kalfaoğlu via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
path/to/src/spamdyke-5.0.1
patch -p0 <
/path/to/patch/spamdyke-5.0.2-beta1-reject_sender_not_local.patch
make
Then copy the new binary into place.
Thank you very much for reporting this!
-- Sam Clippinger
On Nov 4, 2016, at 7:24 AM, Sam Clippinger via spamdyke-users
<s
I'm not sure I completely understand your setup, so yes, I think the full log
might be helpful. You can send it to me directly if you don't want to post it
to the list.
-- Sam Clippinger
On Nov 1, 2016, at 9:33 AM, Pablo Murillo <p...@rednet.com.ar> wrote:
> Yes, I hace
erent configurations?
-- Sam Clippinger
On Oct 31, 2016, at 6:07 PM, Pablo Murillo via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> Hi
>
> I will try to explain the subject
> We use Qmail, VpopMail and Spamdyke
> We have multiple servers with jails with
ill
solve this?
If that doesn't help, I'd suggest using spamdyke's full logging feature to
capture one of these failed connections. That will show exactly what's data is
being sent and how long it's taking.
-- Sam Clippinger
On Oct 12, 2016, at 2:31 PM, marek--- via spamdyke-users
<s
ly being read by tcp-env).
It's been quite a while since I've worked with Plesk but I seem to remember
that option is set within the Plesk admin interface. It'd be a good idea to
change it there -- otherwise if you change it on disk, it'll probably just get
overwritten the next time Plesk sav
ain active for local connections, use a
config-dir to remove "localhost" from the blacklist for 127.0.0.1.
Incidentally, are you using the reject-unresolvable-rdns filter? That filter
has a special exception for "localhost" to allow that name for 127.0.0.1 but
block it for all ot
d
this change, proceed with caution...)
-- Sam Clippinger
On Jul 22, 2016, at 6:17 PM, Gary Gendel via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> Sam,
>
> Is there a way to get spamdyke to log invalid authorizations in a manner that
> fail2ban can use? My host h
Could probably do that. Or maybe print the matching file/line in the "reason"
field, the same way it already does for blacklist matches?
-- Sam Clippinger
On Jul 22, 2016, at 11:37 AM, Faris Raouf <aster...@raouf.net> wrote:
> Hi Sam,
>
> I just had a chance to
t to me privately and I'll
take a look.
-- Sam Clippinger
On Jul 21, 2016, at 6:39 AM, Faris Raouf via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> Dear all,
>
> I'm having a bit of an issue trying to block messages based on the envelope
> sender. Basically it d
I'll get that added to the next release, thanks!
-- Sam Clippinger
On May 10, 2016, at 5:37 AM, Jonas Pasche via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> Hey there,
>
> while the configure script of the current version tells that it would be
> able to hand
before spamdyke runs. Those limits
are extremely high, so there's very little chance they're going to cause any
problems, but spamdyke will keep complaining about them as long as log-level is
"verbose" or higher.
-- Sam Clippinger
On May 4, 2016, at 3:04 PM, BC via spamdyke-users <sp
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 skipping that line and using the IPv4 nameserver.
-- Sam Clippinger
On May 4, 2016, at 2:54 PM, BC
ot;-v"
flag (possibly twice) to see why it's deciding to allow the recipient.
Something like this:
spamdyke-qrv -v pricom.com.au jackspratt
-- Sam Clippinger
On May 4, 2016, at 4:39 AM, Philip Rhoades via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> Peopl
ect either the user's password has been
compromised or the user's PC has been infected with malware.
I'd suggest changing the account password so authentication will fail --
spamdyke's filters should work fine after that.
-- Sam Clippinger
On Mar 23, 2016, at 5:00 AM, Stephen Provis via s
ml#REJECTING_SENDERS
-- Sam Clippinger
On Dec 29, 2015, at 11:54 PM, Philip Rhoades via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> People,
>
> I thought of starting a new thread but the question relates to this
> discussion so I thought I would revive it - see inl
that I'm still amazed people still use
Solaris at all, much less OpenIndiana? :)
-- Sam Clippinger
On Dec 15, 2015, at 7:10 PM, Gary Gendel via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> Sam,
>
> I've started a discussion on the OpenIndiana developer's mailing list ab
enabling the
"full-log-option" to capture the data from one of these failed connections?
-- Sam Clippinger
On Dec 14, 2015, at 8:29 AM, Arne Metzger <mo...@foni.net> wrote:
> Hi Sam,
>
> sorry for the delayed reply.
>
> My config files are attached below. But i
It's hard to say what the problem might be without more information. Could you
post your spamdyke config file? Also, if you use the full-log-dir option,
spamdyke will capture everything that happens into a log file for each
connection, which should show exactly what's going on.
-- Sam
alue).
Why not just use multiple entries in the file? If either one matches, the
message will be blocked and it'd be easier to understand:
From: *@skysoft.com
Reply-To: *@skysoft.com
-- Sam Clippinger
On Oct 2, 2015, at 4:34 AM, Philip Rhoades via spamdyke-users
<spamdyke-us
host you telnet from isn't blocked or whitelisted for some other
reason (most folks whitelist localhost, for example).
-- Sam Clippinger
On Sep 25, 2015, at 1:31 AM, Philip Rhoades via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> Sam,
>
>
> On 2015-09-15 07:27, S
in action -- the
sender's mail client gave your address as a recipient but didn't put your
address on the "To" line in the message header.
-- Sam Clippinger
On Sep 13, 2015, at 9:20 PM, Philip Rhoades via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> Sam,
>
>
&g
.
-- Sam Clippinger
On Sep 13, 2015, at 4:11 PM, Philip Rhoades via spamdyke-users
<spamdyke-users@spamdyke.org> wrote:
> People,
>
> One variety of spam that is successfully delivered to me has a different
> "From:" addresses but the same "Reply-To:" addr
to checkpasswd-pam. I tried hard-coding the string that was sent (and works
fine on external checkpasswd-pam tests) but it still times out. However,
spamdyke's auth works fine which is how I discovered the above problem.
Gary
On 08/24/2015 12:26 PM, Sam Clippinger via spamdyke-users wrote:
What
that shows how to
reproduce this? That'll probably save me quite a bit of time.
-- Sam Clippinger
On Aug 21, 2015, at 1:54 PM, Gary Gendel via spamdyke-users
spamdyke-users@spamdyke.org wrote:
Sam,
If I use qmail with smtp auth, then spamdyke announces STARTTLS capabilities,
but if I
of versions away unfortunately.
-- Sam Clippinger
On Aug 22, 2015, at 5:40 AM, Philip Rhoades via spamdyke-users
spamdyke-users@spamdyke.org wrote:
People,
Here are some stats after a couple of months of happy Spamdyke usage -
thanks! If I had remembered to set the logrotate number
I think you can test it by using the openssl client from the command line:
openssl s_client -ssl3 -connect SERVERNAME:PORT
If it connects and you see Protocol: SSLv3, it's not disabled. If you see
sslv3 alert handshake failure and it doesn't connect, you're done!
-- Sam Clippinger
/qmail/#oversize-dns
-- Sam Clippinger
On Aug 20, 2015, at 8:18 AM, Gary Gendel via spamdyke-users
spamdyke-users@spamdyke.org wrote:
Sam,
I'm convinced I just spent a day trying to get the qmail package from
netbsd-pkgsrc running on OmniOS. There were messed up dependencies
to generate warnings, so I'll get it fixed in the next
version and add Ubuntu 14.04 to my list of test systems. Thanks for reporting
this!
-- Sam Clippinger
On Aug 19, 2015, at 5:42 AM, Arne Metzger via spamdyke-users
spamdyke-users@spamdyke.org wrote:
Hi,
i am trying to make spamdyke
while doing all the filtering it does now, it should work
nicely with just about any other mail server.
-- Sam Clippinger
On Aug 18, 2015, at 12:03 PM, Gary Gendel via spamdyke-users
spamdyke-users@spamdyke.org wrote:
I use port 22 for non-auth mail and 587 for TLS with auth mail. On 587 I
I agree. qmail is rejecting your recipient address because it's not a local
address and you don't have permission to relay. If you authenticate first,
qmail should accept the message.
-- Sam Clippinger
On Aug 9, 2015, at 11:42 AM, Galatis via spamdyke-users
spamdyke-users@spamdyke.org
directory feature is here:
http://spamdyke.org/documentation/README.html#CONFIGURATION_DIR
-- Sam Clippinger
On Aug 5, 2015, at 7:16 PM, Quinn Comendant via spamdyke-users
spamdyke-users@spamdyke.org wrote:
We're experiencing blocked email due to a DENIED_RDNS_MISSING error, although
one of the connections
that should be blocked, it would show exactly what spamdyke is doing (or not
doing) at every step.
-- Sam Clippinger
On Jun 27, 2015, at 11:55 AM, Shane Bywater via spamdyke-users
spamdyke-users@spamdyke.org wrote
It can do this in a limited fashion right now. If the improper To field is
always To: %from_email (or something from a known set of bad values), you
could use the header blacklist filter to block it. But at present, there's no
way to block a message with a missing header line.
-- Sam
software is sending the MAIL FROM command in a way spamdyke can't
parse, causing it to eat the input and never send it to qmail, but the full log
would show it either way. The option to enable that feature is full-log-dir.
-- Sam Clippinger
On Jun 22, 2015, at 11:32 AM, Angus McIntyre via
the message).
-- Sam Clippinger
On Jun 19, 2015, at 9:09 PM, Philip Rhoades via spamdyke-users
spamdyke-users@spamdyke.org wrote:
Sam,
See inline comments:
On 2015-06-20 11:53, Sam Clippinger via spamdyke-users wrote:
You're correct spamdyke does not support regexes for any of its
time trying to track down bugs that were caused
by softlimit and I finally reached my own limit this year. That's why spamdyke
5.0.1 examines the limits it starts with and, if it can, resets them. It can't
undo hard limits set by the ulimit program, but it can (and does) undo
softlimit.
-- Sam
#HEADERS
Header filtering doesn't support regexes either, but it does use globbing to
allow more wildcard options.
-- Sam Clippinger
On Jun 19, 2015, at 7:47 PM, Philip Rhoades via spamdyke-users
spamdyke-users@spamdyke.org wrote:
People,
As well as using GreyLite I have done my own thing
a patch or a filter like spamdyke.
-- Sam Clippinger
On Jun 19, 2015, at 5:21 AM, Philip Rhoades via spamdyke-users
spamdyke-users@spamdyke.org wrote:
People,
I have been using GreyLite for many years but it hasn't been supported for
quite a while - I think it is time to update
://www.spamdyke.org/documentation/README.html#SMTP_ERROR
-- Sam Clippinger
On Jun 12, 2015, at 9:06 AM, Agence Webtao via spamdyke-users
spamdyke-users@spamdyke.org wrote:
Hi everybody,
Do you know a way to customize reject message?
for exemple this one: Refused. Your reverse DNS entry
be
able to add it soon.
-- Sam Clippinger
On Jun 12, 2015, at 4:42 AM, Alessio Cecchi via spamdyke-users
spamdyke-users@spamdyke.org wrote:
Hi,
I'm running spamdyke 5.0.1 and works very well, but I have a request.
Can spamdyke log the helo sent from the remote server? For example
Anything's possible hard to say. Could you post your config file? Have
you tried running the config-test command?
-- Sam Clippinger
On May 19, 2015, at 12:49 AM, Les Fenison via spamdyke-users
spamdyke-users@spamdyke.org wrote:
I finally got around to installing version 5.0.1
tested).
Version 5.0.1 is backwards-compatible with version 5.0.0; simply replacing the
old binary with the new one should be safe.
-- Sam Clippinger
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo
5.0.0: cd /path/to/src/spamdyke-5.0.0 patch -p1 spamdyke-5.0.0-segfault.patch makeThen install the new binary over the old one.If this doesn't fix your crashes, at least it'll fix a lot of other potential ones!
spamdyke-5.0.0-segfault.patch
Description: Binary data
-- Sam Clippinger
On Apr 9, 2015
sent, you're using the ip-relay-file option and I think
it's very likely spamdyke is crashing while trying to parse that file. If you
still have it, could you send me that file so I can test against it?
-- Sam Clippinger
On Apr 10, 2015, at 1:49 PM, Steve Cole via spamdyke-users
spamdyke-users
this line instead:
reject-sender=!!!
That will reset the reject-sender option to zero (none), which is what you
want. I'll include a real fix for this in the next version.
Still trying to find the segfault, that's a deeper rabbit hole...
-- Sam Clippinger
On Apr 8, 2015, at 12:35 AM
The error DENIED_RDNS_RESOLVE means spamdyke found an rDNS name, but the name
it found doesn't forward-resolve to an IP address (any IP address). So even
though compxroads.com has an IP, m1.compxroads.com does not, so spamdyke
rejected it.
-- Sam Clippinger
On Mar 24, 2015, at 4:03 PM
You're quite correct -- this is a bug in version 5.0.0. I've got it fixed in
the next version, hopefully to be released very soon.
-- Sam Clippinger
On Feb 2, 2015, at 1:38 PM, Heiko Bornholdt via spamdyke-users
spamdyke-users@spamdyke.org wrote:
Hi,
I’m trying to replace my Spamdyke
...
-- Sam Clippinger
On Jan 10, 2015, at 9:40 AM, Martin H. Sluka via spamdyke-users
spamdyke-users@spamdyke.org wrote:
Hi Konstantin,
I have difficulties using spamdyke-qrv in combination with aliases
on aliased domains with vpopmail. For example when I'm creating a
new domain original
keyword file at all
and the filter isn't working.
I assume you're on the latest version? Would you mind sending me your complete
configuration file? I'd like to be able to reproduce this so I can be sure
I've got it fixed.
-- Sam Clippinger
On Nov 27, 2014, at 8:21 PM, Les Fenison l
a single
space. I thought I'd already fixed that before, but apparently not.
Thanks for reporting this! I'm currently testing the next version and hope to
release it next week with some important fixes to spamdyke-qrv.
-- Sam Clippinger
On Nov 28, 2014, at 12:14 PM, Les Fenison l
with a successful delivery. In other words, the number of spambots that
are actually deterred by the graylist filter.
-- Sam Clippinger
On Nov 20, 2014, at 3:27 AM, Quinn Comendant qu...@strangecode.com wrote:
On Tue, 04 Nov 2014 08:05:22 -0700, BC wrote:
At the suggestion of others here, I turned
Yikes, that's no good! I'll get that fixed in the next version, thanks for
reporting this!
-- Sam Clippinger
On Nov 4, 2014, at 1:55 AM, Quinn Comendant qu...@strangecode.com wrote:
[This is a reply to
https://www.mail-archive.com/spamdyke-users@spamdyke.org/msg03900.html—I
don't have
. The hunter_seeker script still works
great for me, though it's important to add new filters periodically as you
notice new spammers becoming effective.
-- Sam Clippinger
On Nov 4, 2014, at 8:53 PM, Quinn Comendant qu...@strangecode.com wrote:
Sam,
The URLs for hunter_seeker and spamtrap you
I just recreated the tarball to include the new scripts I've created recently.
It's available on the site now.
-- Sam Clippinger
On Nov 5, 2014, at 8:11 AM, Gary Gendel g...@genashor.com wrote:
Sam,
Do you have a repository of your current filters that you're willing to
share? Or do
.
-- Sam Clippinger
On May 30, 2014, at 5:11 PM, Les Fenison l...@deltatechnicalservices.com
wrote:
According to the list of files in the docs, I am missing some. Is it
necessary to have them all? I am missing these...
/var/qmail/control/envnoathost
/var/qmail/control/percenthack
). Could
you send me your spamdyke configuration file so I can try to reproduce your
setup and nail it down?
-- Sam Clippinger
On Mar 13, 2014, at 3:03 PM, Shane Bywater sh...@apexia.ca wrote:
Hi,
I disabled all whitelist options in spamdyke.conf and restarted
spamdyke. Confirmed
to authenticate with
the username webmaster. Is that legal on your server? Most Plesk servers
require authenticating with the full email address as the username.
-- Sam Clippinger
On Mar 18, 2014, at 5:30 AM, Arne.Metzger mo...@foni.net wrote:
In the meantime i switched back to 4.3.1, which works like
the * character so it doesn't match every recipient.
-- Sam Clippinger
On Mar 21, 2014, at 10:40 AM, Lutz Petersen l...@shlink.de wrote:
Hi,
today we got some astonishing Mails - such Recipients:
*@domain.tld
Does anyone know how to prevent this ?
Lutz Petersen
.
-- Sam Clippinger
On Mar 28, 2014, at 1:47 PM, Eric Shubert e...@shubes.net wrote:
Marc ( Sam),
Would you please elaborate a little on this? I'm trying to straighten
things up on QMail-Toaster and could use a little help. I'm far from an
openssl expert, but I'm learning
If the earlytalker filter actually blocks a connection, you should see a
DENIED_EARLYTALKER message in the log. Are you sure that connection isn't
whitelisted or authenticating? Either of those things would prevent the
earlytalker filter from actually blocking the connection.
-- Sam
(CBL is almost always
first). When I request delisting, it's usually done within a few hours.
Obviously your experience has been different, but I have no complaints.
-- Sam Clippinger
On Mar 9, 2014, at 8:30 AM, Gary Gendel g...@genashor.com wrote:
I tend to agree. The lists I've chosen
it with the full-log-dir option enabled to capture the full log of everything
that's happening. That log would show everything about how spamdyke is
configured, the environment, inputs and outputs, etc. I could use that to
reproduce the problem and find the bug.
-- Sam Clippinger
On Feb 26, 2014
Honestly, the RBL that seems to do the most good these days for me is the
Barracuda Central list (b.barracudacentral.org). I also use Spamhaus, Spamcop
and Spam Eating Monkey, but together those three don't catch even a tenth of
what Barracuda catches.
-- Sam Clippinger
On Mar 6, 2014
SpamAssassin if it
took too long, then continue accepting the message. Until that day however, I
think the only solution is to increase your idle timeout setting.
-- Sam Clippinger
On Feb 8, 2014, at 4:34 PM, Eric Shubert e...@shubes.net wrote:
On 02/08/2014 02:40 PM, Sam Clippinger wrote
Yes, this is completely possible. The feature you're looking for is a
configuration directory -- it'll let you turn different options on or off for
different domains (and other conditions).
http://www.spamdyke.org/documentation/FAQ.html#FEATURE8
-- Sam Clippinger
On Feb 7, 2014
triggered, the remaining filters are
skipped. So if the missing rDNS filter is going to reject the connection but
is forced to wait until the recipient(s) are given, the RBL filters won't run
at all.
-- Sam Clippinger
On Feb 5, 2014, at 3:50 AM, Lawrence spamdyke.ad...@freeman.me.uk wrote
. I can't
imagine your helpdesk staff would thank you for that change though.
I'm already planning to add a filter to a future version to block
authentication unless SSL/TLS is in use, but I can't give you an ETA on that.
-- Sam Clippinger
On Feb 3, 2014, at 8:05 PM, Bruce Schreiber bschrei
it's
not localhost:25 but mail.domain.com:25)?
It works fine on my server on both port 25 (TLS) and port 465 (SSL), not that
that helps. :)
-- Sam Clippinger
On Feb 3, 2014, at 3:05 PM, Marc Gregel m...@gregel.net wrote:
Hi there,
after upgrading from 4.3.1 to 5.0.0 I can't use TLS
to recommend everyone NOT use the spamdyke-qrv
program for recipient validation.
-- Sam Clippinger
On Feb 3, 2014, at 10:10 AM, Stephen Marley step...@nxds.com wrote:
Hi Sam
I’ve done some more testing on the problem I have and it seems that if a
.qmail-user file contains an external forwarding
when you
see the 220 greeting from qmail:
./spamdyke --log-target stderr -lexcessive -r -R
/var/qmail/bin/qmail-smtpd
Most of the output will be from the DNS code -- you should be able to see
exactly what packets spamdyke sends to which nameservers and what the responses
are.
-- Sam
Then replace your existing spamdyke binary with the new one.
-- Sam Clippinger
On Feb 4, 2014, at 3:34 PM, Bruce Schreiber bschrei...@max.md wrote:
Sam,
I found this thread on the web from 2011.
https://www.mail-archive.com/spamdyke-users@spamdyke.org/msg03120.html
We are now thinking
That particular option went away in version 5.0.0, along with a few others. It
should be renamed to qmail-rcpthosts-file. The full list of
backwards-incompatible changes is here:
http://www.spamdyke.org/documentation/UPGRADING_version_4_to_version_5.txt
-- Sam Clippinger
On Feb 4
.
-- Sam Clippinger
On Feb 1, 2014, at 5:05 PM, Stephen Marley step...@nxds.com wrote:
Hi
I’ve just installed Spamdyke 5.0.0 and the spamdyke-qrv program is
incorrectly returning invalid recipient for addresses with .qmail- files that
forward to other valid addresses.
For example
could be a bug!
-- Sam Clippinger
On Jan 31, 2014, at 5:18 PM, Denny Jones lhweb...@aol.com wrote:
Not to point directly to a bug but I have been working on this issue for
quite some time so I'm pretty sure it'll keep on occurring.
Also, I only pasted 2 lines from the log file. In reality
That wasn't an intentional change -- I'll look into it. Thanks for reporting
this!
-- Sam Clippinger
On Jan 31, 2014, at 9:40 AM, Gary Gendel g...@genashor.com wrote:
Sam,
Not an issue but you should mark down that 5.0.0 treats the spawned
program argument differently than 4.x
there: Graphstat.
Easy, simple, convincing graphs are just a click away. They're really handy
for display on publicly visible monitors -- everyone loves a good graph!
Anyway, check it out:
http://www.graphstat.org/
-- Sam Clippinger
___
spamdyke
if they don't
match the username given during authentication (or if the domain doesn't
match). Lots of bug fixes too!
Because of all the changes to spamdyke's options, version 5.0.0 is not
backwards compatible with previous versions. Be sure to read the documentation
before upgrading!
-- Sam Clippinger
1 - 100 of 626 matches
Mail list logo
