Windows 7 - Errors with Verizon POP3

Asked By Nissi1 on 24-Dec-09 11:47 AM
I am using WLM in Vista and am having problems with the Verizon email
account.  The following is an error report:

Unable to send or receive messages for the Verizon (xxxxx) account. The
connection to the server has failed.

Server: 'incoming.verizon.net'
Windows Live Mail Error ID: 0x800CCC0E
Protocol: POP3
Port: 995
Secure(SSL): Yes
Socket Error: 10060

The Outgoing port has been changed to 587.

This has been occurring since yesterday.  Last week a similar situation
occurred with the AOL account.



--




N. Miller replied to Nissi1 on 24-Dec-09 12:14 PM
The error you are showing is for the incoming server connection. Server time
out, based on an Internet search on the socket error. Failure to connect
with the server, based on an Internet search on the WLMail Error ID.

Could be a firewall issue, or an AV scanner issue.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum
Peter Foldes replied to Nissi1 on 24-Dec-09 01:15 PM
Disable the email scanning option of your AV by uninstalling the AV and then
re-installing it without the email integration (scanning ) option

Also see the following

http://thundercloud.net/infoave/tutorials/email-scanning/index.htm

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.
Michael Santovec replied to Nissi1 on 24-Dec-09 02:35 PM
If it is an intermittent error, it could be a temporary problem with the
mail server.

In the last week I had that happen a number of times with Yahoo.

--

Mike - http://TechHelp.Santovec.us
Gary VanderMolen \(MVP\) replied to Nissi1 on 24-Dec-09 04:16 PM
I am not so sure that server supports advanced ports and/or SSL.
Try these settings:
Incoming port: 110, no SSL.

--=20
Gary VanderMolen, Microsoft MVP (Mail)
http://mvp.support.microsoft.com/default.aspx/profile/vandermolen


The=20
situation=20
Nissi1 replied to Gary VanderMolen \(MVP\) on 24-Dec-09 08:47 PM
For some reason over the past month I have had problems with each one of my
accounts in Windows Live Mail.  Two weeks ago it was Gmail which caused the
other accounts outgoing mail to get stuck in the Outbox.  I wrote to this
Newsgroup concerning it, but everything cleared up after I removed the Gmail
account.

Last week the AOL account also had problems with incoming mail.  It finally
cleared up on its own.  Now this week it is the Verizon account which is
having the same problem.  All the settings, except the Outgoing port which
was changed from 25 to 587 two months ago, are the same today as they were a
year ago when I started using WLM.  This is annoying.

I do not use an AV scanner, whatever that is, and I have used the same
firewall for over a year.  I will change the setting suggested by Gary and
see if that helps.

Thank you all for your assistance.

Have a Merry Christmas.

--



I am not so sure that server supports advanced ports and/or SSL.
Try these settings:
Incoming port: 110, no SSL.

--
Gary VanderMolen, Microsoft MVP (Mail)
http://mvp.support.microsoft.com/default.aspx/profile/vandermolen
Nissi1 replied to Nissi1 on 24-Dec-09 09:01 PM
I changed the incoming port to 110 and unchecked the SSL.  Once I clicked
Apply and OK, emails in the Verizon account immediately downloaded.

Thank you Gary and again Merry Christmas!

--



I am using WLM in Vista and am having problems with the Verizon email
account.  The following is an error report:

Unable to send or receive messages for the Verizon (xxxxx) account. The
connection to the server has failed.

Server: 'incoming.verizon.net'
Windows Live Mail Error ID: 0x800CCC0E
Protocol: POP3
Port: 995
Secure(SSL): Yes
Socket Error: 10060

The Outgoing port has been changed to 587.

This has been occurring since yesterday.  Last week a similar situation
occurred with the AOL account.



--
Michael Walraven replied to Nissi1 on 24-Dec-09 09:17 PM
My current verizon.net setting which are working fine:
Outgoing
Outgoing.verizon.net
SMTP, port 25
NOT SSL required

