[spamdyke-users] wishlist for RBL functions
Hi! I would have a wishlist for spamdyke, because it is a real gret software, and I plan to use it in all of my installations. 1. It would be nice if I can quarantine everykind of message. I'm thinking of the messages denied by RBL lists for example. It is very rare that there can be false positives, but this feature would be very nice. If someone is looking for a mail, I can consult the logfile of course, but I can't get the message back for the user, which can be a big problem. 2. For the lowering of false-positive messages created by RBLs, it would be nice if I could tell spamdyke to only greylist those, who come from an RBL, and if it passes the greylist-test, then let them in for further investigation (spamassassin, clamav etc.). Thank you very much! Daniel ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] wishlist for RBL functions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Snow schrieb: Hi! I would have a wishlist for spamdyke, because it is a real gret software, and I plan to use it in all of my installations. 1. It would be nice if I can quarantine everykind of message. I'm thinking of the messages denied by RBL lists for example. It is very rare that there can be false positives, but this feature would be very nice. If someone is looking for a mail, I can consult the logfile of course, but I can't get the message back for the user, which can be a big problem. That would raise your needed space to quarantine every mail. For me it would be 97% of incoming.You should think again about _why_ rblstmp ist blocking the mail-delivery in the beginning. Keeping the mails again would be more load of CPU and RAM. If someone is sending legal mail, and it's would be denied by any reason, you'll have a log, and the sender could be informed. If someone is missing mails, he will tell you. 2. For the lowering of false-positive messages created by RBLs, it would be nice if I could tell spamdyke to only greylist those, who come from an RBL, and if it passes the greylist-test, then let them in for further investigation (spamassassin, clamav etc.). Greylist and RBL are two different things. You shouldn't mix them up. RBL blocks _known_ bad IP's. False Positives will only occure if the sender has an IP wich had been abused before. If you got more false-positives then i think, please tell us some examples. Maybe there's a security issue or something. Thank you very much! Daniel -- ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users - -- Technischer Support/ Hotline BLACKBIT neue Medien GmbH | BLACKBIT neue Werbung GmbH Ernst-Ruhstrat-Str. 6 - D-37079 Göttingen Geschäftsführer: Stefano Viani | Daniel Gerlach Registergericht: Amtsgericht Göttingen, HRB 3222 Umsatzsteueridentifikationsnummer (§ 27a UstG): DE 813 114 917 Tel: +49 [551] 50675-50 - Fax: +49 [551] 50675-20 Störungs-Hotline (mobil): +49 [171] 745-843-8 E-Mail: [EMAIL PROTECTED] Klassische Werbung und Online-Marketing: http://www.blackbit.de Software fuer Online-Marketing: http://www.go-community.de -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIROyCWFnhIgg1RRoRAsdhAKCw3j7duyWo2HveHEg2ZiTLN28SzgCffKhe F+ukin56R66fIZN74h6BlKM= =99tT -END PGP SIGNATURE- ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
[spamdyke-users] Implementation issue with Spamdyke 3.1.8, Plesk 8.0.1, FreeBSD 6.0
I searched the archives and found what I thought I needed to determine how to properly setup Spamdyke 3.1.8 on a Plesk 8.0.1 server running FreeBSD6.0. What I found was that I needed to run Spamdyke before relaylock and if my current smtp entry in inetd.conf contained a rblsmtpd entry that I could simply replace that with a call to spamdyke. I did those things and I also successfully executed Spamdyke with the --confi-test and --config-test-user options. Upon inspection of /usr/local/psa/var/log/maillog I see every minute or two the following error: spamdyke[44404]: ERROR: unable to write 30 bytes to file descriptor 1: Broken pipe I don't know if this means email is not being delivered correctly or if it means that Spamdyke can't modify a file that may not be created or has incorrect permissions. I didn't find anything in the Spamdyke archives which would help me fix this issue so I'm hoping someone on the list can. My inetd.conf is shown below (contained on one line on server): smtp stream tcp nowait root /usr/local/psa/qmail/bin/tcp-env tcp-env /usr/local/bin/spamdyke -f /etc/spamdyke.conf /usr/local/psa/qmail/bin/relaylock /usr/local/psa/qmail/bin/qmail-smtpd /usr/local/psa/qmail/bin/smtp_auth /usr/local/psa/qmail/bin/true /usr/local/psa/qmail/bin/cmd5checkpw /usr/local/psa/qmail/bin/true My /etc/spamdyke.conf is: log-level=3 local-domains-file=/usr/local/psa/qmail/control/rcpthosts max-recipients=5 idle-timeout-secs=60 graylist-dir=/var/spamdyke/graylist-dir graylist-min-secs=300 graylist-max-secs=1814400 #policy-url=http://my.policy.explanation.url/ sender-blacklist-file=/var/spamdyke/sender-blacklist-file recipient-blacklist-file=/var/spamdyke/recipient-blacklist-file ip-in-rdns-keyword-file=/var/spamdyke/ip-in-rdns-keyword-file ip-blacklist-file=/var/spamdyke/ip-blacklist-file #rdns-blacklist-dir=/home/vpopmail/blacklist_rdns.d reject-empty-rdns reject-unresolvable-rdns #reject-ip-in-cc-rdns #rdns-whitelist-file=/home/vpopmail/whitelist_rdns ip-whitelist-file=/var/spamdyke/ip-whitelist-file greeting-delay-secs=5 #check-dnsrbl=zombie.dnsbl.sorbs.net #check-dnsrbl=dul.dnsbl.sorbs.net #check-dnsrbl=bogons.cymru.com reject-missing-sender-mx tls-certificate-file=/usr/local/psa/qmail/control/servercert.pem #access-file=/var/spamdyke/access-file recipient-whitelist-file=/var/spamdyke/recipient-whitelist-file Regards, Shane Bywater ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
