3 ms·
I agree that it's not easy to do mail right, that's my daily business. But that's also the reason why i was wondering. I probably just don't like the marketing
by buster 14y ago
I agree that it's not easy to do mail right, that's my daily business. But that's also the reason why i was wondering.
I probably just don't like the marketing speak of the website (as if it would be something unusual to do SPF or mail routing or filtering or regex, etc. etc.). On the other hand it is hard enough in this business already. You need to point out that stuff, ok..
Anyhow, i have been downvoted for a serious question. Sorry i did upset people with a question....
- Udo 14y agoI didn't downvote you, but I suspect it might have more to do with the style of the question that was maybe somewhat easy to misunderstand. I don't think anyone is upset. But I go disagree about the marketing copy. It says on the front page "Email for developers. Mailgun is a set of powerful APIs that allow you to send, receive, track and store email effortlessly." To me this conveys exactly the information I need about the service. I'm just disappointed they didn't play with the railgun analogy more, but still there is a reasonably cute mail gun gadget ;)
- ChuckMcM 14y agoI think you were getting down voted because its not the kind of comment folks come to HN to read. It sounds like from this comment that you're a competitor? ("that's my daily business") There is a lot of information on mailgun, both on HN and on the web. They've made no secret of the problem space they were going after. So Rackspace felt like they were worth acquiring, the product and customers are supported so its not a strict acquihire exit, and while the questions about sendgrid are good here (which are proxies for "What is Rackspace's strategy as a services provider really?") there clearly was enough to Mailgun to make this worthwhile. That you don't "get it" is ok but instead of the snarky "Soo they just send email?" kind of thing why not dig into their product and ask specifically about it? If it seems un-remarkable then talking about how you implement the same features and qualifying the scale of that would be helpful too.