Community Discussions and Support
Pegasus Mail and Verizon FIOS

^^^^  Like he said!

 Just found and quickly solved a connection issue to my host provider's servers. All it took was an upgrade to version 4.70. So I made a donation to help fund ongoing development, and I encourage other users to do the same!

<p>^^^^  Like he said!</p><p> Just found and quickly solved a connection issue to my host provider's servers. All it took was an upgrade to version 4.70. So I made a donation to help fund ongoing development, and I encourage other users to do the same! </p>

Something odd has happened... Beginning last night, I'm unable to send or receive email through Verizon FIOS with Pegasus 4.63 on any of the computers on my home network. When I try, I immediately get the very uninformative error message:

 http://rednoise.vacau.com/temp/Pmail_error1.png

"SMTP Network of Protocol Error sending mail. An error has occurred during and SMTP mail transaction. The details of the error are show below, and if one is available, a trace showing the communication between Pegasus Mail and the server appears at the foot of the window.

"Description of error: A network error occurred during the connect to the host.

"Trace showing end of transaction: <<No trace information is available>>"

I'm still able to send/receive mail to other hosts (Gmail, Yahoo, etc.) with Pegasus. I'm still able to send/receive mail to Verizon with Outlook 2003, Outlook Express, and Thunderbird.

My POP3 settings are Port 995 via direct SSL connect. SMTP are Port 465/SSL. These are the same settings I use with Outlook/OE/Tbird.

I've tried disabling Windows XP's firewall, disabling my AV (Avira Free), enabling the "Disable certificate validation" option in Pegasus.
I turned on the "Keep a log of messages sent (in SYSLOG.PM file)" option, but no such log is created. I've rebooted the computer.

I made no changes in Pmail that I'm aware of. I made no changes in Pmail that I'm aware of. It seems to me that Verizon made some change on their end last night that doesn't agree with Pegasus, but which the other programs find acceptable. I have a suspicion that it has something to do with SSL, but without a meaningful error message, I'm at a loss as to how to troubleshoot this. Does anyone have any ideas or suggestions?


&lt;p&gt;Something odd has happened... Beginning last night, I&#039;m unable to send or receive email through Verizon FIOS with Pegasus 4.63 on any of the computers on my home network. When I try, I immediately get the very uninformative error message: &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;a href=&quot;http://rednoise.vacau.com/temp/Pmail_error1.png&quot; title=&quot;http://rednoise.vacau.com/temp/Pmail_error1.png&quot; target=&quot;_blank&quot; mce_href=&quot;http://rednoise.vacau.com/temp/Pmail_error1.png&quot;&gt;http://rednoise.vacau.com/temp/Pmail_error1.png&lt;/a&gt; &quot;SMTP Network of Protocol Error sending mail. An error has occurred during and SMTP mail transaction. The details of the error are show below, and if one is available, a trace showing the communication between Pegasus Mail and the server appears at the foot of the window. &quot;Description of error: A network error occurred during the connect to the host. &quot;Trace showing end of transaction: &amp;lt;&amp;lt;No trace information is available&amp;gt;&amp;gt;&quot; I&#039;m still able to send/receive mail to other hosts (Gmail, Yahoo, etc.) with Pegasus. I&#039;m still able to send/receive mail to Verizon with Outlook 2003, Outlook Express, and Thunderbird. My POP3 settings are Port 995 via direct SSL connect. SMTP are Port 465/SSL. These are the same settings I use with Outlook/OE/Tbird. I&#039;ve tried disabling Windows XP&#039;s firewall, disabling my AV (Avira Free), enabling the &quot;Disable certificate validation&quot; option in Pegasus. I turned on the &quot;Keep a log of messages sent (in SYSLOG.PM file)&quot; option, but no such log is created. I&#039;ve rebooted the computer. I made no changes in Pmail that I&#039;m aware of. I made no changes in Pmail that I&#039;m aware of. It seems to me that Verizon made some change on their end last night that doesn&#039;t agree with Pegasus, but which the other programs find acceptable. I have a suspicion that it has something to do with SSL, but without a meaningful error message, I&#039;m at a loss as to how to troubleshoot this. Does anyone have any ideas or suggestions? &lt;/p&gt;

This is the Url that lists general setup for email:

http://www22.verizon.com/Support/Residential/Internet/highspeed/email/setup+and+use/questionsone/86782.htm 

Does your ISP send/receive definition match this?

