 NetFixerFrom my cold dead handsPremium
join:2004-06-24
The Boro
 ·Comcast Business..
 ·Vonage
 ·Cingular Wireless
·Comcast
1 edit | inbound.att.net SSL cert expires today The inbound.att.net SSL cert expires today, and some email clients may start complaining if you are using that hostname to get your @att.net or @bellsouth.net email and are also using SSL on port 995.
My SeaMonkey client was complaining about it, but changing the server name from inbound.att.net to fpostoffice.isp.att.net fixed the problem. Outlook Express and my hMailServer polling client seemed to to be ignoring it (for now), but I suspect that they too would have started complaining after midnight (SeaMonkey was just being a bit premature with its warning).
EDIT:
Well, it's after midnight and I am getting no more complaints about an expired SSL certificate on inbound.att.net, so I guess they got around to installing the new certificate (at least for the server(s) that I connected to).
--
We can never have enough of nature.
We need to witness our own limits transgressed, and some life pasturing freely where we never wander. |
|
 burrisPremium
join:2000-08-22
Miami, FL
·VOIPo
| It's really amazing, isn't it?
Here's an example of one of the most mismanaged companies on the planet and yet one of the most successful.
Even after the breakup and the labs coming apart, they recovered, and no matter what they do or how they do it, they make money.
They must own the rights to the world of monopolies. |
|
 jativ
join:2001-07-25
Hurley, MS | reply to NetFixer
I am still getting the warning today on the server and port you mentioned using Outlook 2007. |
|
NetFixerFrom my cold dead handsPremium
join:2004-06-24
The Boro Reviews:
·Comcast Business..
·Vonage
·Cingular Wireless
·Comcast
| said by jativ:I am still getting the warning today on the server and port you mentioned using Outlook 2007.
It started working for my SSL queries starting sometime after midnight (but I just did a few brief tests and then switched back to fpostoffice.isp.att.net). Since the hostname inbound.att.net is actually a server farm, and not just a single server, it is possible that some of them have still not been updated with a new valid certificate, so getting the error message would be somewhat random. Maybe on Monday (when the engineers come back to work), all of the servers will get their SSL certificates updated.
--
We can never have enough of nature.
We need to witness our own limits transgressed, and some life pasturing freely where we never wander. |
|
 Wm
@bellsouth.net | reply to NetFixer
I'm having the same issues with outlook 2007 & my iPod.
My speed has been low for the last couple of weeks too. |
|
|
|
Reviews:
 ·AT&T U-Verse
·Comcast
 ·DIRECTV
·Vonage
 ·AT&T Southeast
·VOIPo
1 edit | reply to NetFixer
i have received the same expiration notice for the security certificate for inbound.att.net on 9.30.2012. it started last night, happened again tonight, same port (995), using MS Outlook 2007.
i called att u-verse tech support to let them know, was xfered to level 2, waited on hold almost an hour, but was finally able to reach a support rep and reported the problem.
the rep was kind enough to identify which server farm was processing my inbound email to report the issue.
--
The truth will set you free. But not until it is finished with you. - David Foster Wallace |
|
