Sendgrid VS邮戳VS亚马逊SES和其他电子邮件/ SMTP API供应商? [英] Sendgrid vs Postmark vs Amazon SES and other email/SMTP API providers?

查看:550
本文介绍了Sendgrid VS邮戳VS亚马逊SES和其他电子邮件/ SMTP API供应商?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

能否请您就相对优点/缺点的Sendgrid,邮戳,亚马逊SES和其他电子邮件服务提供商对此有何评论?其中,你会推荐,为什么?难道还有其他的电子邮件服务,你会建议呢?

Could you please comment on the relative merits/drawbacks for Sendgrid, Postmark, Amazon SES, and other email providers? Which would you recommend, and why? Is there another email service that you would recommend instead?

附:这是目前被人津津乐道的那些清单:

Attached: Here is a list of the ones currently being talked about:

  • Amazon SES
  • Postmark
  • SendGrid
  • SocketLabs
  • MailJet
  • ElasticEmail

推荐答案

在这一天结束的时候像亚马逊的竞争对手进入市场,你到达底部。有没有办法邮戳 SendGrid 或的Mailjet 邮资或的 SocketLabs SendLabs 都将能够在价格上竞争。

At the end of the day, when a competitor like Amazon enters a market, you reach the bottom. There's no way Postmark or SendGrid or Mailjet or Postage or SocketLabs or SendLabs are going to be able to compete on price.

我不认为这一点是在价格上竞争,但在功能和服务。邮戳的路线图与林立真棒。在一天结束时,有创新和竞争,在市场赢得客户。

And I don't think the point is to compete on price, but on features and service. Postmark's roadmap is bristling with awesome. At the end of the day customers win when there's innovation and competition in a market.

要回答你的问题,邮戳等都有为SMTP缓和与公司已经在使用一个股票SMTP实现集成支持。还有洞察电子邮件产能,能够处理DKIM / SPF问题对你来说,入站处理,等它归结为你的使用情况,以及服务的优点(实际产能率为例)。

To answer your question, Postmark and others have support for SMTP to ease integration with companies already using a stock SMTP implementation. There's also insight into email deliverability, being able to handle DKIM/SPF issues for you, inbound processing, etc. It comes down to your use case, and the merits of the service (actual deliverability rates for example).

(我是一个开发人员邮戳)

(I was a developer at Postmark)

这篇关于Sendgrid VS邮戳VS亚马逊SES和其他电子邮件/ SMTP API供应商?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