Martin 

&lt;p&gt;This is the Url that lists general setup for email:&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://www22.verizon.com/Support/Residential/Internet/highspeed/email/setup+and+use/questionsone/86782.htm&quot;&gt;http://www22.verizon.com/Support/Residential/Internet/highspeed/email/setup+and+use/questionsone/86782.htm&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Does your ISP send/receive definition match this?&lt;/p&gt;&lt;p&gt;Martin&amp;nbsp;&lt;/p&gt;

Yes, it does. And it's been working just fine for the past 2 years, and I've not made any changes.

 

I asked this question on the PMWIN list, and got one response that they, too, are having a similar problem. It's very curious that the problem only seems to be between Pegasus and Verizon. All other mail hosts still work with Pegasus, and all other email programs still work with Verizon. How could this be??

 


&lt;p&gt;Yes, it does. And it&#039;s been working just fine for the past 2 years, and I&#039;ve not made any changes.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I asked this question on the PMWIN list, and got one response that they, too, are having a similar problem. It&#039;s very curious that the problem only seems to be between Pegasus and Verizon. All other mail hosts still work with Pegasus, and all other email programs still work with Verizon. How could this be??&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt; &lt;/p&gt;

I'm having the exact same problem, and receiving the exact same message. I'm glad to know it isn't just me.

Like the original poster, everything was working fine as of last night. Then, this morning, for no discernible reason, I can't connect to Verizon through Pegasus. Verizon can't help, as they don't support Pegasus (at least that's what they told me). I've confirmed all my settings, and they all seem to be correct.

Something must have happened last night. Verizon swears it was nothing on their end. I'd like to get this resolved as soon as possible, so I'm hoping that someone here can offer some insight/help.

 Thanks!

 John 

&lt;p&gt;I&#039;m having the exact same problem, and receiving the exact same message. I&#039;m glad to know it isn&#039;t just me.&lt;/p&gt;&lt;p&gt;Like the original poster, everything was working fine as of last night. Then, this morning, for no discernible reason, I can&#039;t connect to Verizon through Pegasus. Verizon can&#039;t help, as they don&#039;t support Pegasus (at least that&#039;s what they told me). I&#039;ve confirmed all my settings, and they all seem to be correct.&lt;/p&gt;&lt;p&gt;Something must have happened last night. Verizon swears it was nothing on their end. I&#039;d like to get this resolved as soon as possible, so I&#039;m hoping that someone here can offer some insight/help.&lt;/p&gt;&lt;p&gt;&amp;nbsp;Thanks!&lt;/p&gt;&lt;p&gt;&amp;nbsp;John&amp;nbsp;&lt;/p&gt;

Good Evening Group:

I thought that I was losing my mind... it is somewhat reassuring to now know that we are not alone.

Having said that, I agree with all the other assertions that all setting for both SMTP and POP are correct and unchanged. I too have approached this rather systematically to no avail. Verizon Tech Support, Firewall, Anti Virus, System Restore. I even reloaded the WinSock in the hope to make things right.

I sincerely hope that a cure is forth comming in that I've come to rely on Pegasus in my day to day business activities. The old cliche "You don't know what you have, until it is gone."

Any and all constructive comments welcome.

All The Best

TEGSR 

 

. 

 

 

 

 

 

&lt;p&gt;Good Evening Group:&lt;/p&gt;&lt;p&gt;I thought that I was losing my mind... it is somewhat reassuring to now know that we are not alone.&lt;/p&gt;&lt;p&gt;Having&amp;nbsp;said that, I agree with all the other assertions that all setting for both SMTP and POP are correct and unchanged. I too have approached this rather systematically to no avail. Verizon Tech Support, Firewall, Anti Virus, System Restore. I even reloaded the WinSock in the hope to make things right.&lt;/p&gt;&lt;p&gt;I sincerely hope that a cure is forth comming in that I&#039;ve come to rely on Pegasus in my day to day business activities. The old cliche &quot;You don&#039;t know what you have, until it is gone.&quot;&lt;/p&gt;&lt;p&gt;Any and all constructive comments welcome.&lt;/p&gt;&lt;p&gt;All The Best&lt;/p&gt;&lt;p&gt;TEGSR&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;.&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;

I have the SAME issue that started last night.

I have always had the correct settings via SSL and they have worked on two computers w/P-Mail until last night.

