Initial MsgFiler Responses and Bugs

The initial response to MsgFiler has been pretty good. That said, a number of users have been encountering a couple of errors when using MsgFiler. For instance, if you’re experiencing the following error dialog:

Can’t make current application into type anything (-1700)

You’ll want to wait for the next release. People who have been sending me this error all seem to have MacBook Pros, but I think the issue is with how the mailboxes have been configured.

Another issue that’s cropped up is handling Unicode characters. I’m currently identifying the source of these problem and will get a fix out soon!

Update: Here’s a list of bugs that we’ll be resolving in the next few days:

I get this error, Can’t make current application into type anything (-1700), when I try to file a message

I think the issue is due to the way the user’s IMAP server has been configured. MsgFiler builds the list of mailboxes from the Finder directory structure (since AppleScript is so slow). For people who have their IMAP servers configured in a particular way, this causes MsgFiler to barf when searching for a mailbox. This is why some people have the problem and others do not.

I get another error when trying to search for mailboxes.

If you have a mailbox with double quotes in the name, the MsgFiler may not work entirely. We are looking into the problem

I have mailboxes with accented characters / Unicode characters that can’t be found in MsgFiler

This is another problem that we are currently looking into

MsgFiler does not load properly into Mail. I can’t see the Move with MsgFiler menu item

This may be an incompatibility with other third-party mail plug-ins. We’re looking into it!