AuPhalanx wrote:
I hope this helps you to understand our plight.
I understand the issue well enough. The problem is that Apple Mail has no way to tell if there really is an SMTP associated with that account. In the case of fake/forwarded addresses, there would not be any associated SMTP account. When you move an email message out of the inbox, it is no longer assocated with that inbox. When you want to reply, it just picks the best server it can find.
I tried your procedure on my Lion VM. The Lion behaviour is identical to Mountain Lion. I suggest using IMAP and smart mailboxes instead. If you need to archive messages, you can do that every few months. The smart mailboxes will still find them. That way, if you need to respond to a message, it will pick the correct server. There is much less chance of responding to a message three months old and, if you do, you can pick the correct server manually. That is the way I have always used Mail and it has never been any problem.
If you want to change the default e-mail address, just drag your preferred account to the top of the list of accounts in your Inbox.
In the situation you described, where you immediately pull messages and put them into archived folders, it would be possible to track down the correct outgoing e-mail account. That would be an enhancement rather than a bug report. I admit that I did not try any POP accounts in Lion. I haven't used POP for many years. If you used IMAP accounts, you could do that on the server and everything would work as you expect.
So, I do see an area where an enhancement is possible. I don't know if it is justified because it is an enhancement which would seem to apply only to people doing immediate archives with POP accounts which are not very popular anymore. All of Apple's future efforts are going towards Exchange accounts. There, I admit it - Microsoft won the e-mail wars. You can quote me on that.
I wouldn't get my hopes up for a bug report in duplicate state. Duplicate just means someone else reported it first. It does not mean Apple is ever going to do anything about it. I just did the same regression test that an Apple engineer would do. According to my test, it works the same way in Lion. Ergo, it would be an enhancement not a bug. You probably aren't going to see that in 10.8.2. According to the rumor sites, 10.8.2 just has bug fixes and things that were supposed to be in 10.8 but didn't make it.
As with everything in Mountain Lion, I suggest you explore some of the new features that are now available and re-think how you have been doing things. There is probably a much better way to handle things now.