Skip to content

MsgFiler Engine Mail Plugin

The MsgFiler Engine is an Apple Mail Plugin that is an optional add-on for MsgFiler 3. It speeds up mailbox loading and filing performance to remote IMAP mailboxes.

While it is highly recommended, if you are running MsgFiler on Snow Leopard or Lion, you do not need to install the MsgFiler Engine Mail Plugin in order to use MsgFiler. MsgFiler Engine is required to get the best performance out of MsgFiler on Mountain Lion.

Download MsgFiler Engine

Which version of MsgFiler Engine you must download depends on which version of MsgFiler you are running. Use this chart to determine which version of the Engine you should download.

MsgFiler 3.1MsgFiler 3.1.1 or higher MsgFiler 3.0.4MsgFiler 3.0.4 or 3.0.5
Download MsgFiler Engine Version 1.1.3 Download MsgFiler Engine Version 1.0.9.1

Check the MsgFiler About screen to see which version of MsgFiler 3 you are running.

Installing the Plugin

MsgFiler Engine is an Apple Mail Plug-In that works with MsgFiler 3. To install MsgFiler Engine, follow these instructions:

  1. Quit the Mail application.
  2. Go to the Finder
  3. Hold the Option key and click on the Go menu
  4. Choose Library
  5. Navigate to the Mail directory in the Library directory
  6. Drag MsgFilerEngine.mailbundle to Bundles folder in the Mail directory. Create the Bundles folder if it does not already exist.
  7. If you have never used another Mail bundle, you will need to run the following two commands in the Terminal application:

    If you are using OS X 10.7/Lion or OS X 10.8/Mountain Lion, type

    defaults write com.apple.mail EnableBundles -bool true
    defaults write com.apple.mail BundleCompatibilityVersion 4

    If you are using OS X 10.6/Snow Leopard, type

    defaults write com.apple.mail EnableBundles -bool true
    defaults write com.apple.mail BundleCompatibilityVersion 3
  8. Launch Mail.
  9. Launch MsgFiler.
  10. Open MsgFiler’s Preferences by clicking on the action menu in MsgFiler and choosing Preferences.
  11. Click the Filing tab.
  12. Check Use MsgFiler Engine to file messages.
  13. Close the MsgFiler Preferences window.

MsgFiler is now configured to use the MsgFiler Engine to file your messages.

NOTE #1: When using the MsgFiler Engine, the ability to move the selection up or down will be disabled in favor of Mail’s selection behavior after filing.

Removing the Plugin

To remove the MsgFiler Engine Plugin follow these steps:

  1. Quit Mail if it is currently running.
  2. Go to the Finder.
  3. Hold the Option key and click on the Go menu
  4. Choose Library
  5. Open Mail.
  6. Open Bundles.
  7. Move the folder MsgFilerEngine.mailbundle to a new location.
  8. Restart Mail.

NOTE #2: Undo/Redo support is handled by Apple Mail instead of MsgFiler.

Support Questions and Known Issues

Mountain Lion has disabled the MsgFiler Engine plugin. Filing is slow again in MsgFiler 3!
Update to MsgFiler 3.1 and install MsgFiler Engine 1.1.1
Filing is so slow after upgrading to Mountain Lion/Lion!
Re-install MsgFiler Engine. All Mail plugins are automatically disabled following an upgrade of the operating system.
I’m an old user of the MsgFiler Mail Plugin. Installing MsgFiler Engine makes the original mail plugin disappear.
Install the latest version of MsgFiler Engine to resolve this problem.

Version History

Version 1.0.0 – 2011-02-24
Initial release
Version 1.0.1 – 2011-03-07
Support for MsgFiler 3.0.1
Version 1.0.2 – 2011-03-09
Fixed bug preventing filing of messages to local mailboxes on non-English machines.
Version 1.0.3 – 2011-04-25
Faster loading of mailboxes with MsgFiler 3.0.2
Version 1.0.4 – 2011-06-08
OS X 10.7 Lion compatibility.
Version 1.0.5 – 2011-08-24
OS X 10.7 Lion compatibility.
Version 1.0.6 – 2011-09-08
Compatibility with SpamSieve.
Version 1.0.7 – 2011-10-11
Support for offline accounts.
Version 1.0.8 – 2011-12-27
Compatibility fixes.
Version 1.0.9 – 2012-08-09
Compatibility fixes for OS X 10.7.5.
Version 1.1.0 – 2012-08-01
Support for MsgFiler 3.1.
Version 1.1.1 – 2012-08-06
Compatibility fixes.
Version 1.0.9.1 and 1.1.2 – 2012-09-21
Compatibility fixes for OS X 10.6.8 and latest security update
Version 1.1.3 – 2013-04-18
Compatibility fixes.
Comment Feed

