Community Discussions and Support
Verizon Mail - Can't send Mail

Just a quick update... my suspicions were correct in that my inability to send mail was a direct result of issues at AOL / Verizon. At this point things appear to be OK with an occasional hiccup.

 

Thanks

 

Tom G, Sr. 

<p>Just a quick update... my suspicions were correct in that my inability to send mail was a direct result of issues at AOL / Verizon. At this point things appear to be OK with an occasional hiccup.</p><p> </p><p>Thanks</p><p> </p><p>Tom G, Sr. </p>

Good Afternoon:

This AM when attempting to reply to a business e-mail I noticed that I couldn't send.

No problem receiving mail. No changes to any of the setting...

Was on the phone with AOL tech support, they were helpful but of no assistance.

I can't prove it but I firmly believe that the difficulty lies in the Verizon/AOL SMTP server. 

I use my Pegasus for business communications and have for years. I'm dead in the water... any constructive thoughts are gratefully accepted.

Thank you

Tom G, Sr. 

 

<p>Good Afternoon:</p><p><span style="font-size: 10pt;">This AM when attempting to reply to a business e-mail I noticed that I couldn't send.</span></p><p><span style="font-size: 10pt;">No problem receiving mail. No changes to any of the setting...</span></p><p><span style="font-size: 10pt;">Was on the phone with AOL tech support, they were helpful but of no assistance.</span></p><p>I can't prove it but I firmly believe that the difficulty lies in the Verizon/AOL SMTP server. </p><p>I use my Pegasus for business communications and have for years. I'm dead in the water... any constructive thoughts are gratefully accepted.</p><p>Thank you</p><p>Tom G, Sr. </p><p> </p>

In case this is relevant...

The following comment was recently posted in a discussion about an AOL login problem:

Apparently AOL has recently changed their logon to require the full name, e.g., "username@verizon.net"; not just "username"

You might want to search out Verizon's most current connection requirements to check for any other changes (ports,SSL/TLS settings).

Also, an internet session log may identify the point of failure.  Don't post a entire log though because it will contain credentials, possibly encrypted so as to be unrecognizable if you don't know what to look for, but it's easily decrypted.

<p>In case this is relevant... </p><p>The following comment was recently posted in a discussion about an AOL login problem:</p><blockquote><p>Apparently AOL has recently changed their logon to require the full name, e.g., "username@verizon.net"; not just "username"</p></blockquote><p>You might want to search out Verizon's most current connection requirements to check for any other changes (ports,SSL/TLS settings).</p><p>Also, an internet session log may identify the point of failure.  Don't post a entire log though because it will contain credentials, possibly encrypted so as to be unrecognizable if you don't know what to look for, but it's easily decrypted. </p>

The problems started February 14/15.  I initially opened a ticket with the LOUSY AOL Support on 2/16.

Oath is a subsidiary of Verizon but separate.  Oath is in the process of merging the email systems of AOL, Yahoo and Verizon.  In doing so they have fouled up the Verizon email services.

When I initially opened the ticket with AOL this is what I experienced and it was with AOL POP3...

When  pop.verizon.net  [ which is the published address to use ] is used and it resolves to;  global-jpop-aol.mail.gm0.yahoodns.net   POP does not work correctly.

When  pop.verizon.net  resolves to;   pop-verizonmail.egslb.aol.com   POP works as expected.

When the email client is hard coded for;   pop-verizonmail.egslb.aol.com   POP works properly


It is now March 5 and pop.verizon.net  resolves to;  global-jpop-aol.mail.gm0.yahoodns.net

[hr]

Now SMTP is also problematic.

Both;  smtp.verizon.net   and  outgoing.verizon.net  resolve to;  smtp-verizonmail.egslb.aol.com


HOWEVER, now smtp-verizonmail.egslb.aol.com is NOT configured properly for TLS/SSL

When  Verizon moved its email to AOL infrastructure we noted a similar issue.  rednoise is not online. Last active: 11-02-2015, 3:17

rednoise  came up with an eloquent solution using a SSL Proxy software called STunnel.

RE:  Re: Pegasus Mail and Verizon FIOS

The objective is to install STunnel as a NT Service [ "C:\Program Files\stunnel\bin\stunnel.exe" -install ]

and then to edit its configuration file for Verizon servers;  C:\Program Files\stunnel\config\stunnel.conf

and add...

[verizon-POP3-SSL]
; SSL connection to Verizon's POP3 server for Pegasus
client = yes
accept = 10995
connect = pop-verizonmail.egslb.aol.com:995

[verizon-smtp-SSL]
; SSL connection to Verizon's SMTP server for Pegasus
client = yes
accept = 10465
;connect = smtp.verizon.net:465
connect = smtp-verizonmail.egslb.aol.com:465

 STunnel will listen at Ports 10995 and 10465 on the local PC [ 127.0.0.1 ] and when it sees activity at these ports it makes the secure connection at AOL Email servers using the TCP ports they require  but uses STunnel to provide the secure connection.

 

