>Right, the STMP interaction is all coming from the client. The server has no >way to talk back. Maybe you can try to return a series of: >250-Waiting<crlf> >250-Waiting<crlf> > >to keep the client from timeout?
I had tried the 250, it just thinks of it as an OK (I need it to wait just after it sends the DATA stream, so a 250 tells it the stream was received ok). However, I tried some other 2xx codes, and it looks like 211 (help) works. The RFC says that the 211 help code is not supposed to effect the current status of the communication. So far in my limited testing, the email clients accept the 211 and ignore it. So they hold the connection open because they see data coming back, but they don't issue an error because they ignore the command and continue to wait for either a 250 or a 5xx saying the data was ok or errored. So it looks like I can get around my timeout problem. Thanks -chris <http://www.mythtech.net> ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