53 Responses

  1. msgfiler engine doesn’t seem to work – even though I installed the plugin, msgfiler still says it is not installed.

    • You need to check Enable access for assistive devices in Universal Access System Preferences for this to work. I’ll make this more clear in the documentation and on the app in the next release.

  2. Does MsgFiler.app also have to be running for the engine to function?

    • Yes, MsgFiler Engine requires MsgFiler to be running. MsgFiler app does not require MsgFiler Engine to work. It’s just there in case you want faster filing to remote IMAP mailboxes.

  3. It doesn’t seem to work: the message is reported as “filed” but it remains in the original mailbox. If I disable the “Use MsgFiler Engine…” option, it works. Assistive devices access is enabled and MsgFiler is running.

  4. @Sergio – Have you removed the original MsgFiler Plugin mail bundle from bundles or are both still there?

    • Same here. Assistive devices access is enabled, MsgFiler is running, removed the original MsgFiler Plugin mail bundle from bundles. Message is reported as “filed” but it remains in the original mailbox.

  5. G’day Adam,

    I suggest that you add a script to the installer to enable assistive devices (or to the app when choosing the option to use the plugin) and to remove the “old” plugin…..

    It is a pity that you have to go for this kind of clunky workaround – I hope that Apple loosens the rules on plugins so that you can make it a properly integrated experience!

  6. I bought the new version because I’m a long-time user and want to support development. That said, I’m going to continue to use my old plug-in as long as it works. Thanks for jumping through the Apple hoops though Adam and keeping this invaluable tool available.

  7. One thing you might look at is that if Mail isn’t running, you can’t check the “use MsgFiler Engine…” box.

  8. I have submitted MsgFiler 3.0.1 to the Mac App Store. It features a number of bug fixes and performance improvements, such as MUCH faster loading and creation of mailboxes. Spell Catcher compatibility is there and fixed bugs related to the use of the MsgFiler Engine Mail Plugin. Stay tuned for when the app is available to update from the Mac App Store.

  9. I just bought 3.0 is it possible to get just the uppdate from you

  10. “Enable access for assistive devices must be checked in the Universal Access pane of System Preferences.” -> Can’t find this, as my system language is German and all sorts of trying to translate this failed… Screenshot?

    Peter MetzingerJuly 29, 2011 @ 2:16 pmReply
  11. I am using the old version of MsgFiler now. If I upgrade to version 3, is it the case that I will have to accept either an icon in the dock or an icon in the status bar? Can I run version 3 headless, like version 2?

  12. John – You can turn off both via MsgFiler’s preferences. you should, however, install the MsgFIler Engine mail plugin to get the same performance of the original plugin in the new app.

  13. Any news on comptibility with 10.7.3?

    • Download 1.0.8, which works in 10.7.3. OS X updates routinely disable all Mail plugins. I typically have a new release of the Engine plugin at the same time the OS update comes out.

  14. I just tried re-downloading 1.0.8 with 10.7.3 and it isn’t working. Keeps complaining that an unsupported plug in was found and disabled.

  15. I’m having trouble here too with 10.7.3. I reinstalled and it works for a bit, then crashes and freezes up mail.

    • Check MsgFiler preferences and set Preferences / Filing / Label filed messages to None. Also make sure that Use MsgFiler Engine to file messages is checked.

    • It looks like that did the trick! Thank you Adam. Your product is outstanding and makes my life better every day.

      JenniferFebruary 15, 2012 @ 4:15 pm
    • Thanks, Adam-
      I had the same problem and that fixed it.

      Eric CataniaJune 8, 2012 @ 8:24 am
  16. G’day Adam,

    Will there be an update so that the MsgFiler Engine works with Mountain Lion?

  17. Yes, but the new MsgFiler Engine requires MsgFiler 3.1 (and vice versa), which I’m waiting to get approved on the Mac App Store.

  18. No Mail directory in the Library directory. I tried instead the Mail directory in the Applications folder but without success. Any hint?
    It is not critical since, without the engine, it is still working pretty fast.
    Thanks for a very helpful app !
    Regards, Lalo

    • The Mail directory should be in your User Library: ~/Library, not the Applications folder or the /Library folder.

  19. Thanks ! You are completely right (take into account that I am using the spanish names …).
    And thanks for the excellent MsgFiler. Lalo

  20. Just upgraded to latest version = mistake. Since there was nothing wrong, I shouldn’t have touched it. Now it’s moving messages slowly again (even with engine installed and “checked” in preferences). Basically, takes about 5-10 seconds per message to move now.

    I deleted msgfiler.app, new mail bundle, and all preference files. Installed old version I had in time machine backup and reverted old mail bundle. Fast again.

    10.7.4

    • Other users have been reporting this problem. It hadn’t come up in my debugging. Were you trying to file to local or remote mailboxes? Did you notice the slowdown with one or both methods?

  21. If the checkbox Use MsgFiler Engine to file messages is disabled, turn on access for assistive devices in System Preference / Accessibility temporarily.

    MsgFiler 3 should need this checkbox set, and I’ll fix this bug in the next point release (3.1.1).

  22. Using Snow Leopard, I installed 3.1 and the latest MsgFiler Engine. When I click on Use MsgFiler Engine to file messages I’m told that MFE isn’t installed. But it is in the ~/Library/Mail/Bundles folder and access for assistive devices is enabled.

  23. I have the same problem as Danny. I’m also using Snow Leopard and 3.1 and have used Terminal with the command lines as you instructed. After clicking the checkbox to use MsgFiler, a dialog tells me that MsgFiler Engine is not installed. But it is. Here is the path:
    ~/Library/Mail/Bundles/MsgFilerEngine.mailbundle/Contents/MacOS
    The MsgFiler Engine shows up as a Unix Executable File as the only item in the MacOS directory.

  24. Thanks for your prompt response, Adam. It solved my problem. As you instructed, I installed MsgFiler 3.0.5 and MsgFiler Engine 1.0.9, and that combination did the trick. MsgFiler is working beautifully now under Snow Leopard.

  25. I’ll have more extensive information on this, but Snow Leopard and Lion users of MsgFiler 3 can download MsgFiler 3.0.5 from here:

    http://msgfiler.com/downloads/MsgFiler305.zip

    Be sure to use MsgFiler Engine 1.0.9 with this version of MsgFiler.

    • Thanks Adam. I can confirm that this worked for me too. I’m on 10.6.8 with the latest updates, Mail version 4.6.

  26. I did a system update today to 10.7.5 which disabled MsgFiler. I tried to put it back into the Bundles folder but kept getting the same error message:

    “Incompatible Plug-ins Disabled
    Mail has disabled the following plug-ins:

    MsgFiler

    Contact the makers of these plug-ins for versions that are compatible with Mail 5.3 and Message 5.3.”

    What can I do? I can’t live without MsgFiler for long! ;)

  27. I downloaded MsgFiler Engine today. “MsgFilerEngine.mailbundle” shows up as a folder rather than as a package. Shouldn’t the bundle bit be set like other mail plugins I’ve seen (e.g., MailTags, Mail ActOn, etc.)?

    Jim RatliffOctober 2, 2012 @ 11:33 amReply
  28. OSX 10.8.2, MsgFiler 3.1 + Engine 1.1.2 extremely slow on IMAP remote accounts. Even with spinning pizzas, almost unusable :(

    • This will be fixed in MsgFiler 3.1.1, which is currently stuck in Apple’s approval process (they are complaining about something they never complained about before in previous versions of the app). Hopefully, the review board will approve it quickly. Stay tuned and be patient!

  29. Finally there – and works fine ! What a relief !

  30. Should I install the MsgFiler Engine if I am using the Exchange protocol?

  31. Does the MsgFiler Engine auto-update? Is there a way to check what version of the engine is installed?

    • The MsgFiler Engine DOES NOT auto-update. You can look at the current version number in the Message menu of Mail. This only applies to the Mountain Lion version of MsgFiler Engine 1.1.2.

      Note: Many times after an OS X update, you’ll have to download a new version of the Engine for compatibility purposes. I usually have new versions of the Engine out on the same day as the OS X point release updates.

  32. Any ETA on a 10.8.4 compatible version?

    Dave OranApril 15, 2013 @ 11:33 amReply



Some HTML is OK

or, reply to this post via trackback.

Continuing the Discussion

  1. [...] who routinely file to remote mailboxes will also be interested in downloading and installing the MsgFiler Engine Mail Plugin. The Engine is an Apple Mail plugin that speeds up filing with MsgFiler 3. If you’re a fan of [...]

  2. [...] the current Developer Preview 3 of Mac OS X Lion (namely filing via AppleScript and not using the MsgFiler Engine). I have filed several bug reports with Apple, and I’m hoping that these will fixed in a [...]