Actually that was a change I made just today, it was sender-blacklist and I changed it to sender-blacklist.conf. I had run the config test earlier today before that change and everything was fine.
I just ran the config test again. There is only one error which I don't know how to fix having to do with grey listing. I have grey listing off on purpose. Here is my result > spamdyke --config-test -f /etc/spamdyke.conf /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true spamdyke 4.2.0+TLS+CONFIGTEST+DEBUG (C)2011 Sam Clippinger, samc (at) silence (dot) org http://www.spamdyke.org/ [11] Use -h for an option summary or see README.html for complete option details. WARNING: Running tests as superuser root(0), group root(0). These test results may not be valid if the mail server runs as another user. SUCCESS(binary-check): File is executable: /usr/local/bin/spamdyke SUCCESS: /var/qmail/bin/relaylock appears to offer TLS support but spamdyke will intercept and decrypt the TLS traffic so all of its filters can operate. SUCCESS: /var/qmail/bin/relaylock appears to offer SMTP AUTH support. spamdyke will observe any authentication and trust its response. SUCCESS(config-file): Opened for reading: /etc/spamdyke.conf SUCCESS(dns-resolv-conf): Opened for reading: /etc/resolv.conf SUCCESS(graylist-exception-ip-file): Opened for reading: /etc/spamdyke.d/graylist-exception-rdns.conf SUCCESS(graylist-exception-rdns-file): Opened for reading: /etc/spamdyke.d/graylist-exception-ip.conf ERROR(graylist-level): The "graylist-level" option is "none" but other graylist options were given. They will all be ignored. SUCCESS(hostname-file): Opened for reading: /var/qmail/control/me SUCCESS(ip-blacklist-file): Opened for reading: /etc/spamdyke.d/ip-blacklist.conf SUCCESS(ip-whitelist-file): Opened for reading: /etc/spamdyke.d/ip-whitelist.conf SUCCESS(local-domains-file): Opened for reading: /var/qmail/control/rcpthosts SUCCESS(rdns-whitelist-file): Opened for reading: /etc/spamdyke.d/rdns-whitelist.conf SUCCESS(recipient-whitelist-file): Opened for reading: /etc/spamdyke.d/receivers_whitelist.conf SUCCESS(sender-blacklist-file): Opened for reading: /etc/spamdyke.d/sender-blacklist.conf SUCCESS(sender-whitelist-file): Opened for reading: /etc/spamdyke.d/sender-whitelist.conf SUCCESS(tls-certificate-file): Opened for reading: /var/qmail/control/servercert.pem SUCCESS(tls-certificate-file): Certificate and key loaded; SSL/TLS library successfully initialized ERROR: Tests complete. Errors detected. On Mon, 13 Jun 2011 18:08:25 -0500, Sam Clippinger wrote: > I think there may be some typos involved here. Your spamdyke.conf file > gives the sender blacklist file as > "/etc/spamdyke.d/sender-blacklist.con" (note the missing "f") but your > prior emails refer to "sender-blacklist.conf". Your recipient whitelist > is given in spamdyke.conf with an underscore, not a hyphen. Have you > double-checked to make sure the filenames are absolutely correct? Are > you seeing any errors in your log file? Have you tried running the > "config-test" feature to look for configuration problems? > > I agree with Eric -- it looks like a whitelist is causing these messages > to be accepted. If you could turn up the log-level to "verbose" or > higher, spamdyke should log any whitelists that are being matched. > > -- Sam Clippinger > > On 6/13/11 4:53 PM, Spamdyke User wrote: > >> I can't think of one.. With spamdyke working this way, I am having to use my firewall to block certain senders which is not a good thing.. I will attach my spamdyke.conf. There isn't much of anything in the files in /etc/spamdyke.d/ just a small list of 5 addresses in the ip_whiltelist.conf file On Mon, 13 Jun 2011 14:00:15 -0700, Eric Shubert wrote: >> >>> Bad guess. :( Is there some (other) whitelist parameter that's being satisfied? -- -Eric 'shubes' On 06/13/2011 01:43 PM, Spamdyke User wrote: >>> >>>> service smtp { disable = no socket_type = stream protocol = tcp wait = no user = root instances = UNLIMITED env = SMTPAUTH=1 server = /var/qmail/bin/tcp-env server_args = -Rt0 /usr/local/bin/spamdyke -f /etc/spamdyke.conf /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true } On Mon, 13 Jun 2011 13:23:31 -0700, Eric Shubert wrote: >>>> >>>>> I would suspect that your spamdyke.conf file somehow isn't the one being used. Just a guess. What does your run file contain? >>>> _______________________________________________ spamdyke-users mailing list [email protected] [1] [email protected] [2]> http://www.spamdyke.org/mailman/listinfo/spamdyke-users [3] >>> _______________________________________________ spamdyke-users mailing list [email protected] [4] [email protected] [5]> http://www.spamdyke.org/mailman/listinfo/spamdyke-users [6] >> _______________________________________________ spamdyke-users mailing list [email protected] [7] http://www.spamdyke.org/mailman/listinfo/spamdyke-users [8] > > _______________________________________________ > spamdyke-users mailing list > [email protected] [9] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users [10] Links: ------ [1] mailto:[email protected] [2] mailto:[email protected] [3] http://www.spamdyke.org/mailman/listinfo/spamdyke-users [4] mailto:[email protected] [5] mailto:[email protected] [6] http://www.spamdyke.org/mailman/listinfo/spamdyke-users [7] mailto:[email protected] [8] http://www.spamdyke.org/mailman/listinfo/spamdyke-users [9] mailto:[email protected] [10] http://www.spamdyke.org/mailman/listinfo/spamdyke-users [11] http://www.spamdyke.org/
_______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
