3 ms·
The "fix" for this is actually pretty trivial, and it doesn't require using a unique subject or sender. When you send an email that you don't want to be collap
by rgrove 8y ago
The "fix" for this is actually pretty trivial, and it doesn't require using a unique subject or sender.
When you send an email that you don't want to be collapsed into any previous thread on Gmail, include an `X-Entity-Ref-ID` header with a random value.
I don't remember where I learned this. I can't seem to find any official documentation mentioning it. But it works.
- quantumhobbit 8y agoIf the company can’t figure out how to add a date to the subject line, they won’t be able to figure this out either. It’s gmails bug, but I’m amazed they couldn’t figure out hiw to implement the fix. Amazed but not too surprised given how not nimble big companies are.
- rgrove 8y agoIt's not a bug.
- user5994461 8y agoTo be fair, the header should be significantly easier to implement. There is a truckload of issues with formatting a date in 100 languages that don't apply. Incredible how Hacker News figured out the workaround in 6 hours, when they couldn't in 6 years.
- bluetech 8y agoWe've been using it for some time as well, not even with a random value, just `X-Entity-Ref-ID: null` works too. Found it through some obscure StackOverflow answer.
- davewasthere 8y agoOr changing the sender's email address. e.g. myaccount+randomstring@domain.com Otherwise a unique subject is always easy for some people.