Re: tmda-ofmipd raises exception on TLS

Stephen Warren <[email protected]>
Newsgroups gmane.mail.spam.tmda.user
Message-ID <[email protected]>
Ole Wolf wrote:
> Just to make sure it had nothing to do with EHLO commands and such  
> entered after the secure connection had started, I configured  
> tmda-ofmipd to start with SSL rather than optional TLS. Connecting  
> with an email client configured to use SSL, the ofmipd debug output is:
> 
> Incoming connection from: ('192.168.1.2', 31233)
> Incoming connection to: ('192.168.1.2', 8025)
> Data: 'EHLO hostname'
> error: uncaptured python exception, closing channel  
> <__main__.SMTPSession connected 192.168.1.2:31233 at 0x9546d4c> (<type  
> 'exceptions.ValueError'>: [/usr/lib/python2.5/asyncore.py|read|68]  
> [/usr/lib/python2.5/asyncore.py|handle_read_event|390]  
> [/usr/bin/tmda-ofmipd|handle_read|1285]  
> [/usr/lib/python2.5/site-packages/tlslite/integration/AsyncStateMachine.py|inReadEvent|132] [/usr/lib/python2.5/site-packages/tlslite/integration/AsyncStateMachine.py|_doReadOp|177] [/usr/bin/tmda-ofmipd|outReadEvent|1312] [/usr/lib/python2.5/asynchat.py|handle_read|137] [/usr/bin/tmda-ofmipd|found_terminator|222] [/usr/bin/tmda-ofmipd|smtp_EHLO|463] [/usr/bin/tmda-ofmipd|push|189] [/usr/lib/python2.5/asynchat.py|push|160] [/usr/lib/python2.5/asynchat.py|initiate_send|219] [/usr/bin/tmda-ofmipd|send|1331] [/usr/lib/python2.5/site-packages/tlslite/integration/AsyncStateMachine.py|setWriteOp|231] [/usr/lib/python2.5/site-packages/tlslite/integration/AsyncStateMachine.py|_doWriteOp|181]  
> [/usr/lib/python2.5/site-packages/tlslite/TLSRecordLayer.py|writeAsync|254])

This particular exception occurs when TMDA (or the tlslite internals) 
attempts to write to a closed connection.

I'm guessing what happens is that the "auth failed" response gets sent 
back to the client, which then disconnects, but the disconnect occurs 
before all the SSL protocol hand-shaking has been transferred, hence the 
exception.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.