Personal i don’t use anymore, but yes for me that was the reason
Yes I chose it because it was recommended and it sent the most email for free out of the recommended services. After discovering there is no clear way for EE to communicate bounce info to Discourse, I plan on making the switch to Mailgun.
EE should be removed from the recommended services IMO due to it not fully integrating with Discourse like the others do. Or at the very least a disclaimer should be added next to the recommendation.
Ran into this same issue over last two months and now regretting using Elastic Email without knowing this limitation.
Just created a pull request for this:
Looks like their pricing also changed completely
100/day limit
Just created a PR to remove it completely as it lost the only benefit it had:
Their paid plans aren’t widely out of line with the others listed. Those suggestions aren’t only for small communities interested in a free ride.
Would recommend updating their details to reflect the change, rather than unilaterally deciding to remove them completely.
(as mentioned on GitHub)
I understand, however as mentioned in the for-removal section and in this thread, the main issue with elastic is the double-footer (which also causes re-subscribe issues); as such I don’t think it should be considered as a recommendation (unless that issue changes).
I believe that the main reason it was kept on the list is that of the generous free plan; given the multiple integration issues.
I’ve filed an alternate PR with the amendments I suggested. Unless @codinghorror asks it be removed all we need to do is update it as-is.
Based on the new severe restrictions to the free tier, Elastic is now sorted at the bottom in the docs, whereas it used to be at the 
so this issue should naturally resolve itself over time.
还有 Mailjet，每月最多提供 6000 封免费邮件。
我对 Elastic Email 很感兴趣，因为他们有 非营利合作伙伴计划，而我运营的是一个非营利组织的论坛。
我仍然不太清楚取消订阅链接的问题具体是什么——能否有人总结一下：如果用户点击的是取消订阅链接，而不是 Discourse 添加的链接（或者像注册确认邮件那样，Discourse 根本没有添加链接），具体会发生什么情况？
更新：Elastic Email 现在可与 Discourse 管理员协作，禁用 EE 的退订链接，并通过 Discourse 管理订阅。
我已向他们的支持团队提出该问题，并收到如下回复：
您好 Dan，
我们的一些客户正在使用 discourse.org，他们的发送统计数据表现良好。换句话说，他们都是我们乐于服务的合法企业。
考虑到您的具体情况，我们将与您合作并禁用退订链接。这样，您就可以通过 Discourse.org 管理订阅。
希望这能符合您的需求。
谢谢
Lubomir
Dan，我想问题在于会出现脱节。Discourse 中的数据无法反映邮件已停止发送并被邮件服务的抑制列表拦截这一事实。
随后，你不得不定期在 Discourse 中手动清理这些记录，这是一项令人烦恼的工作。
此外，而且可能更糟糕的是，用户无法简单地通过 Discourse 界面重新激活订阅，你必须以某种方式在邮件服务中移除抑制状态。
这是个好消息！谢谢，我会跟进。
这就是上面描述的问题。我认为需要做的，是为 Mailjet 添加一个 webhook，以便在发生这种情况时，Mailjet 可以通知 Discourse。（已有针对 Mailgun 等其他服务的#howto）。
虽然让 Mailjet 移除其退订链接是个好主意，但这仍然无法涵盖因其他原因导致邮箱地址失效的情况。
我最近为 Postmark 提交了一个 PR：Postmark bounce support? - #6 by pfaffman
我设想（但这并非由我决定），类似的针对 ElasticEmail 的 PR 也会受到欢迎。
他们的 webhook 文档在此：https://help.elasticemail.com/en/articles/2376855-how-to-manage-http-web-notifications-webhooks
我刚刚与他们沟通，他们表示也打算从我发送的邮件中移除该链接。
这太棒了！
不过我要补充一点，他们提出的一个条件是：只要所有邮件都由 Discourse 生成，他们就会提供帮助（
）