Ralf Hildebrandt:
> * Wietse Venema <wie...@porcupine.org>:
> 
> > > Jul  3 17:44:00 mail postfix/smtpd[1210]: SSL_accept error from 
> > > post.blossin.de[217.92.177.100]: -1
> > > Jul  3 17:53:22 mail postfix/smtpd[1174]: SSL_accept error from 
> > > post.blossin.de[217.92.177.100]: -1
> > > Jul  3 18:31:12 mail postfix/smtpd[8533]: SSL_accept error from 
> > > post.blossin.de[217.92.177.100]: -1
> > > Jul  4 15:13:25 mail postfix/smtpd[9088]: SSL_accept error from 
> > > post.blossin.de[217.92.177.100]: -1
> > > 
> > > ...
> > > 
> > > Jul  5 11:38:38 mail postfix/smtpd[17412]: SSL_accept error from 
> > > www.neuro.med.tu-dresden.de[141.76.248.20]: 0
> > > Jul  6 02:32:25 mail postfix/smtpd[1491]: SSL_accept error from 
> > > server.detodos.com.br[189.90.142.30]: 0
> > > 
> > > So what are those?
> > 
> > Postfix prints all information that is available on the OpenSSL
> > error stack. The absence of such logging suggests that the error
> > stack is empty (perhaps the client hung up), 
> 
> I guess so then
> 
> > or that your grep(1) command eliminated them.
> 
> That's all there was. OK, I'll just ignore those then.

I would not deny that this user interface can be improved.  One
minor improvement would be to log "lost connection" when the OpenSSL
error stack is empty (i.e. when ERR_peek_error() returns an end-of-data
indication instead of an OpenSSL error number).

        Wietse

Reply via email to