POP3 Network or Protocol Error - Socket failed 277A

irelam

posted Oct 26 '07 at 5:18 am

Code 227A is not a Winsock error message, the Url below lists all Winsock codes:

http://msdn2.microsoft.com/en-us/library/ms740668.aspx

I think you should check your router documentation and/or the vendor site

Martin

Code 227A is not a Winsock error message, the Url below lists all Winsock codes:http://msdn2.microsoft.com/en-us/library/ms740668.aspx&nbsp;I think you should check your router documentation and/or the vendor siteMartin &nbsp;

Ambassador

posted Oct 24 '07 at 11:07 pm

I am running v4.41 and have been regularly experiencing an error message when trying to send or receive mail. The message "POP3 Network or Protocol Error - A network error occurred during connection to the host", and also "3: Socket failed, 277A".

This usually happens about twice a day, and I always have to close Pegasus Mail and reload the program, and then it is OK. I should add here that other internet services are available when this happens, but Pegasus just will not send or receive until I reload.

Looking at other postings, I gather that this is not a Pegasus Mail issue as such, but I don't know what the code "277A" is indicating - and therefore am at a loss to know how to resolve this?

Thanks,

David

Hi I am running v4.41 and have been regularly experiencing an error message when trying to send or receive mail. The message "POP3 Network or Protocol Error - A network error occurred during connection to the host", and also "3: Socket failed, 277A".This usually happens about twice a day, and I always have to close Pegasus Mail and reload the program, and then it is OK.&nbsp; I should add here that other internet services are available when this happens, but Pegasus just will not send or receive until I reload. &nbsp;Looking at other postings, I gather that this is not a Pegasus Mail issue as such, but I don't know what the code "277A" is indicating - and therefore am at a loss to know how to resolve this?&nbsp;&nbsp;Thanks,&nbsp;David&nbsp;&nbsp;

Thomas R. Stephenson

posted Oct 24 '07 at 11:36 pm

[quote user="Ambassador"]

Looking at other postings, I gather that this is not a Pegasus Mail issue as such, but I don't know what the code "277A" is indicating - and therefore am at a loss to know how to resolve this?

Thanks,

David

[/quote]

Don't know specifically what this error code is either but these are generally TCP/IP timeout type errors. Try increasing the TCP/IP timeout in the POP3/SMTP setup to around 180 seconds and see if this fixes the problem.

[quote user="Ambassador"]Hi I am running v4.41 and have been regularly experiencing an error message when trying to send or receive mail. The message "POP3 Network or Protocol Error - A network error occurred during connection to the host", and also "3: Socket failed, 277A".This usually happens about twice a day, and I always have to close Pegasus Mail and reload the program, and then it is OK.&nbsp; I should add here that other internet services are available when this happens, but Pegasus just will not send or receive until I reload. &nbsp;Looking at other postings, I gather that this is not a Pegasus Mail issue as such, but I don't know what the code "277A" is indicating - and therefore am at a loss to know how to resolve this?&nbsp;&nbsp;Thanks,&nbsp;David&nbsp;&nbsp;[/quote]&nbsp;Don't know specifically what this error code is either but these are generally TCP/IP timeout type errors.&nbsp; Try increasing the TCP/IP timeout in the POP3/SMTP setup to around 180 seconds and see if this fixes the problem.&nbsp;

Ambassador

posted Oct 25 '07 at 2:45 am

Hi Thomas

>Don't know specifically what this error code is either but these are generally TCP/IP timeout type errors. Try increasing the TCP/IP timeout in the POP3/SMTP setup to around 180 seconds and see if this fixes the problem.<

Tried that but I have just had the problem again (a few minutes ago). When this problem arises, and I click the globe icon (to get new mail), the error displays immediately - ie it does *not* wait for the 180 secs and then displays....

Any ideas?

David

Hi Thomas &nbsp;&gt;Don't know specifically what this error code is either but these are generally TCP/IP timeout type errors.&nbsp; Try increasing the TCP/IP timeout in the POP3/SMTP setup to around 180 seconds and see if this fixes the problem.&lt; Tried that but I have just had the problem again (a few minutes ago).&nbsp;When this problem arises, and&nbsp; I click the globe icon (to get new mail), the error displays immediately - ie it does *not* wait for the 180 secs and then displays.... Any ideas? &nbsp; David &nbsp;

Thomas R. Stephenson

posted Oct 25 '07 at 4:16 pm

[quote user="Ambassador"]

Hi Thomas

Any ideas?

David

[/quote]

Yes, WinPMail gets an answer from the winsock that it's broken. The why is more of a problem. For some reason WinPMail is setting there with a dead winsock connection and that's a problem at a much lower level than WinPMail works. Is there some sort of proxy working between WinPMail and the outside world?

[quote user="Ambassador"]Hi Thomas &nbsp;&gt;Don't know specifically what this error code is either but these are generally TCP/IP timeout type errors.&nbsp; Try increasing the TCP/IP timeout in the POP3/SMTP setup to around 180 seconds and see if this fixes the problem.&lt; Tried that but I have just had the problem again (a few minutes ago).&nbsp;When this problem arises, and&nbsp; I click the globe icon (to get new mail), the error displays immediately - ie it does *not* wait for the 180 secs and then displays.... Any ideas? &nbsp; David &nbsp;[/quote]&nbsp;Yes, WinPMail gets an answer from the winsock that it's broken.&nbsp; The why is more of a problem.&nbsp; For some reason WinPMail is setting there with a dead winsock connection and that's a problem at a much lower level than WinPMail works.&nbsp; Is there some sort of proxy working between WinPMail and the outside world?&nbsp;

Ambassador

posted Oct 25 '07 at 4:36 pm

Hi again

>Yes, WinPMail gets an answer from the winsock that it's broken. The why is more of a problem. For some reason WinPMail is setting there with a dead winsock connection and that's a problem at a much lower level than WinPMail works. Is there some sort of proxy working between WinPMail and the outside world?<

Not sure how I would know this? Basically, all other services to the internet remain OK when this issue arises (eg Browsing, Napster, Cute FTP) - it is only Pegasus that won't connect until the program is shut down and reloaded. We are using ADSL with a Belkin router (does up to 4 wireless connections), and this has been in place for years (unalterered). I am using CA Security Suite Firewall, but again I can't see why that should be an issue either..

Where do I look and how do I check for any proxy settings, and is there any list that explains what code 277A actually is?

Thanks again, David

Hi again &nbsp;&gt;Yes, WinPMail gets an answer from the winsock that it's broken.&nbsp; The why is more of a problem.&nbsp; For some reason WinPMail is setting there with a dead winsock connection and that's a problem at a much lower level than WinPMail works.&nbsp; Is there some sort of proxy working between WinPMail and the outside world?&lt; Not sure how I would know this? Basically, all other services to the internet remain OK when this issue arises (eg Browsing, Napster, Cute FTP) - it is only Pegasus that won't connect until the program is shut down and reloaded. We are using ADSL with a Belkin router (does up to 4 wireless connections), and this has been in place for years (unalterered). I am using CA Security Suite Firewall, but again I can't see why that should be an issue either.. Where do I look and how do I check for any proxy settings, and is there any list that explains what code 277A actually is? &nbsp;Thanks again,&nbsp; David&nbsp; &nbsp;

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history