Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

An "Unverifiable security certificate" problem.

1 view
Skip to first unread message

Jorie

unread,
Aug 7, 2008, 9:38:00 AM8/7/08
to
I use WLM with Comcast.net. Every time I log on to send or receive email I
get a dropdown message "The server you are connected to is using a security
certificate that could not be verified. The certificate's CN name does not
match the passed value. Do you want to continue? Yes/No" I have to click
"Yes" before it will continue.

Comcast claims this is not their problem and to check my firewall settings.
I don't see any problem there--that is Comcast does not seem to be blocked or
anything like that.

Is there a way to deal with this nuisance?

Jorie

unread,
Aug 7, 2008, 9:46:01 AM8/7/08
to
I should have added that I'm using Vista Home Premium Version 6.0.6001
Service Pack 1 Build 6001
if that makes any difference.

...winston

unread,
Aug 7, 2008, 4:14:18 PM8/7/08
to
1. Verify your comcast account settings and ensure they are correct for server, port, authentication (outgoing), and SSL.
2. Define logon
- sign on to Windows
- sign on to WLM
- enter a username and password when prompted after manually initiating a send/receive in WLM
- enter a username and password when prompted during an automatic send/receive in WLM
- logon to the Web server

3. For IE7
- Click tools, internet options, click advanced tab, uncheck the box that says..check for server certificate revocation

4. Do not remove the account without backing up all folders and messages. Remove the account in WLM will remove the folders and
messages
--
...winston
ms-mvp mail


"Jorie" <Jo...@discussions.microsoft.com> wrote in message news:69A2AB9B-AFB8-45E2...@microsoft.com...

Michael Santovec

unread,
Aug 7, 2008, 6:33:44 PM8/7/08
to
Typically that means that at Tools, Accounts, Mail, Properties, Servers,
Incoming Mail (POP3) you are using an alias for the server name rather
than their preferred name as recorded in the certificate.

If you anti-virus is set to scan mail as it downloads it may have put a
phony name there in order to place itself between WLM and the mail
server.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm

"Jorie" <Jo...@discussions.microsoft.com> wrote in message
news:69A2AB9B-AFB8-45E2...@microsoft.com...

Jorie

unread,
Aug 7, 2008, 9:15:08 PM8/7/08
to
Hmm. Well, it's what they gave us when our email was set up w/ Comcast a
year ago. I'll check again w/ them, or, is there any way to go online to see
what different companies use? they aren't very helpful when I contact them
but I'll try again. thanks for your help.

Gary VanderMolen

unread,
Aug 7, 2008, 10:44:21 PM8/7/08
to
Go to Tools, Accounts, select that account, Properties.
On the Servers tab, notice what your are using for incoming (POP3) and
outgoing (SMTP) server names.
On the Advanced tab, notice what you are using for port numbers and SSL option
for the two mail servers. Post that information here.

--
Gary VanderMolen, MS-MVP (Mail)


"Jorie" <Jo...@discussions.microsoft.com> wrote in message news:CD17E7C7-16A3-40C7...@microsoft.com...

Jorie

unread,
Aug 8, 2008, 9:03:01 AM8/8/08
to
Thank you for the responses.

BTW (re advice from Winston) I tried to uncheck the box that says..check for
server certificate revocation and that made no difference.

Server POP3
SMTP smtp.comcast.net
Outgoing Port 587
Requires SSL
Incoming Port 995
Requires SSL

Gary VanderMolen

unread,
Aug 8, 2008, 1:11:59 PM8/8/08
to
OK, I see the reason for your problem.
Go to Tools, Accounts, select that account, Properties, Advanced.
Change the 995 port to 110. Unselect the SSL option for both servers.
Click OK. That should do it.

--
Gary VanderMolen, MS-MVP (Mail)


"Jorie" <Jo...@discussions.microsoft.com> wrote in message news:DD6853EF-4085-44B2...@microsoft.com...

...winston

unread,
Aug 9, 2008, 4:58:35 AM8/9/08
to
Return the setting to its original setting.
Thanks for reporting the impact.

--
...winston
ms-mvp mail


"Jorie" <Jo...@discussions.microsoft.com> wrote in message news:DD6853EF-4085-44B2...@microsoft.com...

Jorie

unread,
Aug 9, 2008, 3:40:00 PM8/9/08
to
Thanks for the reminder. I had done that.

Jorie

unread,
Aug 9, 2008, 3:39:01 PM8/9/08
to
Well, I was hopeful--but it didn't work.

