John Dennis wrote: > >Depends on whether the client waits for a success status or not, which >if my memory serves me correctly (its been failing lately :-) is not the >behavior in an SMTP transaction. I believe the MTA accepts the input, >queues the request and control is returned, at that point I believe the >connection is typically closed. At this point the outgoing running will >loop again and attempt initiate a new SMTP transaction. At least that >how I think it works, plus the behavior is specific to each MTA.
Mailman, via SMTPDirect sends all the delivery chunks for a message before returning control to the outgoing runner. Assuming we're not VERPing or personalizing, it sends the 'MAIL FROM' command followed by SMTP_MAX_RCPTS 'RCPT TO' commands, followed by 'DATA' and the message. After receiving the response to the 'DATA', it (normally, but depends on SMTP_MAX_SESSIONS_PER_CONNECTION) sends the 'MAIL FROM' for the next chunk on the same connection. It may throw in another HELO/EHLO between transactions. This is in the Python smtplib, and I haven't looked in detail. >If the client waits for the transaction to complete they of course >you're right. The client (Mailman) waits for the response to the 'DATA' command for each chunk. This doesn't mean the mail has been sent, but it has been accepted and queued within the MTA. How many queues the MTA uses at this point to actually send the mail is up to the MTA, not Mailman. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
