Hi Sam, Am 16.10.2008 20:05 Uhr, Sam Clippinger schrieb: > I don't think it's related to a qmail patch. In a "normal" qmail > installation that uses tcpserver, only stdout is sent to the network. > stderr is used for logging, which is why spamdyke supports sending its > log messages there. In Plesk installations, xinetd is used instead of > tcpserver, which seems to send stderr to the network also.
I rechecked the qmail-spp docs and you are right. Stderr is also used by spp to log errors, so it must be and issue with xinetd. It's hard to find the source of an error with that mixture of processes interacting and all the different patched qmail variants. > -- Sam Clippinger -- Felix > Felix Buenemann wrote: >> Hi Sam, >> >> Am 16.10.2008 16:37 Uhr, Sam Clippinger schrieb: >> >>> Using the full logging feature with a "log-level" option set to >>> "excessive" will no longer send log output to the remote server when >>> spamdyke is used on Plesk servers. Thanks to Arthur Girdari for >>> reporting this one and helping to track it down. >>> >> I think this isssue is not related to the qmail-spp[1] patch, which >> Plesk is using. It uses the stderr to send responses to the client, so >> stderr may no longer be used for error logging. I had a similar isssue >> with simscan which I patched to use syslog() to work arround this problem. >> So other users running qmail-spp will be affected by this aswell. >> >> [1] http://qmail-spp.sourceforge.net/ >> >> -- Felix Buenemann >> _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
