If no text portion of an email is submitted, automatically make one from the html portion. This should help with deliverability. The parse incoming seems to do this now according to the documentation so you may already have routines to do this.13 votes
When designing HTML emails, having to use inline styles (style="xxxx") instead of CSS classes is a right old pain.
There are tools and libraries that can take a HTML document, and automatically 'inline' the CSS styles. E.g. http://beaker.mailchimp.com/inline-css
It would be AWESOME if there was an option to apply this transformation to a HTML email before it gets sent....10 votes
Create HTML (and text) templates within Mailgun. When sending an email using API/SMTP, reference the template instead of sending the message body every time, and include replacement variables.
This would allow us to manage email templates from within Mailgun, instead of in the code base. Similarly, allow us to combine different stylesheets with these templates so we can make a single CSS change, and apply it to all email templates (instead of editing every email template).1 vote
Thanks for the feedback here! We’re currently working on implementing a templating feature where you can upload/create/store a template on the Mailgun platform and simply reference the template ID when sending a message.
Please consider providing the timestamp, token and signature as http headers. Some frameworks such has JAX-RS provide the ability to validate an incoming request via interceptors. This is difficult to do with form data as it is processed later in the request.
Ideally this would be done similar to Twilio https://www.twilio.com/docs/security
Based on this we could verify the request before actually decoding the form data.3 votes
- Don't see your idea?