REST-based email and multi-part MIME

Hello,

I'm currently migrating our SOAP-based emails to the new REST-based ones. I'm finding that there is no longer a mechanism that HTML and a text version are grouped together, you need one template for HTML and one version for the text one. On the web its not such a big deal as the web can render both emails as a text string and combine them into one email. But sending from the client is our issue - I don't see how to avoid having our staff sending two or polling the customer for which version to send.

It seems weird that this worked in the SOAP architecture and has been taken away with the newer version. I understand wearables like Apple watch display text versions so the argument for just doing away with text versions all-together seems to have lost some steam. Additionally I'd expect there to be some accessibility issues with using only HTML emails.

I'm just wondering what others are doing about this.

Thanks,

Sean

Parents Reply Children
  • Thanks for the response Troy but how would that work within the context of a REST template that would get called from the client?

    Are you suggesting using one "master" template to render two other "sub" templates - one HTML and one text - and then construct the email and send it? If so, what do you do send back as the contents of the "master" template? I'd think triggering a send to the "master" template from the client would send the multi-part email as part of the C# code (YAY) but then the master's rendered contents (empty?) would be sent in a second email.

    Hopefully that question makes sense.

    Sean

  • I have never done it before, but it looks like it can be done with the limited searching I did on it. It appears that you would be duplicating all of your razor output. One for the HTML and the other for Text. The receiver determines which format. Chrome, Firefox, and IE tend to favor HTML all the time. Other email clients have options to filter HTML and only use text. 

  • Hi Troy,

    I understand that C# can create and send multipart emails, I've done that.

    Where I'm getting stuck is how to make it work within the framework of how the Tessitura front-end client fetches and sends Razor templates from the order screen. I'd like one send action to ultimately deliver both versions together and don't see how to make that happen.

    Sean