At 03:08 AM 5/30/2011, Ron Pitts wrote:
>We are testing surgemail to replace our production email server and
>experiencing problems sending mail via the .NET Framework, now and
>again we receiving an error that the socket was closed, e.g. :
>
>Message: Unable to read data from the transport connection:
>net_io_connectionclosed.

Make sure the IP address of the machine sending the messages is 
exempt from any and all sending/connection/max message count limits 
or Surgemail will attempt to stop the "abuse" from that machine's IP address.

-Robert





>Stack trace:    at
>System.Net.Mail.SmtpReplyReaderFactory.ProcessRead(Byte[] buffer,
>Int32 offset, Int32 read, Boolean readLine)
>    at System.Net.Mail.SmtpReplyReaderFactory.ReadLines(SmtpReplyReader
>caller, Boolean oneLine)
>    at System.Net.Mail.SmtpReplyReaderFactory.ReadLine(SmtpReplyReader caller)
>    at System.Net.Mail.CheckCommand.Send(SmtpConnection conn, 
> String& response)
>    at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender,
>MailAddressCollection recipients, String deliveryNotify,
>SmtpFailedRecipientException& exception)
>    at System.Net.Mail.SmtpClient.Send(MailMessage message)
>
>This was reported previously via Microsoft by someone else using
>surgemail, is this a feature of the mail server?

"Well done is better than well said." - Benjamin Franklin