This ist my Plesk / xinetd configuration which works well. Spamdyke BEFORE relaylock had a reason I don't remember anymore ;)
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 All the best, Gero > I would try putting spamdyke between relaylock and qmail-smtpd: > > smtp stream tcp nowait root /usr/local/psa/qmail/bin/tcp-env > tcp-env /usr/local/psa/qmail/bin/relaylock > /usr/local/bin/spamdyke -f /etc/spamdyke.conf > /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 > > Shane Bywater schrieb: > > 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. _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
