stderr use under xinetd

[Graham M. <gr...@we...>]

Hi All,

On a Plesk server, it uses xinetd to start qmail. It also uses qmail-spp.

I have written a triplet checking greylisting plugin using sqlite3 and it is working fine except
when I change the log level and make it noisy.

Normally the plugin only sends messages to stderr when a critical error occurs. I have never
seen anything in the log files.

When I decrease the log level thus increasing the messages to stderr, I do not get anything in
the log and the client end of the transaction is seeing errors to do with TLS (which is probably
from the next thing in the chain /var/qmail/bin/smtp_auth).

There would always be more than one line output to stderr when this level of logging is
selected.

The plugin is based on Peter Conrad's old greylisting-spp work with substantial upgrading for
sqlite3 among others.

It passes the make tests that simulate various error conditions and expects certain answers from
the plugin. The stderr strings appear on the console (and can be redirected with 2>filename)
during this phase of the make.

I have read that xinetd sends the stderr output back to the client or into the stream which may
explain the messed up TLS issue.

Any ideas?

Happy to send more detail of error messages and configuration and code etc.

Cheers
Graham