> For the complete documentation index, see [llms.txt](https://docs.msgfiler.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.msgfiler.com/support/plugin/migrating.md). # Migrating to MsgFiler 4 Support has ended for MsgFiler Classic. If you have upgraded to macOS Sonoma and are lamenting the fact that Mail Plug-Ins have been removed from the Mail app, you should purchase MsgFiler 4. There are many new features in MsgFiler 4 that users have requested over the years, including: * favorite mailboxes * recent mailboxes * ability to create new mailboxes from within MsgFiler * configurable default action * exclude mailboxes * match on mailbox names only * restrict search to selected accounts * full keyboard access ## Differences Between the Application and Classic Plug-In The previous version of MsgFiler came in the form of an [Apple Mail Plug-in](https://msgfiler.com/support/mail-plugins-explained/). Because the Mac App Store guidelines restricts plug-ins, MsgFiler has been rewritten to be a standalone application that communicates with Mail via [AppleScript](http://en.wikipedia.org/wiki/AppleScript). Differences between the plug-in and the application are noted below: * **Hide Offline and Inactive Accounts**\ MsgFiler 3.0 does not have the ability to determine whether a mail account is offline or inactive. * **Mark as Read**\ Due to AppleScript performance issues, the Mark as read feature has been removed from the application. From within MsgFiler, however, you can press `Command-Shift-U` to toggle the read/unread status of messages before you file them. * **Loading Mailboxes**\ The plug-in, by virtue of being integrated with Mail, is faster at loading and reloading of mailboxes. * **Filing To Remote Mailboxes**\ MsgFiler’s performance is slower than filing with the plug-in because MsgFiler must use AppleScript, whereas MsgFiler Classic has access to an internal method within the Mail application for filing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.msgfiler.com/support/plugin/migrating.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.