[quote user="Brian Fluet"]
Tell me, is the setting now enabled or disabled.
[/quote]
The box was checked, now unchecked.
<!--[if gte mso 9]><xml> </p><p> <w:WordDocument> </p><p> <w:View>Normal</w:View> </p><p> <w:Zoom>0</w:Zoom> </p><p> <w:PunctuationKerning/> </p><p> <w:ValidateAgainstSchemas/> </p><p> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> </p><p> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> </p><p> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> </p><p> <w:Compatibility> </p><p> <w:BreakWrappedTables/> </p><p> <w:SnapToGridInCell/> </p><p> <w:WrapTextWithPunct/> </p><p> <w:UseAsianBreakRules/> </p><p> <w:DontGrowAutofit/> </p><p> </w:Compatibility> </p><p> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </p><p> </w:WordDocument> </p><p></xml><![endif]--><!--[if gte mso 9]><xml> </p><p> <w:LatentStyles DefLockedState="false" LatentStyleCount="156"> </p><p> </w:LatentStyles> </p><p></xml><![endif]--><!--[if gte mso 10]> </p><p><style> </p><p> /* Style Definitions */ </p><p> table.MsoNormalTable </p><p> {mso-style-name:"Table Normal"; </p><p> mso-tstyle-rowband-size:0; </p><p> mso-tstyle-colband-size:0; </p><p> mso-style-noshow:yes; </p><p> mso-style-parent:""; </p><p> mso-padding-alt:0in 5.4pt 0in 5.4pt; </p><p> mso-para-margin:0in; </p><p> mso-para-margin-bottom:.0001pt; </p><p> mso-pagination:widow-orphan; </p><p> font-size:10.0pt; </p><p> font-family:"Times New Roman"; </p><p> mso-ansi-language:#0400; </p><p> mso-fareast-language:#0400; </p><p> mso-bidi-language:#0400;} </p><p></style> </p><p><![endif]-->
Recently been having problems with my isp Verizon & Pegasus. Been having to go to its webmail page to read the mailas selective download(s) not working or the check host option. Sometimes I will have say 10 messages and 8 will show breing downloaded but the completion process never takes place and I will received following messages (which I apologize for length) Seems like some type of timing problem
>> 0155 +OK Messaging
Multiplexor (Sun Java(tm) System Messaging Server 6.3-11.01 (built Feb 12
2010)) <398dd86b159feb72bd2d2de62c5e1d03@vms171051.mailsrvcs.net>
<< 0015 USER (I have
deleted for this forum it is OK)
>> 0041 +OK password
required for user (I have deleted for forum it is OK)
<< 0021 PASS
XXXXXXXXXXXXXX
>> 0020 +OK Maildrop
ready
<< 0006 STAT
>> 0015 +OK 8 1067047
<< 0006 LIST
>> 0026 +OK scan listing
follows
<< 0008 RETR 1
>> 0019 +OK 163814
octets
<< 0008 DELE 1
>> 0021 +OK message
deleted
<< 0008 RETR 2
>> 0018 +OK 15599 octets
<< 0008 DELE 2
>> 0021 +OK message
deleted
<< 0008 RETR 3
>> 0019 +OK 771328
octets
<< 0021 PASS
XXXXXXXXXXXXXX
>> 0020 +OK Maildrop
ready
<< 0006 STAT
>> 0015 +OK 4 5239877
<< 0006 LIST
>> 0026 +OK scan listing
follows
<< 0008 UIDL 1
>> 0024 +OK 1
30569-1251803036
<< 0009 TOP 1 1
8: Socket read timeout.
15: Peer connect failure (the
host has refused the connection).
> 8: Socket read timeout.
> 15: Peer connect failure (the host has refused the connection).
First of all increase the timeout setting in Tools | Internet options | (Receiving)POP3 to something like 180 (or even 300) seconds to see if this solves your problem.
If it does not then you may have a packet fragmentation problem. 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.
I think it may be working since I increased the timeout setting as you suggested.
I've also copied the rest of your suggestion for future use in case I may have to use
Thanks Again for the help. I see you have a new avatar. Looks like a nice truck
I have benefitted greatly form help I have received on this forum in the past. This is a new problem that just started in the last few hours today: Verizon (DSL connection) is not accepting any mail I send; the result is this report:
[*] Connection established to 206.46.232.12
>> 0120 220 vms173015pub.verizon.net -- Server ESMTP (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009))
<< 0021 EHLO [192.168.1.43]
>> 0030 250-vms173015pub.verizon.net
>> 0014 250-8BITMIME
>> 0016 250-PIPELINING
>> 0014 250-CHUNKING
>> 0009 250-DSN
>> 0025 250-ENHANCEDSTATUSCODES
>> 0010 250-HELP
>> 0044 250-XLOOP 772F06AF824D7FA46E31B4F4EBC1DD16
>> 0042 250-AUTH DIGEST-MD5 PLAIN LOGIN CRAM-MD5
>> 0022 250-AUTH=LOGIN PLAIN
>> 0010 250-ETRN
>> 0019 250-NO-SOLICITING
>> 0019 250 SIZE 20971520
<< 0015 AUTH CRAM-MD5
>> 0046 334 PDI1ODI0OTEzNTAuNzc3Njc1MUB2bXMxNzMwMTU+
<< 0066 ZW5nbGlzaGludHJveSBjYjY0OGI5ODhmZGJmNzY5MGQ3YzI5OGI3YzA5MWU5YQ==
>> 0066 500 5.7.0 Unknown AUTH error -1 (Internal authentication error).
It appears to be saying that the authentication is missing or incorrect. I have not made any changes to my settings in a very long time; things have been working smoothly for a few years since the last problem with Pegasus & Verizon.
Jeff English
Troy, New York
[quote user="english in troy"]I have benefitted greatly form help I have received on this forum in the past. This is a new problem that just started in the last few hours today: Verizon (DSL connection) is not accepting any mail I send; the result is this report:[/quote]
Try after enabling Only use SSLv3 ... on the respective Security pages of your connection settings. See here for a screenshot. Or you may need to disable AUTH CRAM-MD5 in your SMTP settings (at the bottom of the Security tab).
Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
To Jerry Wise,
Received your message off-forum; thank you for replying. I examined the line in question, and I don't see my password in there so I think I'm OK there.
You have exposed my lack of diligence by asking if I'm using v4.70. The answer is, no, I'm still using v4.65.
I'm also still using port 25. This is because the last time Verizon gave notice to change ports, I found that the alternatives did not work but port 25 continued to work for me.
Since it now appears that I need to get with the times, I will update to v4.70 and try ports 465 & 587 to see if that fixes things. I will report back either way.
Jeff
OK, regarding updating to v4.70, I looked at the downloads page and did not find anything newer than my v4.65. Am I looking in the wrong place?
I tried port 465, which did not solve the problem, but instead of the authentication error it merely timed out. On port 587 I got the same authentication error.
Thanks for the link. Now that I have v4.70 installed, the problem is the same: port 465 gets "socket read timeout" while ports 25 and 587 get "authentication error".
I recall in the past trying a longer timeout threshold, but even if that works I wouldn't be happy with a long delay when sending mail.
Michael,
Thank you for your suggestions, which I tried along with other suggestions by Mr. Jerry Wise without immediate success.
What got it working was when I changed the security setting from "Via STARTTLS" to "Via direct SSL connect"; these are settings which were under discussion a couple of years ago, and I had set it to "Via STARTTLS" at that time. I'm sure that this only worked after having updated to the current settings called for by Verizon.
So I'm up & running again. Thanks for your help & also for help from Mr. Wise.
Jeff
I don't know if 4.70 solves the SSL issues on Verizon, but Rednoise has found a program called "Stunnel" works on Verizon, described in this thread:
http://community.pmail.com/forums/post/39033.aspx (or just search "Stunnel" on the forum).
It is a straightforward install, with no Windows registry install (can transfer full file between computers, and it launches automatically from an icon (windows shortcut)). While a 2nd program is by definition clunky, Stunnel has the advantage of implementing SSL external to the email client (PMail).
The advantage of Stunnel, besides being a separate thread from the reader, is that it runs full SSL on Verizon.
Now, maybe someone can tell me how to configure Bouncebully to talk through Stunnel (which I think is just a matter of hacking the "conf" file but I hadn't gotten around to it). (:
Things have been going smoothly since last May, but today suddenly I am unable to download mail from Verizon. Here is the report log:
15:01:06.718: --- 25 Feb 2015, 15:01:06.718 ---
15:01:06.718: Connect to 'pop.verizon.net', timeout 90 seconds.
15:01:07.781: [!] OpenSSL reported errors during handshake - error queue follows:
15:01:07.781: [!] -------------------------------------------------------------------------
15:01:07.781: [!] error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
15:01:07.781: [!] -------------------------------------------------------------------------
This comes up immediately, not after 90 seconds of waiting. I have made no changes to my settings since last May.
I will be grateful if somebody can solve this.
Jeff
I forgot to mention that there is a similar problem sending mail; the log:
15:14:23.484: --- 25 Feb 2015, 15:14:23.484 ---
15:14:23.484: Connect to 'smtp.verizon.net', timeout 90 seconds.
15:14:24.578: [!] OpenSSL reported errors during handshake - error queue follows:
15:14:24.578: [!] -------------------------------------------------------------------------
15:14:24.578: [!] error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
15:14:24.578: [!] -------------------------------------------------------------------------
Jeff
Pegasus Mail versions prior to 4.70 do not support OpenSSL. Upgrade to 4.70.
If you are already running 4.70, go to the Security tab on your POP3 and
SMTP host configurations and reverse the setting of the "Use only SSLv3..." option (uncheck it if checked, check it if unchecked).
This problem is the result of the rollout by Verizon of OpenSSL on their servers. It was one of the reasons, if not the primary reason, for the release of 4.70.
[quote user="english in troy"]OK, that seems to have fixed things. I had already been using 4.70; did Verizon change something?[/quote]
Yes. Best I can tell from other posts on this issue, Verizon is rolling out OpenSSL to its servers and just got to the one you are accessing. The setting you changed enables the OpenSSL compatibility in Pegasus Mail. Tell me, is the setting now enabled or disabled. I ask because when 4.70 was first released there was some discussion about the wording of that setting being misleading and I have not yet figured out whether to recommend enabling it or disabling it.
