The purpose of our association s a feature that we have -- storing emails associated to a business entity.
We have yet to build this yet, but the intention is to have a service that runs on our server, that can monitor any replies the user receives that originated from that e-mail chain, so that we can store each of those replies against the business entity that was associated.
One idea is to obviously have a hidden tracking link or meta information that can be scanned. Because the person who replies to the email will likely just hit reply and the reply would contain that piece of meta information. Once the email comes back, our background service could scan for this meta information and store this back into the associated entity.
That would work in most cases.
The other way was to form an association of a threadId to the business entity. And have the service actively look at all threads that have an association, and look at all the messages, and see which ones haven't been copied over yet.
The problem with this I guess would be, when you start an e-mail off, there probably won't be a threadId yet and only a messageId, like what you have said from the destroy event's callback.