Are you trying to filter messages which are being submitted by an
authenticated sender? Spamdyke filters are all bypassed for
authenticated senders. You're *really* not using spamdyke to its best
advantage here. Spamdyke is designed to be used to block spam from
external mail servers.
It sounds to me as though eMPF would be a better tool to use for what
you're trying to accomplish.
HTH.
--
-Eric 'shubes'
On 05/05/2013 09:02 PM, Amir Abbasi wrote:
I just want to use
blacklist_recipients,blacklist_senders,header-blacklist features (for
example I've put my gmail account in /etc/spamdyke/blacklist_recipients
file but the server relayed the test message to that), so I commented
out the others, here is the configuration:
#dns-blacklist-entry=zombie.dnsbl.sorbs.net
#dns-blacklist-entry=dul.dnsbl.sorbs.net
#dns-blacklist-entry=bogons.cymru.com
#dns-blacklist-entry=zen.spamhaus.org
#dns-blacklist-entry=bl.spamcop.net
#graylist-dir=/var/spamdyke/graylist
#graylist-level=none
#graylist-max-secs=2678400
#graylist-min-secs=180
#greeting-delay-secs=6
#idle-timeout-secs=60
ip-blacklist-file=/etc/spamdyke/blacklist_ip
#ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
#ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
ip-whitelist-file=/etc/spamdyke/whitelist_ip
local-domains-file=/var/qmail/control/rcpthosts
log-level=info
log-target=stderr
max-recipients=50
#policy-url=http://my.policy.explanation.url/
#rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
#rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
#reject-empty-rdns
#reject-ip-in-cc-rdns
#reject-missing-sender-mx
#reject-unresolvable-rdns
sender-blacklist-file=/etc/spamdyke/blacklist_senders
sender-whitelist-file=/etc/spamdyke/whitelist_senders
#tls-certificate-file=/var/qmail/control/servercert.pem
#tls-level=smtp
header-blacklist-file=/etc/spamdyke/header-blacklist
----- Original Message ----- From: "Eric Shubert" <e...@shubes.net>
To: <qmailtoaster-list@qmailtoaster.com>
Sent: Sunday, May 05, 2013 7:43 PM
Subject: [qmailtoaster] Re: SpamDyke does not filter relayed messages
On 05/05/2013 04:00 AM, Amir Abbasi wrote:
Hi,
I've insalled and configured SpamDyke recently, but it is not working on
relayed messages. (/etc/tcprules.d/tcp.smtp is as below)
xx.xx.xx.xx:allow,RELAYCLIENT="",SENDER_NOCHECK="1",QMAILQUEUE="/var/qmail/bin/simscan",NOP0FCHECK="1"
shall I configure anything else? (Like Spamassassin).
The tcp.smtp file typically doesn't affect spamdyke.
Are you seeing spamdyke messages in your smtpd log at all?
You might want to post your spamdyke config.
Note, updating the qmail-toaster package will effectively disable
spamdyke. Simply rerun qtp-install-spamdyke after installing
qmail-toaster. Your spamdyke settings will be left intact.
--
-Eric 'shubes'
---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
