You write that
"For messages stored in a server-based (e.g., IMAP or iCloud) mailbox, Mail uses the account associated with that mailbox — regardless of the account to which the message was sent or your preferences. That makes reasonable sense as far as it goes, and even though it’s different from before, it should yield the same result most of the time."
Most of the time, but not all. I receive project-related messages through various email accounts, and use Mail.app rules to gather them into project-based IMAP folders on my personal server. In the past, my replies were sent using the account (and From address) that the sender expects to see. Now they all appear to come from my primary account, unless I take the time to select an account from the dropdown.
Very annoying. And I should have caught this using the beta, but didn't. (Too many other bugs to worry about.)
I'm in a similar situation as Geoff.:
I have many domains that all send their mail to the same mail server inbox, and I use mail aliases for that mail account to respond appropriately.
If Mail.app is now only going to use the one "Reply to" address for each mailbox then this is definitely a problem.
Is it too much to hope that this will be fixed in 10.8.1?
It'll only be fixed if Apple know about it and recognize how it's inconveniencing people. I think if you care about it, you need to file a bug report.
Oddly, I have a server-based IMAP mailbox where I get email to multiple different accounts in two different domain names. I'm seeing the Lion behavior although I'm running Mountain Lion...
Even before these bizarre changes I struggled with the problem.
My suggestion to Apple via their feedback pages was that there should be a field in the Contacts database that associates an individual with the appropriate mail account and uses that for new mail messages and replies. An individual is either a personal contact, or a contact of one of the several businesses I run or represent. This relationship should take priority over contingent questions such as where a particular message happens to reside when I reply, for instance.
It's true that there is a very small set of individuals with whom I have multiple relationships, but these are typically friends made in the course of business and by definition they'd be more forgiving of error.
Does anybody know if it's possible to achieve this? I guess I'm looking for something that relates to Contacts and Mail as BusyCal relates to Calendar.
It's a bug.
From my own experience, Apple appears to be extremely concerned with Mail bugs so this will probably be corrected in 10.8.1.
I also had not seen this much earlier... but this is one of those bugs that can easily be missed while testing.
You write: "I have no idea why Apple made this change, whether it was intentional, why it wasn’t documented, or whether it might be changed back in the future."
Why not ask someone at Apple? Are they really that secretive that even an issue like this can't garner a response if someone in the professional Mac or wider tech community reached out to a contact within the company?
I guess the fact that doesn't take place answers my own question, but still....
I have no contacts at Apple who have anything to do with Mail, and historically, getting any answer from Apple to any question that begins with "Why" has been nearly impossible :-).
Joe
Thanks Joe. Yeah, I get it, and I'm certainly not unfamiliar with Apple's history in that regard. Still, whoever makes up the management team responsible for Mail must be aware of this (and just sticking to this example), and you'd think that they would want to address it in some way, especially once it becomes a story and the support forums are filled with questions/complaints. If it WAS an intentional change, how/why could they ever think it was a good one?
In a perfect world I guess we'd get a good answer :-)
Yeah, getting answers out of Apple is nearly impossible. Even if you can get an internal contact, they can't speak on the record, and Apple PR will never comment on something like this.
I believe the account ML uses when sending is the account you have listed in the "Mailboxes" sidebar under "Inbox". You can change the order by dragging the mailboxes.
In my testing, the From account chosen had nothing to do with the order of inboxes in the sidebar.
After further testing, I realized I was wrong—it is as you say. I've updated the article accordingly :-).
FWIW (probably not much) I brought this to the attention of a Genius at my local Apple store. He denied that anything had changed in Mail that would result in this.
As I say, probably worth not much...
The account it is defaulting to appears to be the first inbox listed in the "uber-inbox".
I've reported two bugs to apple (one for sending from "ON MY MAC" folder, and a separate one for creating a new message with the "uber-inbox" selected). They've already closed one of those as a duplicate, so I'm sure they are aware of these problems, and all indications are that they do not consider this a "feature".
I have figured this out, I think. It uses the first mailbox that you have under your "Inbox" as the default for mail that is not being created from a specific inbox. My solution was to move my preferred default inbox to the first position and now I default to that email account when I write new emails.
Two other commenters said the same thing, but as I mentioned above, that doesn't match the behavior I saw iny own testing. I have seen cases where Mail chooses an account that is not listed first.
Joe, sorry - I missed those comments. I'll observe behavior and check back if something changes. I have no mail "On my mac," it's all IMAP. Perhaps that is the variable.
I have all Tidbits communications moved (via rules) to an On My Mac folder.
This is where I am experiencing the Reply issues that Joe had discussed.
If, in the sidebar of Inboxes in Mail, I can force the reply to come from a specific email address by pushing that Inbox to the top of the list. But not all my replies to discussion groups (or associates) should come from the same email address.
So for now I will carefully look at the From address when creating a Reply. Sure hope that Apple fixes this in 10.8.1
Jerry Naples MUG
Well, I flubbed. Those who said the account used for new messages under Mountain Lion when no mailbox (or a local mailbox) is selected were correct—it's the account of the topmost Inbox. That still leaves plenty of mysteries, alas, but I've corrected that portion of the article.
For me, the real problem is listservs, and particularly listservs I signed up for back in the dot mac days. Mail has decided that though I get mail from these listservs at my .mac address, it should send all my replies from my .me address, which of course the listservs don't recognize. Obviously I can just change all the messages by hand, but it's annoying.
I'm not seeing the behaviour reported. With the preference set to "Account of selected mailbox" then all replies/forwards etc use the account the mail was addressed to - what shows in the Mailbox column. For new mail, I consistently see what Steve reported - if you select Inbox on the left hand side it uses the top account. I can drag/drop accounts to reorder them under inbox and it always chooses the topmost account. If I choose a specific mailbox on the left hand side then new mail is always addressed from that account.
All my mailboxes are local to my Mac, so as has been said, perhaps it's something to do with local/server mailbox mixes.
Off topic, I know, but it's about Mail in 10.8, so I thought I'd ask:
Does anyone else hate that the flagged mailbox is now permanently fixed near the top of Mail & that it can't be hidden as much as I do? I positively loathe it.
I noticed right away ML Mail.app's behavior had changed for the worse, and reported it as a bug. I didn't spend time running down exactly what changed, so I appreciate the explanation.
APPLE GOT THIS WRONG in Mountain Lion.
The above is just another reason I will not change from snow lepord- which allows me to use EUDORA !
Still going strong after about 20 years- can use IMAP or POP- and have virtually zilch problems even when using multiple mail addresses which are clearly displayed and easiloy changed from default and always trigger to return to sender plus return recipts
OH how I wish a GOOD update were available with same features
Dear Eudora! Started out as a Classic (OS 6) app in 1988, still works (for me) as well as ever in Snow Leopard, and can be included among a number of reasons why some 45% of Mac users never bothered with OS X 10.7.
http://tinyurl.com/cnyeomhI'm one of those 45%, but because I do anticipate eventually moving beyond Rosetta I've lately been trying to come to terms with Mail app. It's not been easy, and especially not after 16 years with Eudora, during which I've evolved a fairly complex and perfectly reliable arrangement which includes six accounts, over 100 mailboxes, and well over 200 filters.
Aside from Joe Kissell's TCo books on the subject (thank you, Joe!), the most helpful resource I've found is Indev software's MailTags, which adds to Mail app at least a few of Eudora's most essential organizational features.
Also encouraging is that MailTags (like it's associate app, MailActOn) is OS X 10.8-compatible, even as more than a few old-hand developers are struggling with Apple's increasingly restrictive "sandbox" policies.
So until this I was feeling like I might be making some headway, but now? Looks like yet another reason to be pleased to have spent bits of the past several years evolving an alternate environment in Gmail and Mailplane.
Fact is, I now mostly prefer Gmail's tag-and-search concept, for many of the same reasons outlined in Adam's excellent 4-part series on Zen and the Art of Gmail
http://db.tidbits.com/article/12036, so I'm interested in Mail app really only because I spend several months each year on a connection so slow that any web-based interface becomes tedious.
From that perspective, my favorite parts of Mail app are its threaded messages and MailTags-enhanced smart mailboxes, and by combining those features I've come up with a customized variant of Mail app that works quite well. It's not Eudora, but it's pretty to look at and does do at least a couple of things -- notably Unicode and HTML -- that Eudora never quite understood.
So my coming to terms project has been coming along, but this Mail app reply-from thing is a broadside to every common-sense perspective I can imagine. One can only hope it's an unintentional bug that will be quickly remedied. I'm not holding my breath, but will join those sending feedback to Apple.
I've always felt uncomfortable with the way Mail handles the default mail box. It has always seemed that if I didn't constantly pay attention to the FROM account, I could easily get caught sending a business message from my personal account and vice versa. Hope this gets sorted out soon.
One semi-related question... Does anyone know why you cannot drag & drop a piece of text to the SUBJECT bar in Mail? Is there any logic behind this odd behavior or is another long time bug in Mail?
I just upgraded to Mountain Lion and i can confirm the same issues. Especially troubling is that, as others have noted, when incoming emails are filtered into local folders, ML Mail completely forgets what account they should be associated with, and then when one then replies to those messages, the "From" address almost invariably comes up as the wrong one (at least in a situation where a user has multiple accounts, as i do).
I just spent a good long time on the phone with a senior-level support specialist at Apple who was immensely helpful and determined to work with me to find the cause. I let him view my screen and I also sent him a big dump of my configuration files, which he's forwarding to the engineers in the hopes that they can find a solution. BTW, i also directed him to this article, so with any luck Joe's well-written description of the issues and the testimony of all you good people will be included in Apple's considerations.
One thing that I have noticed is that if you have multiple emails associated with one account (like user@me.com, user@mac.com and user@icloud.com) you need to list all of those emails in the account settings, otherwise your email will always be sent from the account you do have listed.
Email Address: user@me.com, user@mac.com, user@icloud.com
In Preferences => Accounts => Account information.
I haven't noticed the other "on My Mac" related issue because none of my email is stored locally, it is all in server side IMAP folder.
AFAIK, this is how it has been for a while -- you have to have all of the addresses listed otherwise I believe it picks the first one..
It won't allow you to put a from address that you'ven't said belongs to you. The opposite is fraught with huge huge problems.
I am surprised nobody here is also talking about Mail's vanishing cursor bug.
If I go to another app while I am composing in Mail, when I return to the email I was working on the cursor has vanished. I then have to click in the message area of another blank email to get the cursor to return. I keep a shrunk down blank email always open now for this purpose. Everyone I know has this bug in their Mail and there's more on it here...
https://discussions.apple.com/thread/4156726?start=0&tstart=0
I'm not able to duplicate this behaviour at all on my machine. Obviously, a large number of people from your experience are encountering it, but it is equally clearly not a bug that is occurring for every Mac running Mail under Mountain Lion. Best of luck solving it though. Let's all hope that 10.8.1 covers a multitude of sins (I myself have had nothing but problems with Mac to Mac screen sharing since upgrading to Lion).
Makes perfect sense.
If you are in an account, mail is sent from that account.
When did it stop being the users fault that they cannot figure out which mail account they are in? It's not that hard.
It's a problem if you receive mail from many accounts but store the messages in a central location (or in another account). Many mailing lists, for example, accept email only from certain addresses. It used to be that you didn't have to think about that—just reply, and the message is being sent from the right address. Now you have to second-guess Mail every single time.
There is no second guessing.
Just look.
Sure it would be nice if you didn't have to think, but who would be blamed if something went wrong?
This way the onus is on the user to ensure they get it right. No doubt it will improve over time, but the user should always be involved in the decision making.
Sorry, but you're ignoring the fact that Apple changed something that was working pretty well to make it far more inconvenient. Maybe it doesn't bother you, but it's enormously irritating for lots of people, and it's not helpful to say, essentially, "just get over it and pay more attention."
I just upgraded to 10.8.1 and this behavior has not been fixed.
Actually, I think Mail got it right. How is it suppose to know the account you received email from if it was addressed to an email alias or group like customers@somebigcompany.com? What if you were BCC'd so your email account isn't actually in the email headers?
How did Mail perform before Mountain Lion if there was no explicit email address it could match to your accounts? Would it just guess?
Sounds to me like they improved the feature by taking away the guess work for situations like these and made it more reliable and predictable.
I think the only logical thing Mail.app can do is reply from the address that the account is sitting in. That makes a whole lot of sense to me.
I admit, I don't have a On My Mac local account and I reply from the account I was addressed. I don't understand why some people are moving messages to a local folder. Mail works great without a network connection for me. It caches all of my messages so I can see them when I'm not connected
The pain point here isn't the From address, it's the From account. Prior to Mountain Lion, Mail based its decision on the _account_ in which you received the message, not the _address_ to which the message was sent. That was predictable; its current behavior is much less so.
FWIW: before I read this article I filed a bug report.
IMHO this is a bug, since nobody can figure out a logical reason for this non-deterministic behavior.
I also left feedback and encourage others to do so.