MsgFiler Engine

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

MsgFiler Engine is required to get the best performance out of MsgFiler on Yosemite/Mavericks/Mountain Lion. 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.

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.1.1 or higherMsgFiler 3.1.1 or higher MsgFiler 3.0.4MsgFiler 3.0.4 or 3.0.5
Download MsgFiler Engine Version 1.2.2
(Yosemite, Mavericks, and Mountain Lion)
Download MsgFiler Engine Version 1.0.9.1
(Lion and below)

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

Beta Releases – Updated November 20, 2014

MsgFiler Engine 1.2.3b1 is available for OS X Yosemite 10.10.2.

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 or higher, 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

I upgraded to Mavericks and filed messages keep reappearing in the original mailbox (Gmail account)!
Did you hide the All Mail folder in Gmail’s web settings? If so, you will need to reveal this mailbox in IMAP for MsgFiler to work properly. See this article on TidBits for more details.
Mail on OS X Mavericks/Mountain Lion has disabled the MsgFiler Engine plugin. Filing is slow again in MsgFiler 3!
Update to MsgFiler 3.1.2 and install the latest version of the MsgFiler Engine
Filing is so slow after upgrading to Mavericks/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.
Version 1.1.4 – 2013-09-12
Compatibility with OS X 10.8.5.
Version 1.1.5 – 2013-10-21
Compatibility with OS X 10.9.
Version 1.1.6 – 2013-11-08
Compatibility with Mail Update for Mavericks.
Version 1.1.7 – 2013-12-16
Compatibility with OS X 10.9.1.
Version 1.1.8 – 2014-02-25
Compatibility with OS X 10.9.2.
Version 1.1.9 – 2014-05-15
Compatibility with OS X 10.9.3.
Version 1.2.0 – 2014-06-30
Compatibility with OS X 10.9.4.
Version 1.2.1 – 2014-10-20
Compatibility with OS X 10.10.
Version 1.2.2 – 2014-11-17
Compatibility with OS X 10.10.1.

82 comments

    1. 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.

    1. 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.

  1. 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.

    1. 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.

  2. 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!

  3. 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.

  4. 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.

  5. “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?

  6. 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?

  7. 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.

    1. 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.

  8. 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.

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

  9. 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

  10. 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

    1. 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?

  11. 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).

  12. 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.

  13. 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.

  14. 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.

  15. 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! ;)

  16. 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.)?

  17. OSX 10.8.2, MsgFiler 3.1 + Engine 1.1.2 extremely slow on IMAP remote accounts. Even with spinning pizzas, almost unusable :(

    1. 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!

    1. 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.

  18. Any ETA on the engine for Mail 6.6 that was released today (9/12/13). I rely on MsgFiler all day. Looking forward to the update.

  19. The 1.1.4 engine when downloaded contains a bundle dated 6/27/13, not 9/12/13. Is this the correct version, properly updated for 10.8.5?

  20. Yes that’s the correct version I usually don’t release the final version until the OS X release is actually available for the public. 1.1.4 was just lying in wait since June. On the other hand, the Mavericks beta required some reworking so I have a beta of that plugin out before the final GM of 10.9.

  21. 1.1.4 seems to be having some problems with 10.8.5 (or it could be an issue with Mail.app) But, in any event, I’m finding that I move messages, and they appear to move, but when switching mailboxes or quitting and reopening mail, all the messages that I had moved, reappear in the inbox. Same behavior on two separate machines…

  22. Installed Mavericks GM and the 1.1.5b7 engine, but Mail 7.0 keeps disabling it every time I try to restart after reinstalling the bundle. Is there something else I need to do to get this to work?

  23. Hi Adam

    Apple just released a new GM build (13A603), which breaks the plugin (because of a new Mail.app version).

    Hoping for at quick update once again :)

    Thanks

  24. MsgFiler stopped recognizing the Filer engine today. Completely removed and reinstalled both MsgFiler AND the latest version of the engine. MsgFiler continues to believe that I don’t have the Engine installed….and of course as a result is very slow.

    Running OS X 10.8.5 and mail 6.6(1510). I don’t know why this started happening, but I can’t stand dealing with email without a speed MsgFiler. Please help!

  25. Clicking on the “Download MsgFiler Engine 1.1.5″ does not download “MsgFilerEngine.mailbundle.” Instead, it downloads “MsgFilerEngine115.dmg.” Not sure what to do here..

  26. Just downloaded message filer for the first time. 10.9/3.1.2. I followed the instructions for downloading and installing the engine. Do dice. Every time I click “Use Engine” it tells me that the Engine isn’t installed. It is. I have run the terminal program. At the moment the filer runs–very slowly–but it doesn’t remove the messages from my “inbox.” Please advise.

    1. Scratch that. I didn’t realize that the downloaded engine had to double click on the dmg file and drag THAT to the library. Everything working now. And it’s pretty darn amazing. This is going to make life better. Period.

  27. Dan: I am looking into a problem some people are having getting Mail plugins to be recognized in the first place by Mavericks Mail. Stay tuned for a resolution.

  28. Adam, performance seems to be very slow now that I installed Mavericks. Any reason for this? Will there be an update released soon? I do have the latest engine installed, version 3.1.2 build 25.

    1. Can you confirm that the Engine is actually installed and activated?

      If so, MsgFiler’s title bar will read MsgFiler + Engine

      Can you describe how performance is slow? Are you seeing messages disappear after filing, reappearing, and disappearing after a few seconds? If so, this is a Mavericks issue currently, not a MsgFiler one.

  29. Hi – As of the Nov. 8 Mail update the plugin is no longer recognized. It was disabled on the first restart of Mail. Downloaded and reinstalled the plugin. Mail doesn’t complain about it and it doesn’t get moved to the Bundles (Disabled) folder, it simply doesn’t work. Seems as though it’s just ignored/not recognized. Great product btw – thanks for all the ongoing effort!

    1. Indeed – I tried this morning and it didn’t seem to work. Just started over, grabbed a fresh version and now it’s fine. Likely user error due to lack of coffee earlier. Thanks!

  30. Love the program…I have been using it since first offered :)

    Messages filing extremely slow..

    I Now have MsgFiler 3.1.2 installed on Mavericks 10.9.1 Trying to install the Msgfiler 1.1.7 engine..

    I cannot get the terminal to accept the 2 commands..

    Need help!

  31. I just loaded Mail 7.1 and it removed the MsgFiler plug-in. I depend heavily on MsgFiler. Do you have an update to handle this? Please?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s