Ungrouping a Conversation in Mail

Same problem for me. I have two conversations, with two different subjects and recipients that have been grouped together with no apparent reason why.

Impossible to separate them.

Only solution is to split ALL conversations, which I hate.

Also the same problem for me in Apple Mail 8.1 under OS X Yosemite 10.10.1. A number of unrelated email messages to multiple contacts with entirely different subject lines are being grouped into single conversation threads.

Sometimes these messages are days apart and the thread will include new messages with distinct subject lines. Meaning, they don't all share an RE: or FW:, for instance, or any remotely similar wording. They will also be sent from different accounts, sometimes messages from my work account and other times my personal address mixed into the thread.

I haven't yet found any examples of people being included in replies that shouldn't be or of them receiving content in replies that would otherwise normally be in a separate thread.

I'm not sure what criteria Mail uses to group conversations into threads but something is off in Yosemite for sure. I haven't noticed this behaviour under Mavericks or earlier OSs.

This bug really needs to be addressed by Apple. I hope they're following this thread.

Same for me: 176 completly unrelated mails spanning more than four years grouped together.

I am experiencing probably an extreme case of this.

Nothing seems to be the same. The only common feature is that the sender/recipient is me.

The subject lines are different, none of the other sender/recipients overlap, AND the languages are different.

For that matter, the writing systems are different. The other language doesn't use alphabet. No shared workplaces. It's very annoying.

Additionally, recently some Mac users claim they are not receiving my email. I am suspecting that my mails are getting lost in this type of situation on their Macs.

I agree with Hypraktiv. Three years and the problems gets worse before it gets better. Totally unacceptable.

This is a different Apple, no doubt of that. Quality has clearly come down

I decided to deactivate the grouping future

It is 2015 now and this issue still happens, I really think Apple Engineers are having this issue when they are using the Mac...and still nothing changed. I would really like if there is an option says "Organize by Subject" other than the "Organize by Conversation". Please help.

Thank you, it did help.

:-)

I hate grouped mails, more so when they are grouped in a meaningless way.

Although, thanks to this crazy grouping by Mac mail, I once jumped into an old and forgotten mail, which I wrote two years ago, and it proved very useful in another context.

So, thank you, Mac, for being so stupid :-)

Go to Mail > View > and uncheck "organize by conversation". You may have to do this on each mail box, (inbox, trash, etc)

I came on here with the same issue. I decided to uncheck the group by conversation in the View menu. I noticed then that Mail highlights the emails from same conversations in blue, which is definitely better than what it did before...grouping 81 completely unrelated messages together. So, it's better for me for now, although I would still definitely prefer grouped messages from the same conversation.

Try unchecking "Include related messages" in Preferences -> Viewing. That sort-of fixed it for me in 10.10.2

Frank

Same issue here with unrelated emails being grouped in conversations since Yosemite. On latest 10.10.2 update and nothing mentioned in this thread has worked.

I've tried all the suggestions, but nothing happened. I even Rebuilt my mailbox, but now I have three different senders all under the same conversation, even though they have different subjects and email addresses.

Apple, please figure something out!!

in mail go to view and untick organise by conversation. it's as easy as that.

I'm resisting the urge to say something sarcastic, but if you go back and actually read the whole thread, you will see that everyone is aware that we can simply turn this feature off. The point is that we WANT the feature to be on - we just want it to work correctly. The comments in this thread are all simply pointing out that people are still experiencing this bug, years after it was initially reported, and we are extremely frustrated with Apple for ignoring us and not fixing it.

I am a software developer with 34 years of experience writing software, and I'm saying that there is simply no excuse for Apple not being able to fix this issue in the many years that it's been reported by various users. It would be rather easy to fix as well. Give me a day, and access to the source code, and I'll do it myself. It makes me wonder how they spend so much time doing market research for new products (presumably at great expense), but they won't listen to customer complaint constituting FREE advice on what customer actually want from their products. (Do you hear this, Apple?!?)