I was able to setup Vista Winmail and Outlook 2003 using the same settings and they work.  Verizon flipped a switch where TCP ports 995 with SSL and 465 with SSL for P-Mail no longer work.

I have reverted to: 

incoming.verizon.net:110  via "STLS Command"

outgoing.verizon.net:25 via "STARTTLS"

&lt;p&gt;I have the &lt;i&gt;&lt;b&gt;SAME&lt;/b&gt;&lt;/i&gt; issue that started last night.&lt;/p&gt;&lt;p&gt;I have always had the correct settings via SSL and they have worked on two computers w/P-Mail until last night.&lt;/p&gt;&lt;p&gt;I was able to setup Vista Winmail and Outlook 2003 using the same settings and they work.&amp;nbsp; Verizon flipped a switch where TCP ports 995 with SSL and 465 with SSL for P-Mail no longer work. &lt;/p&gt;&lt;p&gt;I have reverted to:&amp;nbsp; &lt;/p&gt;&lt;p&gt;incoming.verizon.net:110&amp;nbsp; via &quot;STLS Command&quot; &lt;/p&gt;&lt;p&gt;outgoing.verizon.net:25 via &quot;STARTTLS&quot; &lt;/p&gt;

I'm also discussing this issue on the PMWIN list, and I was advised to capture a session log Below is the result. Usually I would be careful to obscure my password, but apparently the session never got to that point, and the connection failed during the SSL negotiation.

I'm not quite sure what this signifies, but someone on the list suggested that it means there is an incompatibility issue or problem with PMail's SSL libraries. Obviously, Verizon changed something yesterday on their end that exposed Pegasus' issue. I don't expect that Verizon will ever let us mere users speak to anyone there who will know about or admit to those changes, much less change them back. So... that raises the question: can I continue to use Pegasus Mail with Verizon's mail host. I sure hope so, because I've been a user for decades and I'd hate to be forced to give it up on account of my ISP.

 

==========================

 

--- Tue, 16 Oct 2012 15:39:51 ---


Connect to 'incoming.verizon.net' port 995, timeout 30.


15:39:51.015 [*] Connection established to 206.46.232.10


