For what it’s worth we had a similar requirement to be able to send “rich” emails from both our webservice, and offline services in our infrastructure. We decided to leverage Mailchimp templates sent through our normal mail server. We have an internal email service (which our other services consume) that grabs the mailchimp template requested , puts in the info for the email , and sends the email through our normal email server.
The major advantage is that you can get nice mailchimp templates created through elance/odesk/etc basically overnight for ~$40. This allows us to have good looking email templates whenever we want while leveraging a commoditized layout system (mailchimp).
We don’t actually send any email through mailchimp right now, most of our emails are one offs like “welcome”.
Jeff MacDuff
CTO & Co-Founder, Buddy
Email: je...@buddy.com
<?xml version="1.0" encoding="utf-8"?> <Config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <DefaultScaffolders> <Default DefaultName="CustomScaffolder" ScaffolderName="T4Scaffolding.CustomScaffolder" /> <Default DefaultName="CustomTemplate" ScaffolderName="T4Scaffolding.CustomTemplate" /> <Default DefaultName="DbContext" ScaffolderName="T4Scaffolding.EFDbContext" /> <Default DefaultName="Mailer" ScaffolderName="Mailer.Razor" /> <Default DefaultName="Repository" ScaffolderName="T4Scaffolding.EFRepository" /> </DefaultScaffolders> </Config>