Hector Santos wrote:
IMO, I don't think it will be good engineering on the client part if it
does not reset a SMTP timeout when reading each line buffered or not. As
long as each line begins with a XYZ- number, its all good
I disagree. Now that some people have the (misguided) view that
tarpitting is a good thing, and they sometimes incorrectly trigger
tarpitting on valid e-mail, I think a defensive client *should*
enforce an overall timeout on a command-and-complete-reply. If you're
a very large e-mail sender, you really don't want clients on your main
machine tied up for too long -- if the SMTP server is being slow, you
want to time out and shunt the mail to a machine dedicated to dealing
with slow recipients.
Regards,
David.