Users of MsgFiler on Snow Leopard and Lion are encouraged to download and use either MsgFiler 3.0.4 (the last version from the App Store for Lion and Snow Leopard) or MsgFiler 3.0.5. Engine users should use MsgFiler Engine 1.0.9.1, for the best possible performance.

The release of OS X Mountain Lion has resulted in a number of changes to MsgFiler. Due to the Mac App Store’s sandbox requirements for applications, a number of features are temporarily or no longer available in MsgFiler 3, including:

• Ability to set MsgFiler to launch at login from the application. Users will have to manually add MsgFiler to their Login Items. This ability will be added in a future version of MsgFiler 3.
• Certain Keyboard shortcuts to control Mail from within MsgFiler are no longer available when using MsgFiler 3 on Mountain Lion. These shortcuts included the ability to select next/previous messages, open/close threads, and delete selected messages in Mail while in the MsgFiler application. They are still available for users running MsgFiler 3 on Snow Leopard and on Lion when using the MsgFiler Engine Mail Plugin.
• If you are not using the MsgFiler Engine, the ability to select the next/previous Mail message has been disabled in MsgFiler running on Lion and Mountain Lion. Install the MsgFiler Engine, and this problem goes away.
• Undo/Redo filing support with MsgFiler + Engine is currently unavailable. I’m looking into the root of the problem, as the underlying filing code hasn’t changed in the Engine.

MsgFiler 3 was previously relying on its ability to communicate with the System Events application in order to send keystrokes and commands to the Mail application. Since MsgFiler is now only able to communicate with the Mail application, these features unfortunately had to be removed.

Update July 25, 2012: Mountain Lion has been released, but unfortunately, MsgFiler is still in the “waiting for review” stage in the Mac App Store.

1. There is a bug in Lion Mail, which causes MsgFiler to file multiple messages more slowly. The flip-side is that without this workaround, no messages would be filed. You can also install the MsgFiler Engine 1.0.4 plugin to get speedy filing on the next OS X release.
2. If you are using MsgFiler Engine, you will need to re-install it again. Not re-installing it may result in hanging behavior between Mail and MsgFiler.

Questions, comments, and support, please leave a response on the Support page.

However, much to Adam Tow’s credit, I must say that, within a week of the initial release, all of the problems were solved. Adam fixed the bugs that I had encountered, and explained what I needed to do to regain the ability to undo. It was stellar service and I was quite impressed.

The article also has a good discussion on the pros and cons of moving the app to be exclusive on the Mac App Store. There have been several requests to have a non-Mac App Store version of the app, but there is currently no timetable for its release at the moment.

Improvements and bug fixes in MsgFiler 3.0.2 include:

• Bug fixes.
• Better memory usage.
• Selection in mailbox list does not shift after filing.
• Fixed bug where mailbox names might be improperly truncated.
• Faster loading of mailboxes when using MsgFiler Engine.
• Fixed bug causing MsgFiler to switch to discrete graphics on certain MacBook Pro laptops.
• When no mailboxes are matched, the count says 0 instead of the previous mailbox count.
• Mailbox list updates after adding or removing excluded mailboxes.
• Notifies the user when trying to create a mailbox underneath a mailbox that contains non-ASCII characters. There is a bug in Mail’s AppleScript support that prevents the creation of new mailboxes underneath these kinds of mailboxes.

Accompanying MsgFiler 3.0.2 is MsgFiler Engine 1.0.3. When using the Engine, mailbox loading times are dramatically faster.