Maildown is a transactional email API built for developers - it does away with the WYSIWYG editors and clunky interfaces of some of the bigger email providers, instead focusing on its simple and scalable REST API, which allows you to create emails using markdown syntax
Not necessarily in that way. It might be easy for you this way, but does it break the product for your users?
I.e. lets say I do indeed not use it for transactional mail, but send a newsletter. How do I reliably fulfill my obligation to remove a customer from my newsletter database if they request so, if your service adds an unsubscribe link that doesn't inform me about the user request?
If I'm not using it for newsletters, you're saying I need a second transactional email system to communicate with the customers that pressed your opt-out link but I still need to communicate with?
5 comments
[ 0.29 ms ] story [ 18.0 ms ] threadMaildown is a transactional email API built for developers - it does away with the WYSIWYG editors and clunky interfaces of some of the bigger email providers, instead focusing on its simple and scalable REST API, which allows you to create emails using markdown syntax
Thanks for looking, Chris
I.e. lets say I do indeed not use it for transactional mail, but send a newsletter. How do I reliably fulfill my obligation to remove a customer from my newsletter database if they request so, if your service adds an unsubscribe link that doesn't inform me about the user request?
If I'm not using it for newsletters, you're saying I need a second transactional email system to communicate with the customers that pressed your opt-out link but I still need to communicate with?