it used to be disabled, and then people complained when they changed the archive granularity, and couldn't re-archive...I suppose we could check if clicking archive would do anything before deciding to enable the button, though I think we'd want to punt in the case of a large multi-selection...

I think I may have regressed this in bug 542998. One solution (which I'll happily work on since it's my fault) would be to just enable cmd_archive when you have selected messages in the archive folder but that folder doesn't match whatever your current archive scheme is.

Created attachment 525333[details][diff][review]
Enable archiving even in the archive folder [checked in]
This does the opposite of comment 0, but fixes the use case in comment 1, which is probably a net gain. Having a smarter solution in place would probably be nice, but at the very least, I want to make sure I don't regress this behavior for 3.3. If you think tests are necessary, let me know and I'll add some.

If you have the archive settings such that it keeps your folder structure within the archive, and then you accidentally re-archive a message, it totally destroys the folder structure. In other words, the messages are moved recursively into new archive folders within the current archive folders. This is quite problematic for me. The archive button should either be disabled within the archive folder, or something should be done to prevent recursive archiving folder creation.