Skip to content

Re-enable Mail.app Plugins in 10.6.5, 10.6.7

'Brick' plugin icon

Since Snow Leopard, each new release of Mail.app (recently updated with 10.6.5 and now 10.6.7) and the Message.framework it depends on changes a ‘plugin compatibility’ UUID and suddenly breaks any plugins or extensions you have enabled in Mail.app. The developers of each extension have to update each and every one manually, and can’t do so before the new software from Apple is released.

If you can’t (be bothered to) wait for the updates from your plugin developers to arrive, however, and are confident that the plugin will work with the new version, you can hack said plugins and force them to be re-enabled inside Mail.app using the following method. Here I’ll be working with GrowlMail 1.1.2, but this should work for most Mail.app plugins.

A word of warning — not only does this involve editing the plugin’s files, which if you get it wrong could break that plugin and force you to download and install it again, it is possible that your plugin really isn’t compatible with the new version of Mail, in which case it could cause more serious problems. Back stuff up before trying this — you should be doing so anyway.

Find the bundle

Your Mail.app plugins should be located in ~/Library/Mail/Bundles. If you’ve already launched Mail.app after the upgrade to 10.6.5 (or other upgrade), it might have already disabled the plugins. In that case, you’ll find them in ~/Library/Mail/Bundles (Disabled). (Some plugins may also install in the root-level Library — /Library/Mail/Bundles)

Locate Info.plist

Contents of GrowlMail.bundle

Once you’ve found the bundle you want to re-enable with the new version of Mail, open it (you may need to right-click and choose Show Package Contents). Here, that is GrowlMail.bundle.

Inside the Contents folder, you should find Info.plist. Open this in TextEdit.

Info.plist for GrowlMail

You’ll find a section looking like this:

<key>SupportedPluginCompatibilityUUIDs</key>
  <array>
    <string>B3F3FC72-315D-4323-BE85-7AB76090224D</string>
    <string>225E0A48-2CDB-44A6-8D99-A9BB8AF6BA04</string>
    <string>99BB3782-6C16-4C6F-B910-25ED1C1CB38B</string>
    <string>2610F061-32C6-4C6B-B90A-7A3102F9B9C8</string>
    <string>2F0CF6F9-35BA-4812-9CB2-155C0FDB9B0F</string>
    <string>0CB5F2A0-A173-4809-86E3-9317261F1745</string>
    <string>B842F7D0-4D81-4DDF-A672-129CA5B32D57</string>
    <string>E71BD599-351A-42C5-9B63-EA5C47F7CE8E</string>
  </array>

Underneath the last <string> entry, but before </array>, add these two entries. These are the new UUIDs for the 10.6.5 versions of Mail.app and Message.framework:


    <string>BDD81F4D-6881-4A8D-94A7-E67410089EEB</string>
    <string>857A142A-AB81-4D99-BECC-D1B55A86D94E</string>

UPDATE for 10.6.7:

Here are the new UUIDs you’ll need for for Mac OS X 10.6.7. Add these as well to update your Mail.app plugins for this new release:


    <string>9049EF7D-5873-4F54-A447-51D722009310</string>
    <string>1C58722D-AFBD-464E-81BB-0E05C108BE06</string>

That section of your Info.plist should now look something like this:

<key>SupportedPluginCompatibilityUUIDs</key>
  <array>
    <string>B3F3FC72-315D-4323-BE85-7AB76090224D</string>
    <string>225E0A48-2CDB-44A6-8D99-A9BB8AF6BA04</string>
    <string>99BB3782-6C16-4C6F-B910-25ED1C1CB38B</string>
    <string>2610F061-32C6-4C6B-B90A-7A3102F9B9C8</string>
    <string>2F0CF6F9-35BA-4812-9CB2-155C0FDB9B0F</string>
    <string>0CB5F2A0-A173-4809-86E3-9317261F1745</string>
    <string>B842F7D0-4D81-4DDF-A672-129CA5B32D57</string>
    <string>E71BD599-351A-42C5-9B63-EA5C47F7CE8E</string>
    <string>BDD81F4D-6881-4A8D-94A7-E67410089EEB</string>
    <string>857A142A-AB81-4D99-BECC-D1B55A86D94E</string>
    <string>9049EF7D-5873-4F54-A447-51D722009310</string>
    <string>1C58722D-AFBD-464E-81BB-0E05C108BE06</string>
  </array>

Once that is in place, save the Info.plist file and move the whole .mailbundle into Bundles, if it was in the Bundles (Disabled) folder before.

Quit and relaunch Mail, and your plugin should load.

Like this post?

If you would like to support the time and effort I have put into my tutorials and writing, please consider making a donation.

Post a Comment

On some sites, you must be logged in to post a comment. This is not the case on this site.
Your email address is not made public or shared. Required fields are marked with *.
*
*
*

Posting a comment signifies you accept the privacy policy.
Please note — usually your comment will appear straight away but sometimes it will be held for approval (this is due to the spam filter). If your comment is waiting to be approved, please don’t post it again! It will appear eventually.