In P-Mail go to;  Tools --> Internet Options --> Sending ( SMTP ) --> Add

Give it a name such as "Verizon STunnel Proxy" and setup like the below...

 


<p>The problems started February 14/15.  I initially opened a ticket with the <font color="#cc0000"><i><b>LOUSY</b></i></font> AOL Support on 2/16. </p><p>Oath is a subsidiary of Verizon but separate.  Oath is in the process of merging the email systems of AOL, Yahoo and Verizon.  In doing so they have fouled up the Verizon email services.</p><p>When I initially opened the ticket with AOL this is what I experienced and it was with AOL POP3... </p><p>When  <b>pop.verizon.ne</b>t  [ <i>which is the published address to use</i> ] is used and it resolves to;  <b>global-jpop-aol.mail.gm0.yahoodns.net</b>   POP does not work correctly.</p><p>When  <b>pop.verizon.ne</b>t  resolves to;   <b>pop-verizonmail.egslb.aol.com   </b>POP works as expected. When the email client is hard coded for;   <b>pop-verizonmail.egslb.aol.com   </b>POP works properly It is now March 5 and <b>pop.verizon.net</b>  resolves to;  <b>global-jpop-aol.mail.gm0.yahoodns.net</b> </p><p>[hr]</p><p>Now SMTP is also problematic.</p><p>Both;  <b>smtp.verizon.net</b>   and  <b>outgoing.verizon.ne</b>t  resolve to;  <b>smtp-verizonmail.egslb.aol.com</b> HOWEVER, now <b>smtp-verizonmail.egslb.aol.com</b> is NOT configured properly for [url=https://en.wikipedia.org/wiki/Transport_Layer_Security]TLS/SSL[/url]</p><p>When  Verizon moved its email to AOL infrastructure we noted a similar issue.  <img alt="rednoise is not online. Last active: 11-02-2015, 3:17" style="border-width:0px;" src="http://community.pmail.com/Themes/default/images/user_IsOffline.gif"> <a href="http://community.pmail.com/members/rednoise.aspx">rednoise</a>  came up with an eloquent solution using a SSL Proxy software called [url=https://www.stunnel.org/downloads.html]STunnel[/url].</p><p>RE:  <a class="lnk3" title="Re: Pegasus Mail and Verizon FIOS" href="http://community.pmail.com/forums/thread/39683.aspx">Re: Pegasus Mail and Verizon FIOS</a></p><p>The objective is to install STunnel as a NT Service [ <font color="#660000"><b>"C:\Program Files\stunnel\bin\stunnel.exe" -install</b></font> ] </p><p>and then to edit its configuration file for Verizon servers;  <font color="#0000cc"><b>C:\Program Files\stunnel\config\<font color="#330000">stunnel.conf</font></b></font></p><p>and add...</p><p><b><font face="courier new,courier">[verizon-POP3-SSL] ; SSL connection to Verizon's POP3 server for Pegasus client = yes accept = 10995 connect = pop-verizonmail.egslb.aol.com:995 [verizon-smtp-SSL] ; SSL connection to Verizon's SMTP server for Pegasus client = yes accept = 10465 ;connect = smtp.verizon.net:465 connect = smtp-verizonmail.egslb.aol.com:465</font></b></p><p> STunnel will listen at Ports 10995 and 10465 on the local PC [ 127.0.0.1 ] and when it sees activity at these ports it makes the secure connection at AOL Email servers using the TCP ports they require  but uses STunnel to provide the secure connection. </p><p> </p><p>In P-Mail go to;  <b>Tools</b> --> <b>Internet Options</b> --> <b>Sending ( SMTP )</b> --> <b>Add</b></p><p>Give it a name such as "<b>Verizon STunnel Proxy</b>" and setup like the below...</p><p><img mce_src="https://multi-av.thespykiller.co.uk/other/PM1.jpg" src="https://multi-av.thespykiller.co.uk/other/PM1.jpg" width="405" height="476"> <img mce_src="https://multi-av.thespykiller.co.uk/other/PM2.jpg" src="https://multi-av.thespykiller.co.uk/other/PM2.jpg"></p>

Actually, same problem here just popped up a few days ago. Receiving is fine, just can't send. I'm using my own domain. Interestingly I also use eudora for some other addresses and have no problem whatsoever with that. Same settings as peg. 

Actually, same problem here just popped up a few days ago. Receiving is fine, just can't send. I'm using my own domain. Interestingly I also use eudora for some other addresses and have no problem whatsoever with that. Same settings as peg. 
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 ?
Pending draft ... Click to resume editing
Discard draft