I’m working with a client who wants to create email notification messages. Prior to sending the message, they want us to save the HTML and be able to resend the message in the event that the email bounces or is never sent. What would be the best way to approach this?
Hello Lou,
Unfortunately the html generated by the Email Context cannot be saved, only the one generated by the Web Context can be. In a situation like this, what I think most implementations would do is to just re-send the email from the original data instead of attempting to save the contents of an email and re-send it. I mean, it takes so little time to generate, setting up a whole caching system (which, while it’s available in email clients, is generally not something you’ll find on back-end email systems) seems like a lot of trouble for very little benefit.
It means you’d need a tracking number in the email subject so that you know what email it refers to and where it’s cached and an interface that can let you re-send it anyways… Might as well just use Mandrill, I’m pretty sure it handles this (and handles bounces and tracking and such).