15:39:52.218 22: Error -32 activating SSL session (locus 6014, type

4,

'Bad server key agreement parameter

signature\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC')


15:39:52.218 --- Connection closed normally at Tue, 16 Oct 2012

15:39:52. ---\0A\0A


 


&lt;p&gt;I&#039;m also discussing this issue on the PMWIN list, and I was advised to capture a session log Below is the result. Usually I would be careful to obscure my password, but apparently the session never got to that point, and the connection failed during the SSL negotiation.&lt;/p&gt;&lt;p&gt;I&#039;m not quite sure what this signifies, but someone on the list suggested that it means there is an incompatibility issue or problem with PMail&#039;s SSL libraries. Obviously, Verizon changed something yesterday on their end that exposed Pegasus&#039; issue. I don&#039;t expect that Verizon will ever let us mere users speak to anyone there who will know about or admit to those changes, much less change them back. So... that raises the question: can I continue to use Pegasus Mail with Verizon&#039;s mail host. I sure hope so, because I&#039;ve been a user for decades and I&#039;d hate to be forced to give it up on account of my ISP.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;==========================&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;--- Tue, 16 Oct 2012 15:39:51 --- Connect to &#039;incoming.verizon.net&#039; port 995, timeout 30. 15:39:51.015 [*] Connection established to 206.46.232.10 15:39:52.218 22: Error -32 activating SSL session (locus 6014, type 4, &#039;Bad server key agreement parameter signature\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC&#039;) 15:39:52.218 --- Connection closed normally at Tue, 16 Oct 2012 15:39:52. ---\0A\0A &amp;nbsp; &lt;/p&gt;

Hi David:

 "I have reverted to: 

incoming.verizon.net:110  via "STLS Command"

outgoing.verizon.net:25 via "STARTTLS" 

 Are you now able to access both the SMTP and the POP servers?.

Too tired to boot the desktop tonight, I'll check, using your suggested port changes, first thing in the morning.

Thanks

 

TEGSR 

 

 

&lt;p&gt;Hi David:&lt;/p&gt;&lt;p&gt;&amp;nbsp;&quot;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: Tahoma, Arial, Helvetica; background-color: rgb(221, 221, 221); &quot;&gt;I have reverted to:&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: Tahoma, Arial, Helvetica; background-color: rgb(221, 221, 221); &quot;&gt;&lt;p&gt;incoming.verizon.net:110&amp;nbsp; via &quot;STLS Command&quot;&lt;/p&gt;&lt;/span&gt;&lt;p&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: Tahoma, Arial, Helvetica; background-color: rgb(221, 221, 221); &quot;&gt;outgoing.verizon.net:25 via &quot;STARTTLS&quot;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;Are you now able to access both the SMTP and the POP servers?.&lt;/p&gt;&lt;p&gt;Too tired to boot the desktop tonight, I&#039;ll check, using your suggested port changes, first thing in the morning.&lt;/p&gt;&lt;p&gt;Thanks&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;TEGSR&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;

[quote user="sceneryguru"]outgoing.verizon.net:25 via "STARTTLS" 

 Are you now able to access both the SMTP and the POP servers?.[/quote]

 Yes.  That's how I got the Forum email indicating your reply post.

 

[quote user=&quot;sceneryguru&quot;]&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: Tahoma, Arial, Helvetica; background-color: rgb(221, 221, 221); &quot;&gt;outgoing.verizon.net:25 via &quot;STARTTLS&quot;&amp;nbsp;&lt;/span&gt;&lt;p&gt;&amp;nbsp;Are you now able to access both the SMTP and the POP servers?.[/quote]&lt;/p&gt;&lt;p&gt;&amp;nbsp;Yes.&amp;nbsp; That&#039;s how I got the Forum email indicating your reply post.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;

[quote user="rednoise"]

I'm also discussing this issue on the PMWIN list, and I was advised to capture a session log Below is the result. Usually I would be careful to obscure my password, but apparently the session never got to that point, and the connection failed during the SSL negotiation.

[/quote]

 I ran Wireshark and captured packets and saw the email server communicate with my PC using the TLSv1 protocol "Client Hello" so I changed over to TLS instead of SSL and I am up an running.

 I am creating a post on the Verizon forums.  However, I have very low expectations and I do NOT expect anything to come from it

[quote user=&quot;rednoise&quot;]&lt;p&gt;I&#039;m also discussing this issue on the PMWIN list, and I was advised to capture a session log Below is the result. Usually I would be careful to obscure my password, but apparently the session never got to that point, and the connection failed during the SSL negotiation.&lt;/p&gt;&lt;p&gt;[/quote]&lt;/p&gt;&lt;p&gt;&amp;nbsp;I ran Wireshark and captured packets and saw the email server communicate with my PC using the TLSv1 protocol &quot;Client Hello&quot; so I changed over to TLS instead of SSL and I am up an running. &lt;/p&gt;&lt;p&gt;&amp;nbsp;I am creating a post on the Verizon forums.&amp;nbsp; However, I have very low expectations and I do NOT expect anything to come from it &lt;/p&gt;

[quote user="David H. Lipman"]

 I ran Wireshark and captured packets and saw the email server communicate with my PC using the TLSv1 protocol "Client Hello" so I changed over to TLS instead SSL and I am up an running.

 I am creating a post on the Verizon forums.  However, I have very low expectations and I do NOT expect anything to come from it

[/quote]

That works! Whew!

I'm worried, though, that this will only be a short-term solution. I was originally forced several months ago to use ports 995 and 465 when Verizon blocked my use of 110 and 25. I see that those ports are available to me again, but they're not mentioned anywhere on their official settings page. They seem to be deprecated, and maybe they'll go away again.

 Anyway, I'm up and running again, for the moment at least. Thank you.

[quote user=&quot;David H. Lipman&quot;]&lt;p&gt;&amp;nbsp;I ran Wireshark and captured packets and saw the email server communicate with my PC using the TLSv1 protocol &quot;Client Hello&quot; so I changed over to TLS instead SSL and I am up an running. &lt;/p&gt;&lt;p&gt;&amp;nbsp;I am creating a post on the Verizon forums.&amp;nbsp; However, I have very low expectations and I do NOT expect anything to come from it &lt;/p&gt;&lt;p&gt;[/quote]&lt;/p&gt;&lt;p&gt;That works! Whew!&lt;/p&gt;&lt;p&gt;I&#039;m worried, though, that this will only be a short-term solution. I was originally forced several months ago to use ports 995 and 465 when Verizon blocked my use of 110 and 25. I see that those ports are available to me again, but they&#039;re not mentioned anywhere on their official settings page. They seem to be deprecated, and maybe they&#039;ll go away again.&lt;/p&gt;&lt;p&gt;&amp;nbsp;Anyway, I&#039;m up and running again, for the moment at least. Thank you. &lt;/p&gt;

Yes, me too. 

That's why I did NOT post that information on the Verizon server. 

Just that ALL Verizon subscribers using P-Mail to access the Verizon email server are having this problem.

&lt;p&gt;&lt;i&gt;&lt;b&gt;Yes, me too.&amp;nbsp; &lt;/b&gt;&lt;/i&gt;&lt;/p&gt;&lt;p&gt;That&#039;s why I did NOT post that information on the Verizon server.&amp;nbsp;&lt;/p&gt;&lt;p&gt; Just that ALL Verizon subscribers using P-Mail to access the Verizon email server are having this problem. &lt;/p&gt;

I'm glad it wasn't just me. I went back to the old settings and it's working now. I suppose Verizon will shut them off at some point. I'll share if I find anything useful out (but I doubt it, just like everyone else).

I&#039;m glad it wasn&#039;t just me. I went back to the old settings and it&#039;s working now. I suppose Verizon will shut them off at some point. I&#039;ll share if I find anything useful out (but I doubt it, just like everyone else).

Good Morning Group:

Just a brief update. I changed back to the "older" port setting of 110 & 25 respectively. And I'm back in business, literally!.

Thanks folks, I certainly appreciate the comments and end results.  

TEGSR 

 

&lt;p&gt;Good Morning Group:&lt;/p&gt;&lt;p&gt;Just a brief update. I changed back to the &quot;older&quot; port setting of 110 &amp;amp; 25 respectively. And I&#039;m back in business, literally!.&lt;/p&gt;&lt;p&gt;Thanks folks, I certainly appreciate the comments and end results. &amp;nbsp;&lt;/p&gt;&lt;p&gt;TEGSR&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;

It was suggested to me that using port 587 for SMTP is more secure than port 25, and that Verizon is more likely to close off port 25 as it is commonly attacked by outsiders trying to exploit their mail system. And, in fact, they did close it off for me many months ago, which is why I was surprised to find it open to me again. But for now both 587 and 25 work, at least when I'm at home, on Verizon's internet connection.

 I'm wondering, though, if port 587 and/or 25 will work when I'm traveling, that is, when I'm trying to send mail through them while outside their network. Has anybody tried this yet?

 I'm also wondering where the problem lies, where to point the finger, and which side to look to for a permanent fix. Is Verizon's change faulty or does it conflict with established specs? Or is Pegasus's SSL faulty? The fact that Pegasus seems to work fine for all other mail systems (as far as I know) implies the former. The fact that only Pegasus (as far as I know) seems to have trouble with Verizon implies the latter.

Eventually I'd like Pegasus to use SSL to talk to Verizon again.

&lt;p&gt;It was suggested to me that using port 587 for SMTP is more secure than port 25, and that Verizon is more likely to close off port 25 as it is commonly attacked by outsiders trying to exploit their mail system. And, in fact, they did close it off for me many months ago, which is why I was surprised to find it open to me again. But for now both 587 and 25 work, at least when I&#039;m at home, on Verizon&#039;s internet connection.&lt;/p&gt;&lt;p&gt;&amp;nbsp;I&#039;m wondering, though, if port 587 and/or 25 will work when I&#039;m traveling, that is, when I&#039;m trying to send mail through them while outside their network. Has anybody tried this yet?&lt;/p&gt;&lt;p&gt;&amp;nbsp;I&#039;m also wondering where the problem lies, where to point the finger, and which side to look to for a permanent fix. Is Verizon&#039;s change faulty or does it conflict with established specs? Or is Pegasus&#039;s SSL faulty? The fact that Pegasus seems to work fine for all other mail systems (as far as I know) implies the former. The fact that only Pegasus (as far as I know) seems to have trouble with Verizon implies the latter.&lt;/p&gt;&lt;p&gt;Eventually I&#039;d like Pegasus to use SSL to talk to Verizon again. &lt;/p&gt;

I am using Verizon DSL (not FIOS) and my problem with outgoing mail started on 16 Oct. like everyone else.  After reading this thread I made 1 change, and my outgoing queue just emptied.  I switched from SSL to STARTTLS.  Thanks guys!!!!

<object style="position:absolute;z-index:1000" type="application/x-dgnria" id="plugin0" height="0" width="0"><param value="ff-tab-1" name="tabId"><param value="21" name="counter"></object>
I am using Verizon DSL (not FIOS) and my problem with outgoing mail started on 16 Oct. like everyone else.&amp;nbsp; After reading this thread I made 1 change, and my outgoing queue just emptied.&amp;nbsp; I switched from SSL to STARTTLS.&amp;nbsp; Thanks guys!!!! &lt;div nuan_tabactive=&quot;true&quot; id=&quot;nuan_ria_plugin&quot;&gt;&lt;object style=&quot;position:absolute;z-index:1000&quot; type=&quot;application/x-dgnria&quot; id=&quot;plugin0&quot; height=&quot;0&quot; width=&quot;0&quot;&gt;&lt;param value=&quot;ff-tab-1&quot; name=&quot;tabId&quot;&gt;&lt;param value=&quot;21&quot; name=&quot;counter&quot;&gt;&lt;/object&gt;&lt;/div&gt;

Honestly, I'm wondering if it might not be time to switch to Thunderbird. I've been using Pegasus for more than 15 years, but I don't need this kind of aggravation.

Honestly, I&#039;m wondering if it might not be time to switch to Thunderbird. I&#039;ve been using Pegasus for more than 15 years, but I don&#039;t need this kind of aggravation.

Even if there is a "bug" in P-Mail I wouldn't blame it.  I blame Verizon for doing something non-standard that is causing a problem with P-Mail.  It's not like P-Mail is having problems with other email providers.

We have a workaround so I don't see a reason to switch to T-Bird or other email client.  I have patience ( I can't believe I'm saying that ) and I can wait out a formal solution to be able to use SSL again.

 

&lt;p&gt;Even if there is a &quot;bug&quot; in P-Mail I wouldn&#039;t blame it.&amp;nbsp; I blame Verizon for doing something non-standard that is causing a problem with P-Mail.&amp;nbsp; It&#039;s not like P-Mail is having problems with other email providers. &lt;/p&gt;&lt;p&gt;We have a workaround so I don&#039;t see a reason to switch to T-Bird or other email client.&amp;nbsp; I have patience (&lt;i&gt; I can&#039;t believe I&#039;m saying that&lt;/i&gt; ) and I can wait out a formal solution to be able to use SSL again.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;

Like everyone else (apparently) I started having the 'no trace' reports on the 16th... 

However, I have not seen anyone else mention that my condition was INTERMITTENT ...
I'd get four or five 'no trace' reports on POP3 and then it would connect and download...

Only today, Oct. 18th, did I start getting 'no trace' on the SMTP ... and that also
was intermittent...  in fact, I had six outgoing messages pending -- it connected to
'outgoing' and sent four of them, then I got the 'no trace' message and could not
send the remaining two messages.

I 'googled' the 'no trace information' and was directed right to this thread! 

Thanks to all the helpful people on here, I changed smtp from 465 to 587:never
and sending seems to be fine; I changed pop3 from 995:ssl to 110:never and 
it seems to be also working now.

This seems to be a giant step AWAY from security though.   :(

 

&lt;p&gt;Like everyone else (apparently) I started having the &#039;no trace&#039; reports on the 16th...&amp;nbsp;&lt;/p&gt;&lt;p&gt;However, I have not seen anyone else mention that my condition was INTERMITTENT ... I&#039;d get four or five &#039;no trace&#039; reports on POP3 and then it would connect and download... &lt;/p&gt;&lt;p&gt;Only today, Oct. 18th, did I start getting &#039;no trace&#039; on the SMTP ... and that also was intermittent... &amp;nbsp;in fact, I had six outgoing messages pending -- it connected to &#039;outgoing&#039; and sent four of them, then I got the &#039;no trace&#039; message and could not send the remaining two messages.&lt;/p&gt;&lt;p&gt;I &#039;googled&#039; the &#039;no trace information&#039; and was directed right to this thread!&amp;nbsp;&lt;/p&gt;&lt;p&gt;Thanks to all the helpful people on here, I changed smtp from 465 to 587:never and sending seems to be fine; I changed pop3 from 995:ssl to 110:never and&amp;nbsp; it seems to be also working now.&lt;/p&gt;&lt;p&gt;This seems to be a giant step AWAY from security though. &amp;nbsp; :(&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Cancel
Delete
Pending draft ... Click to resume editing
Discard draft