rmd 1.4.6 & no rmd for firefox 3
Last month I put together a 1.4.6 build of the Remember Mismatched Domains extension for Firefox and Thunderbird. This update is pretty much just a “maintenance release” making RMD more compatible with SELinux as well as fixing a couple of my usual localization screw ups. (Thanks to Josh for both pointing out the SELinux issue as well suggesting how to solve it).
The more exciting announcement for this update is that I’m hoping version 1.4.6 will be the final release. Back in October I wrote about the new security exception features in Firefox 3 which essentially provide the functionality that RMD has been providing for the past couple of years. Since then Firefox 3 has been steadily moving through the beta stage and soon enough will be released. (Thunderbird users will be happy to hear that the same security exception features are available in the nightly builds of the still very early Thunderbird 3). What this all means in the long run is that RMD will not be available for Firefox 3. Please note that I have every intention to continue maintaining the extension for Firefox 2 for as long as it is a Mozilla supported product.
Now’s the time to voice your questions, concerns…
Josh says:
January 10, 2008 at 6:36 am
You’re welcome!
I downloaded this and put it into FF and TB and it seems to work well.
Josh
Randy Gamage says:
January 14, 2008 at 1:04 pm
For some reason, with the Pair Networks certificate this add-on doesn’t remember it. It worked for a while, but about a week ago it stopped remembering and now asks every time about this certificate. The Common Name on the cert is “*.pair.com” - maybe the * is throwing it off? I don’t know if Pair recently changed their naming or other cert details - I have an inquiry in to them. Please help! -Rudy
andrew says:
January 14, 2008 at 5:55 pm
Hi Randy,
I just successfully remembered the mismatched cert from pair.com. I wonder if maybe there’s a problem with your RMD installation. Maybe you could check if it works on another domain (I like to try against https://www.google.ca/).
If, as I suspect, it doesn’t work maybe try reinstalling RMD. If you still have trouble let me know (what version of Firefox or Thunderbird and OS?)
Cheers,
A.
Gordon says:
January 17, 2008 at 8:23 am
Does the latest version work on Thunderbird 3?
Thanks!
andrew says:
January 17, 2008 at 9:35 am
No, Thunderbird 3 should also provide the capabilities to define “Security Exceptions”.
Randy Gamage says:
January 18, 2008 at 2:28 pm
Andrew: Yes, that seems to have worked - uninstalled and re-installed the extension. Thanks much,
Randy
(BTW - Using Windows XP & TB 2.0.0.6)
Jonathan says:
January 22, 2008 at 3:47 pm
Randy… Much thanks for this very useful extension. I have 6 IMAP email accounts which I access via a secure IMAP connection. They all have mismatched domains on their certs. It was nearly impossible to manage my email over secure connections in Tunderbird before I found your extension.
I´d like to suggest you continue working on it or pass it on to another developer…or… anything to keep it working with new TB versions. I realise the server you use no longer poses an issue for you… but many of your fan club are using other servers and will still need to use this great extension!!
Much thanks…
Jonathan
andrew says:
January 22, 2008 at 4:53 pm
Johnathan,
Does the security exception feature in new TB3 builds not provide some RMD functionality that you use?
Just to be clear, I’d be fine with continuing to develop / maintain the extension were it required.
Cheers,
A.
mario says:
January 31, 2008 at 8:00 am
I installed the version 1.4.6 on my Seamonkey 1.1.7. The installing works fine. BUT: The remembering doesent work. Every time i will send the mail, i´ve got the message, with the unchecking-possibility for rembembering. Can you help?
Thanks,
Mario
andrew says:
January 31, 2008 at 8:41 pm
Hi Mario,
Seamonkey users have had some problems in the past with getting the XPCOM component for RMD registered. It seems to be most common on Windows (but that just may be a result of Windows’ prevelance).
Anyhow, some folks have had luck with uninstalling and reinstalling the extension. Another trick that sometimes works is to delete the compreg.dat file located in your profile folder and restarting Seamonkey (compreg is the component ‘database’ and deleting it forces Seamonkey to re-register components the next time it starts).
Let me know how you make out.
Cheers,
A.
redfox says:
February 3, 2008 at 4:51 am
I need this extension for Netscape 7.1 (Mozilla 1.4). Will it work?
Or, is there a prefs.js config expression, which could eliminate these warnins for all servers and certificates?
I have been searching for such thing for almost 2 years, but found nothing yet ;)
redfox says:
February 3, 2008 at 4:58 am
P.S. I just tried to install the latest version of rmd to Netscape 7.1 and it completely destroyed it… when I try to load an encrypted page, which has the domain name / certificate mitsmatch, the browser stops working at all.
Godai71 says:
February 9, 2008 at 3:42 pm
Hi.
Just a small question: Why the last version of RMD (1.4.6) is not on Mozilla add-ons?
I can find on AMO only 1.4.3.
andrew says:
February 9, 2008 at 9:15 pm
Only because I’m lazy ;-)
It usually takes awhile for an extension to pass through the AMO Q/A process - do me a favour and remind me again if you don’t see it up there in a week or so?
Cheers,
A.
bloodnok says:
February 23, 2008 at 3:27 pm
just tried installing this on “Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12″ & the install failed with a “… could not be installed because it is incompatible with your Firefox build type (Darwin_x86-gcc3).” sigh …
this is a desirable extension as my isp has a mismatched certificate. any chance of a fix? i have xcode so i can build it myself if that’s allowed.
andrew says:
February 23, 2008 at 6:22 pm
bloodnok, I would’ve expected it to install for ya… (Others with similar setups have RMD running successfully).
Odder still is that the architecture you mentioned (Darwin_x86-gcc3) is in the extensions install manifest:
http://code.google.com/p/rmd/source/browse/trunk/install.rdf#23
Afraid, I don’t have much of an answer for ya… Maybe you could try the install again and compare the architecture string against that in the manifest, perhaps there’s a discrepancy in character case or something (seems unlikely). If you run Thunderbird it would be interesting to see if it behaves in the same way (theoretically it should).
If nothing turns up for you let me know. Worst comes to worst, we could try to hack together an xpi that skips the targetPlatform checking.
Cheers,
A.
Godai71 says:
February 26, 2008 at 6:54 pm
As your request http://www.andrewlucking.com/archives/2008/01/rmd-146-no-firefox3/#comment-64048
I’m here to remenber to update version of your rmd on AMO site.
andrew says:
February 26, 2008 at 7:42 pm
Hi Gogai77,
Thanks for the reminder.
I did submit RMD 1.4.6 to AMO a couple of weeks ago and it’s currently pending Q/A approval. Usually that process takes about a week but I imagine testers are extra busy with extensions being updated for Firefox 3.
Cheers,
A.
Pontificus says:
February 27, 2008 at 2:10 pm
Dude, you frickin rule. That has been bugging the crap out of me for weeks! It even lets you bypass expired certs
ruben says:
February 29, 2008 at 6:54 am
I like your plugin. It helps not to get a brain damage when clicking away this certificate dialog.
It worked fine under Thunderbird 2.0.0.12 with Windows. But under Mac OS 10.5 Thunderbird claims that the plugin is not compatible with the Thunderbird build type “Darwin-X86-gcc3″.
Maybe you could fix this…
andrew says:
February 29, 2008 at 9:05 am
Hey Ruben,
Could you do me a favour and compare the build type string including character case (uppercase / lowercase) that Thunderbird quotes in the error against the value on line 23 in the extension’s manifest file:
http://code.google.com/p/rmd/source/browse/trunk/install.rdf#23
“bloodnok” mentioned the same error a couple of comments above but I’m not sure what’s causing it…
Thanks,
A.
andrewlucking.com » download rmd 1.4.6 from addons.mozilla.org says:
March 3, 2008 at 8:28 pm
[…] just a reminder that RMD will not be updated to support Firefox […]
ruben says:
March 17, 2008 at 8:16 am
Hey Andrew,
the plugin works fine with Thunderbird on MacOS now, I think you did an update …
As far as I remember the build type string was “Darwin_x86-gcc3″ exactly.
Thanks a lot!
andrew says:
March 17, 2008 at 12:28 pm
Glad it’s working. I’d really like to take credit for fixing this but nothing has changed…
Erik Harris says:
April 6, 2008 at 9:53 am
I’ve got an odd problem with RMD. I’ve been using Firefox 3 since Beta 4, so I’ve only installed two versions (4 and 5), but each time I’ve installed a new beta of Firefox 3, RMD has stopped working in Thunderbird, and every time I send an email, I get the mismatched domain notice. Every time I tell it to remember the mismatched domain, it adds it to RMD’s list - which starts to accrue one duplicate entry for each message I send. Uninstalling and reinstalling the addon seems to fix it, but it’s kind of annoying regardless.
I don’t really know why Firefox is affecting Thunderbird’s add-ons, since I’m obviously not using RMD in Firefox 3b, but the add-on has failed for me twice in TB, and both times were right after I installed a new FF3 beta.
Erik Harris says:
April 6, 2008 at 9:53 am
Addendum to last post - I’m using WinXP, and en-us installs of both TB and FF.
andrew says:
April 6, 2008 at 10:37 am
You’re right, that *is* odd. The two applications (FF & TB) should have nothing to do with one another. There’s nothing out of the ordinary with your installs, they’re both installed to respective program files directories? And your profiles are not overlapping or anything?
Is it reproducible if you were to uninstall and then reinstall the Firefox 3 beta?
Cheers,
A.
Erik Harris says:
April 7, 2008 at 3:08 pm
Correct, nothing is odd about the installs. The install directories and profiles are both separate. I’ll try uninstalling and reinstalling Firefox to see if that does anything.
Erik Harris says:
April 7, 2008 at 8:13 pm
Uninstalling and reinstalling Firefox didn’t cause this to repeat. I uninstalled/reinstalled to the same directory, though, whereas the betas have been putting themselves in different directories. Beta 4 put itself in Program Files\Mozilla Firefox 3 Beta 4\ I let it do so thinking I could simultaneously use FF2 and FF3 (no such luck, the FF2 executable redirected to FF3). When beta 5 came out, I forced it to go back to Program Files\Mozilla Firefox\. I have no idea if the directory change had something to do with it, or if some other app may have interfered. If I figure anything out, I’ll add another comment.
andrew says:
April 7, 2008 at 8:59 pm
Thanks for looking into that, Erik.
Glance says:
April 17, 2008 at 8:35 am
Hello mate!
Firstly, I must tell you that this is a great extension and it worked fine in FF. But I need it to work in SeaMonkey too and I’m guessing it’s the problem with registering the XPCOM thingie you’ve mentioned.
I’ve tried removing and installing again your add-on but it didn’t work for me :( Should I try re-installing it again?
Could I do that XPCOM registering manually? Could you give me some pointers?
Thanks and keep up the good work!