Reply
Posted Feb 10, 2013
Recently getting SSL Certificate error for inbound.att.net - bad signature

The topic says it - starting a few weeks ago, every attempt to fetch pop3 mail gets me a popup with the following error:

-----

SSL Certificate check for inbound.att.net:

 

Issuer:            CN=VeriSign Class 3 Secure Server CA - G3,OU=Terms of use at https://www.verisign.com/rpa (c)10,OU=VeriSign Trust Network,O="VeriSign, Inc.",C=US
Subject:           CN=inbound.att.net,OU=att.net Mail,O="AT&T Services, Inc.",L=Southfield,ST=Michigan,C=US
Fingerprint:       3e:13:32:42:87:cb:12:f7:2b:84:bd:a7:56:27:3c:8c
Signature:         BAD

Do you wish to accept?

-----

I am retrieving mail just fine from a different email account on a different PC with similar settings (although with different email app).
  In this case, I am using Evolution under Ubuntu Linux.  Everything was working fine until a few weeks ago.  I know I could just accept the certificate, but I would really love to understand what the problem actually is before I sweep it under the rug.

 

Thanks for any suggestions, preferably not pointing out I'm using "unsupported" software....

Recently getting SSL Certificate error for inbound.att.net - bad signature

1,837 views
5 replies
(0) Me too
(0) Me too
Post reply
Replies
(5)
0
(0)
  • Rate this reply
Feb 11, 2013
0
(0)

ostroffjh,

 

     I have included a few links that will hopefully be of help.

 

I'm having trouble with POP mail but it used to work

 

Email server settings (POP and SMTP)

 

 

     If your still having trouble please feel free to send a private message to one of our ATTCustomer care specialists by using the following link. Please include your name, email address, phone number and the best time to be contacted. An ATT representative will reach out to you within 48 hours.

 

Private Message

 

James

Did a post have a solution that worked for you? Help other people find solutions faster by marking posts that helped you as an "Accepted Solution". Learn about accepted solutions here.

I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: Recently getting SSL Certificate error for inbound.att.net - bad signature

0
(0)
  • Rate this reply
Feb 11, 2013
0
(0)

James,

 

Thanks for the response, but netither of the links you provided were helpful.  I have not changed password recently, and the problem is collecting my sbcglobal.net email via pop, not using att/yahoo to collect other email.

 

However, based on a bunch more searching, I am becoming more convinced that although AT&T/Yahoo might have made some recent change, the reason I am getting the error is likely due to a problem with the way Evolution is handling the SSL Certificates, and not with the certificate itself.  I'll pursue that path a bit further before I use your link for sending a private message.  One way or another, I'll post a follow-up when I have more information.

 

Jack

Re: Recently getting SSL Certificate error for inbound.att.net - bad signature

0
(0)
  • Rate this reply
Feb 14, 2013
0
(0)

ostroffjh,

 

     Yes a follow up post would be great, not only for myself but for many others that might encounter an issue like this as well.

 

 

James

 

Did a post have a solution that worked for you? Help other people find solutions faster by marking posts that helped you as an "Accepted Solution". Learn about accepted solutions here.

I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: Recently getting SSL Certificate error for inbound.att.net - bad signature

0
(0)
  • Rate this reply
Oct 25, 2013
0
(0)

Here we are 8 months later and I'm now having the same issue. Specifically, I've been using pop.att.yahoo.com for inbound on my Samsung Galaxy S (Verizon) cell. About a week or two ago I stopped getting my messages to the cell, although they are picked up by Outlook on the desktop. When I try changing it to inbound.att.net it says "cannot safely connect to server. org.bouncycastle.jce.exception . Could not validate certificate."  ATT says SENDING  is a "known issue" but my problem is receiving. Seems like it's been going on for quite a while...

 

Any ideas? Does ATT know about this? ( I just sent them a private note...)

 

Ed

Re: Recently getting SSL Certificate error for inbound.att.net - bad signature

0
(0)
  • Rate this reply
Oct 25, 2013
0
(0)
Seems I'm not able to send either....

Re: Recently getting SSL Certificate error for inbound.att.net - bad signature

Share this post
Share this post