Pegasus Mail & Mercury

Without changing any settings, Pegasus  has started failing to sent emails.

When sending, the bottom of the window says 'SMTP:sending message 1 of 1 .... 0%, then after a little while, an error message appears: "An unexpected network error occurred during transaction with the host".

In my inbox, the following message appears:

Connection established to 218.214.225.98
>> 0034 220 smtp.syd.people.net.au ESMTP
<< 0020 EHLO

[192.168.1.3]
>> 0028 250-smtp.syd.people.net.au
>> 0016 250-PIPELINING
>> 0014 250 8BITMIME
<< 0037 MAIL FROM:<myemail@people.net.au>
>> 0008 250 ok
<< 0035 RCPT TO:<recipients email@mh.org.au>
>> 0008 250 ok
<< 0006 DATA
>> 0014 354 go ahead
>> 0022 451 timeout (#4.4.2)

 As I said, I haven't fiddled with the settings, but this problem doesn't seem to clear despite restarting, resetting my ADSL modem, etc.

Advice appreciated! 

 

PaulG:

Without changing any settings, Pegasus  has started failing to sent emails.

When sending, the bottom of the window says 'SMTP:sending message 1 of 1 .... 0%, then after a little while, an error message appears: "An unexpected network error occurred during transaction with the host".

In my inbox, the following message appears:

Connection established to 218.214.225.98
>> 0034 220 smtp.syd.people.net.au ESMTP
<< 0020 EHLO

[192.168.1.3]
>> 0028 250-smtp.syd.people.net.au
>> 0016 250-PIPELINING
>> 0014 250 8BITMIME
<< 0037 MAIL FROM:<myemail@people.net.au>
>> 0008 250 ok
<< 0035 RCPT TO:<recipients email@mh.org.au>
>> 0008 250 ok
<< 0006 DATA
>> 0014 354 go ahead
>> 0022 451 timeout (#4.4.2)

 As I said, I haven't fiddled with the settings, but this problem doesn't seem to clear despite restarting, resetting my ADSL modem, etc.

Advice appreciated! 

You might not have changed anything but the people with the server might have.  That timeout line looks a bit strange since it's got the SMTP reply code.  I also assume you changed the email addresses since the RCPT TO: address is invalid.

 

---

Thomas R. Stephenson
Member of Pegasus Mail Support Team

Thanks for the reply. Yes, I changed the RCPT TO: address.

You may be right about the server - the problem seems to have rectified overnight, although I recall this happening intermittently over the past 6 months or so - a day or two of not being able to send emails and then all's well - quite frustrating. 

Same problem ... different error messages...

"Description of error: Connection Timeout (no response from host)"

>> 0016 250-PIPELINING
>> 0014 250 8BITMIME
<< 0037 MAIL FROM:<me@email.com>
>> 0008 250 ok
<< 0033 RCPT TO:<them@email.com>
>> 0008 250 ok
<< 0006 DATA
>> 0014 354 go ahead
8: Socket read timeout.

or 

... etc
>> 0008 250 ok
<< 0006 DATA
>> 0014 354 go ahead
7: Socket read error 2746.


Is this still my internet provider? Or is there something wrong from my end?

 

Can you send mail with another mail account (SMTP server) ?

---

kind regards

>> 0008 250 ok
<< 0006 DATA
>> 0014 354 go ahead
7: Socket read error 2746.

 The POP3/SMTP transmissions may fail if the MTU packet size is so large that a packet is fragmented.  In many cases the receiving system router blocks the receiving servers "packets fragmented" response to the sending system using "MTU Discovery".  These oversize packets are not accepted and so are resent.  This results in a timeout, generally at the end of the message transmission but it can be anywhere in the process.  You need to reduce the MTU size. Windows defaults to a 1500 MTU and many routers and DSL connections need 1492.  You might simply want to turn off the MTU Discovery operation.

You might want to get a copy of SG TCP Optimizer that I find quite handy.  http://www.speedguide.net/downloads.php  This little utility will allow you to test your MTU for maximum size without fragmentation against specific servers.  If will also make it easy to adjust the MTU.  

And finally, does this computer, by chance, happen to have an NVidia NForce 4 chipset on the motherboard?  If so, many other have had this exact problem, and it turned out to be an optimization setting for the built in NIC which caused the problems with packet fragmentation. Disabling the advanced optimization capability called "checksum offload" made all the problems of sending SMTP mail via WinPMail disappear.

---

Thomas R. Stephenson
Member of Pegasus Mail Support Team