1.Tools/accounts/properties/advanced:
Changed Incoming Port from 995 to 110; unchecked SSL;
Tried email program--wouldn't connect.

2. Decided to reverse each of the 3 actions above one at a time to see if it
would work. That is I changed the port number, checked the SSL for incoming,
checked the SSL forSMTP. Wouldn't connect.

I went back and reversed all the changes but it still won't connect at all.

Error message says the connection failed.
Outgoing Error ID 0x800CCC0E (not certain if those are zeroes or cap O in
the error message.) Socket error 10060

I closed the program and reopened--still no connection.

Problem is worse than before. YIKES!
I really need help, guys!

One additional fact to add to the mix.
Under Tools/Accounts/Properties/Servers, "Log on using clear text
authentication"
is checked. I assume that's OK?

I really need help here.

BTW I use Windows OneCare for antivirus/spyware. Since it's a Windows Live
program I think, it shouldn't cause a problem that would throw up this server
certificate issue UNLESS the WLOC firewall is somehow doing something
unusual??

Gary VanderMolen

unread,
Aug 9, 2008, 3:53:52 PM8/9/08
to
Please post the complete error message you get when using port 587
for SMTP and port 110 for the POP3 server, no SSL for either.

"Clear text" authentication is the normal and appropriate setting.
However, make sure "My server requires authentication" is checked.

--
Gary VanderMolen, MS-MVP (Mail)


"Jorie" <Jo...@discussions.microsoft.com> wrote in message news:66B1A299-8468-45B9...@microsoft.com...

Jorie

unread,
Aug 9, 2008, 3:55:00 PM8/9/08
to
This is a second message re my lack of connection for email after making the
suggested changes and then reversing them:

Everything now is as it was beforfe I made the changes you suggested, Gary.
I shut down my WLM, opened again and this time, instead of hitting
"Send/Receive, I separated the functions.

I tried receiving. It showed "connecting" and said I had no new mail. I
assume that means the receiving function is OK (BTW, no request for
certificate approval came up as it has been doing--the original cause for my
post)

I then tried sending. The request for certificate approval did come up.
However, no connection was made and the same error message I reported came up.

Sure hope you guys can help. I have absolutely no idea what to do next.

Gary VanderMolen

unread,
Aug 9, 2008, 4:10:40 PM8/9/08
to
You will get the certificate error whenever you use the inappropriate
"SSL" option. Please use the settings I recommended, and if an
error message results, post it.

--
Gary VanderMolen, MS-MVP (Mail)


"Jorie" <Jo...@discussions.microsoft.com> wrote in message news:E437BF6C-5F7F-41BE...@microsoft.com...

Jorie

unread,
Aug 9, 2008, 4:15:00 PM8/9/08
to
Will do. I did just get some incoming mail -- had the same certificate
error message tho but outgoing didn't work. Will go make the changes you've
suggested and t ry again.

Jorie

unread,
Aug 9, 2008, 4:25:00 PM8/9/08
to
YES it worked!!!

I opened WLM that had been shut down for 5 minutes.
Made the changes you suggested.
Composed a test message to myself.
Clicked Send/Receive
No request to approve a certificate came up!
And--mail was sent and received.

I think you've done it Gary!
I'd like to know the reason for changing to SMTP Port 587 but if you don't
have time to explain that's OK.
I am just so grateful for your time and for the time of everyone who's tried
to help me with this really "nuisance" problem.

Thanks so very much! You are a MVP. Smile!

Jorie

unread,
Aug 9, 2008, 5:01:00 PM8/9/08
to
Again--thanks so much.
It's still working!
I'm closing my responses to this thread now.

Gary VanderMolen

unread,
Aug 9, 2008, 6:07:54 PM8/9/08
to
Glad to hear it worked.

Comcast has changed their SMTP port from 25 to 587, apparently without
notifying their customers adequately.

--
Gary VanderMolen, MS-MVP (Mail)


"Jorie" <Jo...@discussions.microsoft.com> wrote in message news:DA159C66-F3EA-44F9...@microsoft.com...

Gary VanderMolen

unread,
Aug 9, 2008, 6:08:41 PM8/9/08
to
You're very welcome.

--
Gary VanderMolen, MS-MVP (Mail)


"Jorie" <Jo...@discussions.microsoft.com> wrote in message news:4DF388C0-10FE-4E85...@microsoft.com...

0 new messages