<p>Mailjet just released its Go Wrapper for its API. Sending all your emails, reliably on our infrastructure with Go as never been easier! <a href="https://www.mailjet.com/blog/go-go-mailjet/">https://www.mailjet.com/blog/go-go-mailjet/</a></p>
<hr/>**评论：**<br/><br/>lantins: <pre><p>I think this is more an announcement, but do you (or anyone else) have any thoughts on mailjet.com vs mailgun vs sendgrid etc? I've often just fallen back to Postfix, but then I'm not doing a massive amount of emails (or anything newsletter related).</p></pre>arnaudbreton: <pre><p>Thanks for your interest in Mailjet. I work for Mailjet, where I lead developers relations but I'll try to be as objective as possible.. </p>
<p>Mailjet has been built for all kind of emails in mind (from transactional and marketing) from day one, and with global deliverability in mind. Our Api first approach and powerful tools enable us to provide you with all what you need to send great emails, based on a fair and flexible pricing. </p>
<p>If you have more specific questions, I'll be more than happy to answer them!</p></pre>lantins: <pre><p>n.b. I've not investigated Mailjet (yet), but I'm trying to dig a little more then I can through normal browsing :)</p>
<p>This may be a dumb question/comment, but isn't every every mail sending API... API focused/API first? "here blud, send this email, plzkthx", "is my mail bouncing?"</p>
<p>I've been looking at whats out there as of late, but they all seem the same, the biggest draw for me (as a developer) between them all has been whoever had the best Docs / Integration with my favoured language (so I'm pleased to see a Go wrapper :)) and perhaps stats second. Ensuring delivery is a must and I don't expect anyone would say they offer otherwise.</p>
<p>I guess, I'm just having a hard time differentiating between the different options.</p></pre>arnaudbreton: <pre><p>Agreed that every modern ESP on the market is providing an API, letting you trigger emails and retrieve all kind of information and stats about them. These APIs are most often first class products, meaning they come with decent documentations and libraries for the most popular languages / technologies. </p>
<p>What I meant by saying "API-first" at Mailjet is that our API is also the one powering our own system. The API you're using as a an external developer is a subset of what our own developers use everyday to build our front-end and internal softwares. We "eat our own dog food". This ensures you're working with an API which is improved every day and built for the scale and the use-cases you look for.</p>
<p>About deliverability, it is something that can vary from one ESP to another, depending on where the majority of your users base are located, the content you're sending, the way you're collecting the email addresses, etc. It is a critical part of our business and this is why I emphasized more about it.</p>
<p>I'm more than happy to continue this discussion in private and help you figuring out how Mailjet could help you send better emails. You can reach us at <a href="mailto:api@mailjet.com">api@mailjet.com</a>.</p>
<p>Best,
Arnaud.</p></pre>lantins: <pre><p>Thanks Arnaud :)</p></pre>anonfunction: <pre><p>I wonder what powers the underlying API at mailjet. Is it, or parts of it, in Go as well?</p></pre>arnaudbreton: <pre><p>Yes, growing parts of our system (system tasks, backend) and our API are now powered by Go. We'll publish more about what we do with Go in the coming months. Thanks for your interest in Mailjet. Stay tuned!</p></pre>
