On 03/20/2012 02:35 PM, Eric Shubert wrote: > Background: I'm running qmailtoaster (QMT) with spamdyke 4.3.1. QMT has > smtp-auth patch with cram-md5 capability. I would like to turn off > cram-md5 using a simple configuration change, rather than having to > recompile and reinstall the qmail-toaster package. So I figure I'll let > spamdyke handle authentication (via vpopmail), and I can control what > happens via spamdyke's config file. > > So I add these 2 lines to my spamdyke.conf: > smtp-auth-command=/home/vpopmail/bin/vchkpw /bin/true > smtp-auth-level=always > > However, when I run --config-test, I get the following error: > > spamdyke 4.3.1+TLS+CONFIGTEST+DEBUG (C)2012 Sam Clippinger, samc (at) > silence (dot) org > http://www.spamdyke.org/ > > Use -h for an option summary or see README.html for complete option details. > > SUCCESS: Running tests as user vpopmail(89), group vchkpw(89). > SUCCESS: /var/qmail/bin/qmail-smtpd appears to offer TLS support but > spamdyke will intercept and decrypt the TLS traffic so all of its > filters can operate. > ERROR: /var/qmail/bin/qmail-smtpd appears to offer SMTP AUTH support but > spamdyke cannot offer and process authentication itself because one of > the following options was not given: "access-file", "local-domains-file" > or "smtp-auth-command" > SUCCESS(config-file): Opened for reading: > /etc/spamdyke/spamdyke.confsmtp-auth-command=/home/vpopmail/bin/vchkpw > /bin/true > smtp-auth-level=always > > SUCCESS(dns-resolv-conf): Opened for reading: /etc/resolv.conf > SUCCESS(graylist-level): Graylist directory tests succeeded: > /var/spamdyke/graylist > SUCCESS(hostname-file): Opened for reading: /var/qmail/control/me > SUCCESS(ip-blacklist-file): Opened for reading: /etc/spamdyke/blacklist_ip > SUCCESS(ip-in-rdns-keyword-blacklist-file): Opened for reading: > /etc/spamdyke/blacklist_keywords > SUCCESS(ip-in-rdns-keyword-whitelist-file): Opened for reading: > /etc/spamdyke/whitelist_keywords > SUCCESS(ip-whitelist-file): Opened for reading: /etc/spamdyke/whitelist_ip > SUCCESS(local-domains-file): Opened for reading: > /var/qmail/control/rcpthosts > SUCCESS(rdns-blacklist-file): Opened for reading: > /etc/spamdyke/blacklist_rdns > SUCCESS(rdns-whitelist-file): Opened for reading: > /etc/spamdyke/whitelist_rdns > SUCCESS(recipient-blacklist-file): Opened for reading: > /etc/spamdyke/blacklist_recipients > SUCCESS(recipient-whitelist-file): Opened for reading: > /etc/spamdyke/whitelist_recipients > SUCCESS(sender-blacklist-file): Opened for reading: > /etc/spamdyke/blacklist_senders > SUCCESS(sender-whitelist-file): Opened for reading: > /etc/spamdyke/whitelist_senders > SUCCESS(smtp-auth-level): File is executable: /home/vpopmail/bin/vchkpw > WARNING(smtp-auth-level): Authentication command is not owned by root. > Some require being setuid root to read system passwords: > /home/vpopmail/bin/vchkpw: owned by vpopmail(89) > 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. > > Why does spamdyke apparently not see the smtp-auth-command option? > Looks like a bug to me. > > TIA, Sam. >
I did a little testing, and this appears to be just a bug in the config-test. With these settings, cram-md5 is not advertised, and authentication does work. -- -Eric 'shubes' _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
