- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Email was working fine until Monday Sept 30th.
I updated my Eudora 7.1 settings for the new ports required by Verizon, and changed from "incoming.verizon.net" to "pop.verizon.net", and also from "outgoing.verizon.net", to "smtp.verizon.net". Now I cannot get or send anything from Verizon.
Note that I have other pop email accounts from other carriers, and I can still get and receive from those accounts. It is only Verizon that has stopped working. The error is that it times out trying to connect. I tried pinging the addresses "pop.verizon.net", and "smtp.verizon.net", and it gives me timeout errors - It seems I cannot reach these servers.
I restored settings to use "incoming.verizon.net", and "outgoing .verizon.net", and now I can send but not receive. I tried pinging these addresses, and "outgoing..." responds, but "incoming..." does not; which explains why I have the symptom that I can send but not receive.
What's going on? Why can't I connect to the email servers?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@EN01 wrote:Email was working fine until Monday Sept 30th.
I updated my Eudora 7.1 settings for the new ports required by Verizon, and changed from "incoming.verizon.net" to "pop.verizon.net", and also from "outgoing.verizon.net", to "smtp.verizon.net". Now I cannot get or send anything from Verizon.
Note that I have other pop email accounts from other carriers, and I can still get and receive from those accounts. It is only Verizon that has stopped working. The error is that it times out trying to connect. I tried pinging the addresses "pop.verizon.net", and "smtp.verizon.net", and it gives me timeout errors - It seems I cannot reach these servers.
I restored settings to use "incoming.verizon.net", and "outgoing .verizon.net", and now I can send but not receive. I tried pinging these addresses, and "outgoing..." responds, but "incoming..." does not; which explains why I have the symptom that I can send but not receive.
What's going on? Why can't I connect to the email servers?
In addition to port and server names, make sure ALL the new setting requirements that were put out are made. The new settings do work.
- Incoming mail server (POP3): pop.verizon.net
- Incoming Server Port Numbers: 995
- Outgoing mail server (SMTP): smtp.verizon.net
- Outgoing Server Port Numbers: 465
- Make sure SSL is enabled. (For POP & SMTP)
- Make sure Password authentication is set to normal.
- Options similar to "My server requires authentication" should be checked.
- Your Verizon Online user name is *****@verizon.net
- Your Verizon Online password
If you still have problems post a screenshot of your settings and we will be better able to identify the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Walt,
why doesn't verizon post on announcements that they are phasing out old email settings?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@kaytabor30 wrote:Walt,
why doesn't verizon post on announcements that they are phasing out old email settings?
They did. The information was first put out in 21012.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
walt,
sorry i did not make myself clear i ment to say the phasing out of the email settings happined on sept21 why did verizon post that on announements.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
did not post on announcements lol
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, all settings ARE setup as you show.
Even if they weren't it wouldn't explain why I can't ping the server.
Screen Capture (from cmd prompt):
C:\>ping pop.verizon.net
Pinging pop.verizon.net [206.46.232.132] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 206.46.232.132:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>ping smtp.verizon.net
Pinging smtp.verizon.net [206.46.232.100] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 206.46.232.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@EN01 wrote:Yes, all settings ARE setup as you show.
Even if they weren't it wouldn't explain why I can't ping the server.
Screen Capture (from cmd prompt):
C:\>ping pop.verizon.net
Pinging pop.verizon.net [206.46.232.132] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 206.46.232.132:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>ping smtp.verizon.net
Pinging smtp.verizon.net [206.46.232.100] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 206.46.232.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>
Yes it could explain no ping response. If I were Verizon ping would be disabled to prevent a denial of service attack using ping.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Okay, it is possible; But seriously? Ping is such a low overhead operation that it could not be reasonably used for denial of service. The fact is, 95% of the overhead associated with it, is consumed by the system simply discriminating that it IS a ping; So if one wanted to use it for DOS, it would work nearly as well anyway, even if the service wasn't enabled. Besides, ping is part of the core TCP/IP standard; It is used for system troubleshooting, and should NEVER be disabled. Of course, that doesn't mean that it hasn't been ... Can someone verify this?
In ay case, I am still unable to read my email. When Eudora starts its polling cycle,
it shows the following status for an extended duration:
JohnDoe - Logging into POP Server
Then after 5 mins, (I timed it) the status clears and the following appears in the Error Log:
JohnDoe Logging into POP Server, [HH:MM:SS AM]
Error Reading from Network. Cause: Connection closed by foreign host. (0)
Is it possible that my account is corrupted? My service is configured with six mailboxes (my service is supposed to have up to ten I believe) ... In order to read from those mailboxes, I must login with the appropiate ID in each case. Could it be those accounts are not set up correctly on the new server?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@EN01 wrote:Okay, it is possible; But seriously? Ping is such a low overhead operation that it could not be reasonably used for denial of service. The fact is, 95% of the overhead associated with it, is consumed by the system simply discriminating that it IS a ping; So if one wanted to use it for DOS, it would work nearly as well anyway, even if the service wasn't enabled. Besides, ping is part of the core TCP/IP standard; It is used for system troubleshooting, and should NEVER be disabled. Of course, that doesn't mean that it hasn't been ... Can someone verify this?
In ay case, I am still unable to read my email. When Eudora starts its polling cycle,
it shows the following status for an extended duration:
JohnDoe - Logging into POP Server
Then after 5 mins, (I timed it) the status clears and the following appears in the Error Log:
JohnDoe Logging into POP Server, [HH:MM:SS AM]
Error Reading from Network. Cause: Connection closed by foreign host. (0)Is it possible that my account is corrupted? My service is configured with six mailboxes (my service is supposed to have up to ten I believe) ... In order to read from those mailboxes, I must login with the appropiate ID in each case. Could it be those accounts are not set up correctly on the new server?
Perhaps you don't understand what a ping denial of service attack is and does, and how sever it can be. It the most basic method of denial of service and was one of the first used. It can easily overwhelm a site by flooding it with ping requests. I just pinged cnn.com -- they've turned theirs off too, as have almost every other major web site (microsoft.com, apple.com, etc.).
If you really want to test if a site is receiving email, you need to use an smtp client of some sort to open a connection to the Verizon mail server.
Have you tried any other mail client that Eudora? I monitor several email forums, and the only posts I"m seeing like yours are for people using Eudora.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@EN01 wrote:Yes, all settings ARE setup as you show.
Even if they weren't it wouldn't explain why I can't ping the server.
Being able to ping the servers and being able to send and receive email are two separate issues. I can't ping the servers either, but have no problem sending or receiving email. I suggest you ignore that issue as the inability to ping them is probably normal.
On the email issue, many users, including Eudora users have been able to get it to work. But as I don't use Eudora, the best I can do at this point is refer you to a lengthy thread addressing the issue. Hopefully, the solution you need will be found there.
http://forums.verizon.com/t5/Verizon-net-Email/Eudora-amp-server-changes/m-p/551673
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's working fine for me using Outlook on a PC and the Android email app on my tablet.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
>>en01: Email was working fine until Monday Sept 30th. I updated my Eudora 7.1 settings for the new ports required by Verizon, and changed from "incoming.verizon.net" to "pop.verizon.net", and also from "outgoing.verizon.net", to "smtp.verizon.net". Now I cannot get or send anything from Verizon.
First...there is a recent issue with Eudora sending mail in which you get an authentication error message. This started a few days ago and I found that if, after the authentication error message, I went to my Eudora (version 7.1, Win7/Pro) OUT box, double clicked on the non-sent email to open it up again and then clicked on the Send button, the email would be sent successfully although sometimes I had to do the process again to get a successful send. Late last night and about 4:15pm (eastern) today, I was able to successfully send email from Eurdora with no authentication errors so perhaps they've fixed the authentication error problem. I'm in the Washington, DC metro area (VA). Where are you?
With respect to the "new" Verizon server changes.
Check the following in Eudora via Tools > Options > Sending Mail and see if the following are set:
1. SMTP Server: smtp.verizon.net
2. Checkmark: "Allow Authentication", "Immediate Send", "Send on Check"
3. DO NOT Checkmark: "Use submission port 587"
4. Secure Sockets When Sending: choose "Required, Alternate Port" --prior to the recent changes, I had chosen "if available, use STARTTLS"
For your Verizon Personality in Eudora--Personality tab, highlight the appropriate Personality, right-click, choose Properties--on the Generic tab:
1. Email Address: should have your FULL Verizon email address, for example: myverizonemailaddress@verizon.net
2. User Name: should be your Verizon user name--should be the same as your email address, at least mine is--without the "@verizon.net"
3. SMTP Server: smtp.verizon.net
4. Checkmark: "Authentication Allowed"
5. DO NOT Checkmark: "Use submission port 587"
6. Secure Sockets when Sending: choose "Required, Alternate Port" --prior to the recent changes, I had chosen "if available, use STARTTLS"
For your Verizon Personality in Eudora, on the Incoming tab:
1. Incoming Mail: pop.verizon.net
2. Configuration: POP
3. Authentication Style: Passwords
4. Secure Sockets when Receiving: choose "Required, Alternate Port" --prior to the recent changes, I had chosen "if available, use STARTTLS"
Hope that helps...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As this thread is now over two years old, it will be locked in order to keep discussions current. If you have the same or a similar question/issue we invite you to start a new thread on the topic.
