Dears,
I did try to block incoming mails from dynamic IPs but with partial
success still having problem with:
May 4 08:19:31 fw spamdyke[21023]: DENIED_GRAYLISTED from:
v_ashle...@pelicanhotel.com to: yy...@x.cz origin_ip: 200.83.179.199
origin_rdns: pc-199-179-83-200.cm.vtr.net auth:
Did you find any DENIED_IP_IN_RDNS?
How are the file rights?
I have entered .com and .net, not only com and net.
Regards,
Ulrich
Von: Eduard Svarc esv...@intertech.cz
Antworten an: spamd...@intertech.cz, spamdyke users
spamdyke-users@spamdyke.org
Datum: Mon, 4 May 2009 08:32:35 +0200
An:
Dear Ulrich,
I didn't. I had these keywords without '.' as you can see in thread where
I have listed full content of my file:
/etc/spamdyke.d/ip-in-rdns-keyword-blacklist-file
contains:
dsl
com
net
broadband
dynamic
Adding it now will see result.
Thank You
Eduard
Thank you, Sam, for a very excellent explanation of how it all works.
Have you considered writing an MTA to replace qmail which can use spamdyke?
Looking forward to the next version...
Bucky
On 5/4/2009 spamdyke-users-requ...@spamdyke.org wrote:
When a message is delivered to a stock
You know... I may have sub-consciously meant it that way too! :-) Not
necessarily in regards to Spamdyke, but in general, I've found that most
Features are not. In this case, I think it will be a great addition to
Spamdyke.
I know the fact that chkusr is available is a plus for it, but, for
BC wrote:
Thank you, Sam, for a very excellent explanation of how it all works.
Have you considered writing an MTA to replace qmail which can use spamdyke?
Looking forward to the next version...
Bucky
Why reinvent the wheel ? could be done just by rewriting only the
qmail-smtpd.
