This error means that the remote server disconnected while spamdyke still had data to send, most likely because the spammer's software saw an error and immediately closed the connection. spamdyke doesn't know what to do with the leftover data, so it logs an error. You can safely ignore it.
If you change your spamdyke.conf file to reduce "log-level" to 2, the error message won't be logged. In the upcoming version (4.0.0) I've reduced this message's urgency, so it won't appear so easily. -- Sam Clippinger Shane Bywater wrote: > 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 > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