Incoming
incoming.verizon.net
POP3 port 110
NOT SSL required

Win7, WIndow Mail Live, connected via Verizon ISP FIOS

Michael
...winston replied to Nissi1 on 24-Dec-09 11:36 PM
What AntiVirus(AV) software is installed ?

--=20
...winston
MS-MVP[Mail]

of my
caused the
this
Gmail
finally
is
which
were a
and
The
situation
Gary VanderMolen \(MVP\) replied to Nissi1 on 25-Dec-09 12:42 AM
Glad to hear it.
Merry Christmas, Nissi.

--=20
Gary VanderMolen, Microsoft MVP (Mail)
http://mvp.support.microsoft.com/default.aspx/profile/vandermolen


clicked=20
The
situation
D. Kirkpatrick replied to Nissi1 on 25-Dec-09 03:37 PM
I do not believe that Port 995 will work - it might.

Verizon only closed off Port 25 on its mail servers and connecting
nodes.

For verizon mail you need to use Port 587 for sending (SMTP) mail
(outgoing.verizon.net).

As far as I know Incoming POP3 remains on Port 110.  At least that is
how I am set.

Note that Verizon's instructions to use Port 587 for outgoing mail is
only valid for their systems.  If you connect to a mail system other
than Verizon you need to use what ever alternativ eport they tell you.

For Gmail its Port 465.

For my own Web and Mail host its Port 26.
D. Kirkpatrick replied to Nissi1 on 25-Dec-09 03:40 PM
This will not make you feel any better, but I also connect with Verizon
via DSL.

Last week I had mail bounce back at me which was sent to a known-good
address.

The bounce message looked suspicious so I ran a check on the IP
addresses that were contained in the bounce message.

It said that my recipient was a business in Florida - when in fact it
was a Road Runner home account in Texas.  It also claimed that my
sending IP was Yahoo in Japan.

Clearly there was a problem on the net someplace.

Sadly this has been a regular issue for myself and my correspondent in
Texas - so much so that we now CC a Gmail address we each have just to
be certain.

Someone's DNS is screwed up - and on a regular basis.
D. Kirkpatrick replied to Michael Walraven on 25-Dec-09 03:45 PM
You may wish to consider switching to Port 587 for SMTP.  It may
already be active in your area.

Verizon is slowly rolling out a Port 25 block system wide and is doing
that region-by-region.

People are supposed to get a notice by e-mail when this happens but
not everyone is getting notified.

In my case I am a regular at DSL Reports and a Verizon "alt" group
used by customers so I knew this was coming, so one day when I woke up
and mail refused to go anyplace I was able to quickly change the ports
and go right along.

Note that the Port 25 block is effecting ALL MAIL even mail that is
destine for servers external to Verizon's system.  If you use any mail
other than Verizon's you will need to contact that system/ISP/service
to see what other ports are available.  Many will have a second port
activated.

If not, you are SOL Charlie.
N. Miller replied to D. Kirkpatrick on 25-Dec-09 04:16 PM
I'd have to see those IP addresses. I can think of a rational explanation
for the general concept of a geolocator error. Assuming you used
geolocation, and not an ARIN Whois lookup.


Not very likely at all.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum
Lou replied to D. Kirkpatrick on 26-Dec-09 09:46 AM
Ckeck Tools, Accounts, Propertys, Servers. The mail settings for Verizon are
incoming.verizon.net & outgoing.verizon.net. make sure it is set to pop 3.
Also, some 3rd party virus programs, (like Spy Sweeper) prevent mail to work.
In your virus protection go to shields & turn off the e-mail scanning. Hope
this helps.
Lou replied to D. Kirkpatrick on 26-Dec-09 09:54 AM
Check Tools, Accounts, Property's, Servers. The mail setting's for Verizon is
incoming.verizon.net & outgoing.verizon.net. Also some 3rd party virus
prograams (like Spy Sweeper) can affect mail. Open your virus protection, go
to the shields settings & disable e-mail scanning. Hope this helps.