Problem with ATT.NET:995 certificates

[jsjag]

ATT is changing all accounts from the worldnet server. Previously the iPOSTOFFICE.WORLDNET.ATT.NET using SSL. Now they want it to read iPOSTOFFICE.ATT.NET. As of 3/15/2010 the Woldnet server will be gone.

The problem is that unless I have the account setup as iPOSTOFFICE.WORLDNET.ATT.NET I will get an invalid certificate error message.

Is there a work around. I would add an exception if I knew the correct address.

My third party Contact Manager had no problem with changing the server address. I removed Worldnet from the address and it receives and sends just fine.

[tanstaafl]

See http://kb.mozillazine.org/Security_Erro ... te_Expired for a workaround until they update the certificate for the new mail server. They might not bother doing that until the old mail server goes away.

[jsjag]

Thanks but it won't install. The add-on is only valid for up to TB2 and I have TB3. There should be something built into TB to tell it to accept an over-ride for an expired cert. Hopefully they update their certificate, if they don't Thunderbird will not be usable for me. And that would be sad.

See http://kb.mozillazine.org/Security_Erro ... te_Expired for a workaround until they update the certificate for the new mail server. They might not bother doing that until the old mail server goes away.

[tanstaafl]

See http://kb.mozillazine.org/Updating_extensions . Typically if you disable the version check a add-on that supports 1.5 or 2.x will work.

[jsjag]

Thanks for your continued help.

I read it and added by config editor:

extensions.checkUpdateSecurity

The above is set to false

1. Right-click -> New -> Boolean
2. Name: extensions.checkUpdateSecurity
3. Value: false

Problem is that TB 3.01 will still not allow the add on.

I'm starting to get a bit miffed at the inability of me - the user to determine how much security risk I am willing to take. It was one of the reasons I moved from Opera.

Hm?

https://developer.mozilla.org/en/Extens ... patibility

Applies to Firefox 3 and Thunderbird 3 and later

Any entries in the update manifest that do not meet one of those two requirements will be ignored when checking for new versions.

Note that https links to sites with invalid certificates or that redirect to http sites will fail for both the update.rdf and updateLink cases. updateLink using an https site with a non-builtin token CA signed certificate will fail regardless of whether or not updateHash is used.

Does the above mean there is nothing a user can do to disable the certificate problem?

JS

See http://kb.mozillazine.org/Updating_extensions . Typically if you disable the version check a add-on that supports 1.5 or 2.x will work.

[tanstaafl]

I just installed it and while it says in red "not compatible with Thunderbird 3.0.1" the options button works fine. I've had that happen with other add-ons - it usually means it works okay, Thunderbird just complains.

Were you unable to install it, did it disable it, or did you assume it failed because of the error message?

[jsjag]

It said it failed and I assumed it failed.

I'll change the Pop3 address and and see if I get the message. Maybe it did install.

I just installed it and while it says in red "not compatible with Thunderbird 3.0.1" the options button works fine. I've had that happen with other add-ons - it usually means it works okay, Thunderbird just complains.

Were you unable to install it, did it disable it, or did you assume it failed because of the error message?

[jsjag]

It isn't installed.

I tried again to install it and received "Remember Mismatched Domains 1.4.6 could not be installed because it is not compatible with Thunderbird 3.0.1."

Looked in the extensions and it is not there. This is the one I"m trying to install: remember_mismatched_domains-1.4.6-fx+tb+sm.xpi

Sigh.

[tanstaafl]

remember_mismatched_domains-1.4.6-fx+tb+sm.xpi is what I installed

extensions.checkCompatibility is false. Its the critical setting. You didn't mention setting it.

I don't have extensions.checkUpdateSecurity defined. Its not needed since you're getting the add-on from the Mozilla add-ons web site.

[jsjag]

I also install this one: remember_mismatched_domains-1.4.6-fx+tb+sm.xpi
I'll see if checkCompatibility is false.

HM? On a search this isn't even in the config
extensions.checkCompatibility

Should I put it in?

remember_mismatched_domains-1.4.6-fx+tb+sm.xpi is what I installed

extensions.checkCompatibility is false. Its the critical setting. You didn't mention setting it.

I don't have extensions.checkUpdateSecurity defined. Its not needed since you're getting the add-on from the Mozilla add-ons web site.

[tanstaafl]

You need to create a boolean setting called extensions.checkCompatibility and set it false. That was the first of two settings that the KB article said to add. You only added the second.

[jsjag]

Strange thing is I did create something the same with a boolean. I remember because I was wondering how to delete it if I no longer need it. But now it is gone. I can now get it to pop up using add-on /option. How do I get it to work?

Maybe I'm just not seeing it because I have 102 degree fever and my head and chest are so congested I can barley breath.

You need to create a boolean setting called extensions.checkCompatibility and set it false. That was the first of two settings that the KB article said to add. You only added the second.