A BUGNOTE has been added to this bug.
======================================================================
http://dbmail.org/mantis/bug_view_advanced_page.php?bug_id=0000070
======================================================================
Reported By:                danweber
Assigned To:                aaron
======================================================================
Project:                    DBMail
Bug ID:                     70
Category:                   LMTP daemon
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
======================================================================
Date Submitted:             23-Aug-04 01:43 CEST
Last Modified:              26-Aug-04 06:08 CEST
======================================================================
Summary:                    Fails to give reponse upon completion of rcpt
Description: 
A responce is needed directly after rcpt command.  Otherwise its
incompatible with the rfc, and it also makes python hang.    I stumbled
upon this when I was adding lmtp support for mailbox2dbmail.
======================================================================

----------------------------------------------------------------------
 ilja - 23-Aug-04 13:32 CEST 
----------------------------------------------------------------------
AFAIK the client _should_ support pipelining, which means the respons comes
after the DATA command, not after every RCPT command.

----------------------------------------------------------------------
 aaron - 23-Aug-04 18:11 CEST 
----------------------------------------------------------------------
Actually, pipelining means that neither side should block or wait for
anything during the RCPT stage. So both behaviors are slightly wrong.

----------------------------------------------------------------------
 danweber - 24-Aug-04 18:50 CEST 
----------------------------------------------------------------------
Its good practice to send a response after rcpt.  This way it allows a
compatible smtp client to be used with it, like python.

Dan

----------------------------------------------------------------------
 aaron - 24-Aug-04 19:28 CEST 
----------------------------------------------------------------------
Oh, that's a good point. LMTP is a dialect of SMTP, the only difference is
the HELO/EHLO/LHLO greeting. Simple scripts that speak simple SMTP can be
easily modified to work with LMTP, but adding in the pipelining is more
hassle than needed, since the particular behavior we are using isn't quite
correct anyhow.

So I agree we should change the responses to happen immediately following
each RCPT. I'll post a patch this evening.

----------------------------------------------------------------------
 aaron - 26-Aug-04 06:08 CEST 
----------------------------------------------------------------------
This turns out to be fairly hard because I abstracted the list code out to
a separate function, and so I'll need to un-abstract it a little bit. I'm
still working on it, and expect to be done tomorrow evening. I'll commit
the changes to HEAD and Ilja can patch it back to the release branch once
we're 110% sure it's a correct patch.

Bug History
Date Modified  Username       Field                    Change              
======================================================================
23-Aug-04 01:43danweber       New Bug                                      
23-Aug-04 13:32ilja           Bugnote Added: 0000182                       
23-Aug-04 18:11aaron          Bugnote Added: 0000191                       
24-Aug-04 18:50danweber       Bugnote Added: 0000197                       
24-Aug-04 19:28aaron          Bugnote Added: 0000199                       
25-Aug-04 11:04ilja           Assigned To               => aaron           
25-Aug-04 11:04ilja           Status                   new => assigned     
26-Aug-04 06:08aaron          Bugnote Added: 0000207                       
======================================================================

Reply via email to