Really, this belongs on a spamdyke forum, but you guys are geniuses. And since there is no spamdyke forum, I request your advice.
I'm running Spamdyke on a plesk 8.4 FC7 box.
I know spamdyke is working... by the fewer spam emails, by increasing greylists, and by a few reports of senders getting "You email is delayed" reports. We've been using it for 2.5 months.
HOWEVER... I don't see anything in /usr/local/psa/var/log/maillog about spamdyke. My config file is below... am I missing something? Since spamdyke uses the LOG_MAIL, shouldn't it automatically post to the right log in plesk?
I'm trying to find out if spamdyke is the culprit for putting the kibosh on an email someone is trying to send me.
**** my spamdyke config ****
log-level=verbose
local-domains-file=/var/qmail/control/rcpthosts
max-recipients=30
idle-timeout-secs=60
graylist-dir=/var/qmail/spamdyke/greylist
graylist-min-secs=300
graylist-max-secs=1800400
sender-blacklist-file=/var/qmail/spamdyke/blacklist_senders
sender-whitelist-file=/var/qmail/spamdyke/whitelist_senders
recipient-blacklist-file=/var/qmail/spamdyke/blacklist_recipients
ip-in-rdns-keyword-file=/var/qmail/spamdyke/blacklist_keywords
ip-blacklist-file=/var/qmail/spamdyke/blacklist_ip
rdns-whitelist-file=/var/qmail/spamdyke/whitelist_rdns
ip-whitelist-file=/var/qmail/spamdyke/whitelist_ip
reject-empty-rdns
reject-unresolvable-rdns
greeting-delay-secs=5
never-greylist-ip-file=/var/qmail/spamdyke/never_greylist
check-dnsrbl=zen.spamhaus.org
check-dnsrbl=dnsbl.ahbl.org
check-dnsrbl=dnsbl.njabl.org
check-dnsrbl=dnsbl.sorbs.net
check-dnsrbl=bogons.cymru.com
check-dnsrbl=bl.spamcop.net
check-dnsrbl=list.dsbl.org
reject-missing-sender-mx
Spamdyke doesn't seem to be logging
-
- Forum User
- Posts: 17
- Joined: Tue Apr 22, 2008 2:12 pm
You should see loads and loads of stuff in your maillog.
DENY_XXXX where XXX is one of Spamdyke's various denies, inc graylist.
And also ALLOWED when email is allowed.
Version 4 is just out which builds on the super-wonderful-ness of 3.x. Maybe you should give that a try?
Are you really sure it is working? I don't see how it can be if you aren't getting any logging, unless the logs are going to the wrong place somehow.
What does your smtp_psa look like?
Also there is a mailing list for spamdyke which is busy (in a good way) and anybody having problems always gets a reply, quite often from the author himself.
Faris.
DENY_XXXX where XXX is one of Spamdyke's various denies, inc graylist.
And also ALLOWED when email is allowed.
Version 4 is just out which builds on the super-wonderful-ness of 3.x. Maybe you should give that a try?
Are you really sure it is working? I don't see how it can be if you aren't getting any logging, unless the logs are going to the wrong place somehow.
What does your smtp_psa look like?
Also there is a mailing list for spamdyke which is busy (in a good way) and anybody having problems always gets a reply, quite often from the author himself.
Faris.
--------------------------------
<advert>
If you want to rent a UK-based VPS that comes with friendly advice and support from a fellow ART fan, please get in touch.
</advert>
<advert>
If you want to rent a UK-based VPS that comes with friendly advice and support from a fellow ART fan, please get in touch.
</advert>
-
- Forum User
- Posts: 17
- Joined: Tue Apr 22, 2008 2:12 pm
It was NOT working
Ok, this is weird. I thought greylisting was working because I had some people actually get warnings of their emails being delayed coming into my server-- I only assumed that was from spamdyke.
Furthermore, *something* was creating entries in the graylisting folders. In other words, email addresses were getting added to the graylists.
HOWEVER... it appears that spamdyke was not actually doing all that it should've been.
Solution: I upgraded to Spamdyke 4.0, ran some configuration tests, and now I have a working spamdyke config that is logging just as I like it to!
Thanks gents...
Furthermore, *something* was creating entries in the graylisting folders. In other words, email addresses were getting added to the graylists.
HOWEVER... it appears that spamdyke was not actually doing all that it should've been.
Solution: I upgraded to Spamdyke 4.0, ran some configuration tests, and now I have a working spamdyke config that is logging just as I like it to!
Thanks gents...