Comment 11 for bug 102947

Yes. The message goes to stderr and maildrop tries to continue. In case authdaemon is not essential to message delivery, the message is harmless and maildrop succeeds. That is why its exit code indicates (definitively) that there was a failure. However, in cases where authdaemon *is* essential to message delivery, the message is a debugging aid that complements the exit code that indicates that there *was* a failure.

Admittedly, it might be nice if the stderr from the connect attempt could be buffered and printed out only upon an error exit. But the lack of this may be due to some technical constraint such as the library printing it rather than maildrop itself (haven't checked this time).