Move to Predicted mailbox

After updating to 10.12.2 Beta (16C32f) Move to Predicted Mailbox in the contextual menu is working as it should with Predicted Mailbox being replaced with a logical destination most of the time. This is definitely an improvement for me now that it's working.

Thank you. I hope 10.12.2 will be available for all of us soon

Perhaps you can expand on how it "works" and what you meant by "most of the time"?

I am an apple 3rd part dev and just updated to 10.12.2 beta as well and mail has the same behavior as now in 10.12.1: i.e. Predictive Mailbox does not show where I las saved an email: I have to go to Menu > Messages to see where I last saved message (Move or Copy) or just "trust" where I left it with OPT-CMD-T.

Any more detail? i.e. are your email accounts iCloud, private, etc?

I have also been a 3rd Mac party dev since 1986. By "works" I mean that it will allow you to move the selected email to a folder that makes sense based on the email's address. By "most of the time" I mean that if Mail can determine a logical destination for the email based on it's attributes - it will. My email accounts are iCloud, Gmail and my ISP's private IMAP accounts.

It's absolutely utterly useless, not to mention that the absence of the previous format where you could move to the last used mailbox makes for far more work. Bloody stupid.

This is what I noticed too, so I guess it is a bug.

I just re-installed Sierra on top of the existing OS (without doing a clean install), and magically it works...

Yes, I can confirm that performing a clean install solves the issue and than it works like in iOS, beautiful!

YES! You are absolutely right! This has been driving me crazy all week, and I so hope Apple fixes this.

The concept could be great, but for now, the lack of a predicted mailbox all the time or the old function of move to last folder is driving me insane!

I've submitted a bug to Apple through Feedback Assistant. You are all correct. The feature works properly if you do not have the mail message selected. If you have the message selected and you are using Office365 servers you will get a message that the mailbox is not available.

Me too, made an install iver the current system and itvworks

I agree. Right click on any other mail other than the one selected, and the option is enabled. Sure a bug. Frustrating if you are moving a bunch of stuff and you will have to resort to other ways to getting things done.

I noticed this happened for me in the last couple of days, although to be fair I don't use the feature that much so it may have been longer.

The right-click context menu has the grayed out "Move to Predicted mailbox" regardless of which message I right-click on or which one is selected.

However what has also happened (which I've never noticed before) is it's in the main Messages drop-down menu with an option-command-T shortcut. I'm unlikely to use the keyboard shortcut though as I won't likely remember what the last folder I copied something to is without looking, which is why the contextual menu was so useful.

I'm not going to do a reinstall just for this issue so hopefully another update will fix it. Don't understand why Apple has decided to be so flippant with well-used/standard UI elements and commands nowadays.

Oh now that is really interesting. I hadn't noticed that the menu item really is predicted/contextual when it works.

It must look at the sender and predict which is the most likely folder. So that possibly means for regular senders which always get sent to the same folder, the keyboard shortcut would work well even without remembering the last mailbox.

It's just frustrating that you have to be in another message (and actually click on the message window panel if you're in column view) before you can move a different message. Why not the one actually being read, as surely that's the one you want to deal with?

This is clearly a bug... works when the target email isn't selected... sometimes works when multiple emails selected and at least one is flagged as unread.

I use this 100+ times per day. Can't wait for 10.12.2 if that truly fixes this issue.