Postmark and Sendgrid seem to offer a very decent api to use for sending email and improving deliverability. As a bonus stats are also handled by them.
1 ) using shared ip
2 ) sending more than 1000 email per hours may cause Spam
3 ) sending from root server without SMTP login may cause this problem
4 ) contents email has links from websites blocked from RBL ( Real Time Blacklist )
5 ) ...
I'd in general be pessimistic about the IP reputation of platform-as-a-service type offerings. Testing Google AppEngine is on my to-do list, but I've there's been much talk about Amazon EC2 presenting a real problem -- these products are not very efficient preventing use by spammers, and reputation is taking a hit.
As for the practical steps of setting up outbound email, Jeff Atwood has a very nice and nearly comprehensive article on his blog.
What I'd certainly suggest is:
Make sure your sending IP has a reverse DNS.
Check your IP reputation for example at senderscore.org (though that's heavily US centric)
Make sure bounces are handled on your side, and [email protected] is reachable
Set up SPF and DKIM. SenderID if you want to.
Sign up for all feedback loops at major mailbox providers / ISPs and act on spam complaints -- if your user complain, you're doing something wrong. Also, set a "friendly name" on your From: address, as some mailboxes will only display the local part -- " Update" is friendlier than only seeing "automatic" (Gmail does this).
Watch the volume you send. If it's high from the start (>1000s/day to each major ISP) you may get blocked outright.
You'll find a lot of deliverability tips, most of the time from interested parties (email service providers). A relatively reputable resource is deliverability.com, backed in part by Return Path. Of course, going with a commercial email service provider might be a solution for you, but your use case is quite specific and you'll need real-time individual messaging, not marketing newsletters, if I understand you right.
I worked for a company that re-sold Return Path's tool -- so take this with a pinch of salt: It' won't help you get delivered. It can, however, be a valuable tool tracking down where your problems are. It is on the other hand expensive, and hiring a specialist that can go through your specific case might be more affordable. Or reading a lot and experimenting a lot yourself.
@chryss does a great job pointing out the important factors that need to be taken into consideration:
-- reverse DNS, sender reputation, list management (ie, cleaning lists of addresses who have marked your email spam, invalid addresses, etc and keeping track of hard and soft bounces and acting accordingly to those events), SPF records, DKIM signatures, ISP feedback loops, ISP rate limits. Also, email content is important to keep in mind.
Generally speaking, this is all pretty complicated and annoying stuff to deal with, especially as your email volume increases.
In terms of IP reputation with PaaS systems, the key thing to remember is this:
-- if you share an IP with someone who earns a poor reputation (say, a spammer on EC2), that reputation will negatively affect your deliverability. On the other hand, if you send from a dedicated IP, you have the opportunity to earn your own reputation - if you are a good sender, follow best practices, and your customers want the emails they expect to receive from you (which they should since it sounds like you are sending mostly transactional emails), you will maintain a great reputation and should enjoy good deliverability (granted all of the technical stuff mentioned above is taken care of).
We generally keep an eye on deliverability "chatter" online, and send out all the cool/useful stuff that we find on a daily basis through our twitter feed -- feel free to follow us: twitter.com/sendgrid. We are also beginning to ramp up our own blogging, so you can join the conversation if you like: blog.sendgrid.com.
If you want a comprehensive solution without having to do a lot of troubleshooting/fact-finding, just check out SendForensics.com. Disclaimer: I am affiliated with the company.
发布评论
评论（7）
不久前我们也遇到过类似的问题。您可能想了解一下 Microsoft 的发件人 ID：
https://www.microsoft.com/mscorp/safety/technologies/senderid/default.mspx
并查看名为“发件人 ID SPF 记录提交表”的链接。
We had a similar issue a while back.. You probably want to read up on Microsoft's Sender ID:
https://www.microsoft.com/mscorp/safety/technologies/senderid/default.mspx
and look at the link called "Sender ID SPF Record Submission Form".
Postmark 和 Sendgrid 似乎提供了一个非常不错的 API，可用于发送电子邮件和提高送达率。作为奖励，统计数据也由他们处理。
Postmark and Sendgrid seem to offer a very decent api to use for sending email and improving deliverability. As a bonus stats are also handled by them.
1）使用共享ip
2）每小时发送超过1000封电子邮件可能会导致垃圾邮件
3）在没有SMTP登录的情况下从根服务器发送可能会导致此问题
4）电子邮件内容包含来自 RBL（实时黑名单）阻止的网站的链接
5）...
1 ) using shared ip
2 ) sending more than 1000 email per hours may cause Spam
3 ) sending from root server without SMTP login may cause this problem
4 ) contents email has links from websites blocked from RBL ( Real Time Blacklist )
5 ) ...
一般来说，我对平台即服务类型产品的知识产权声誉持悲观态度。测试 Google AppEngine 在我的待办事项列表中，但我已经有很多关于 Amazon EC2 提出了一个真正的问题 - 这些产品不能非常有效地防止垃圾邮件发送者的使用，并且声誉受到打击。
至于设置出站电子邮件的实际步骤，Jeff Atwood 有一个非常好的且几乎全面的 他的博客上的文章。
我当然建议的是：
您会发现很多可传递性提示，大多数时候来自感兴趣的各方（电子邮件服务提供商）。相对信誉良好的资源是 Deliverability.com，部分由 Return Path 提供支持。当然，与商业电子邮件服务提供商合作可能是您的解决方案，但您的用例非常具体，如果我理解正确的话，您将需要实时的个人消息传递，而不是营销新闻通讯。
我曾在一家转售 Return Path 工具的公司工作过，所以对此持保留态度：它不会帮助您交付产品。然而，它可以成为一个有价值的工具来追踪您的问题所在。另一方面，它的价格昂贵，聘请一位可以处理您的具体案例的专家可能会更实惠。或者自己多读书、多尝试。
I'd in general be pessimistic about the IP reputation of platform-as-a-service type offerings. Testing Google AppEngine is on my to-do list, but I've there's been much talk about Amazon EC2 presenting a real problem -- these products are not very efficient preventing use by spammers, and reputation is taking a hit.
As for the practical steps of setting up outbound email, Jeff Atwood has a very nice and nearly comprehensive article on his blog.
What I'd certainly suggest is:
You'll find a lot of deliverability tips, most of the time from interested parties (email service providers). A relatively reputable resource is deliverability.com, backed in part by Return Path. Of course, going with a commercial email service provider might be a solution for you, but your use case is quite specific and you'll need real-time individual messaging, not marketing newsletters, if I understand you right.
I worked for a company that re-sold Return Path's tool -- so take this with a pinch of salt: It' won't help you get delivered. It can, however, be a valuable tool tracking down where your problems are. It is on the other hand expensive, and hiring a specialist that can go through your specific case might be more affordable. Or reading a lot and experimenting a lot yourself.
@chryss 做得很好，指出了需要考虑的重要因素：
-- 反向 DNS、发件人信誉、列表管理（即清理已标记您的电子邮件垃圾邮件、无效地址等的地址列表，并跟踪硬退信和软退信并根据这些事件采取相应行动）、SPF 记录、DKIM 签名、 ISP 反馈循环、ISP 速率限制。此外，记住电子邮件内容也很重要。
一般来说，这些都是非常复杂且烦人的事情，尤其是当您的电子邮件数量增加时。
就 PaaS 系统的 IP 声誉而言，要记住的关键是：
-- 如果您与声誉不佳的人（例如 EC2 上的垃圾邮件发送者）共享 IP，则该声誉将对您的送达率产生负面影响。另一方面，如果您从专用 IP 发送邮件，您就有机会赢得自己的声誉 - 如果您是一个好的发件人，遵循最佳实践，并且您的客户希望收到他们期望从您那里收到的电子邮件（他们应该这样做）因为听起来您主要发送的是事务性电子邮件），您将保持良好的声誉并且应该享有良好的送达率（假设上面提到的所有技术内容都得到处理）。
我们通常会关注在线的可交付性“聊天”，并通过我们的 Twitter 源发送我们每天发现的所有酷/有用的内容 - 请随时关注我们：twitter.com/sendgrid。我们也开始加强我们自己的博客，所以如果您愿意，您可以加入对话：blog.sendgrid.com。
@chryss does a great job pointing out the important factors that need to be taken into consideration:
-- reverse DNS, sender reputation, list management (ie, cleaning lists of addresses who have marked your email spam, invalid addresses, etc and keeping track of hard and soft bounces and acting accordingly to those events), SPF records, DKIM signatures, ISP feedback loops, ISP rate limits. Also, email content is important to keep in mind.
Generally speaking, this is all pretty complicated and annoying stuff to deal with, especially as your email volume increases.
In terms of IP reputation with PaaS systems, the key thing to remember is this:
-- if you share an IP with someone who earns a poor reputation (say, a spammer on EC2), that reputation will negatively affect your deliverability. On the other hand, if you send from a dedicated IP, you have the opportunity to earn your own reputation - if you are a good sender, follow best practices, and your customers want the emails they expect to receive from you (which they should since it sounds like you are sending mostly transactional emails), you will maintain a great reputation and should enjoy good deliverability (granted all of the technical stuff mentioned above is taken care of).
We generally keep an eye on deliverability "chatter" online, and send out all the cool/useful stuff that we find on a daily basis through our twitter feed -- feel free to follow us: twitter.com/sendgrid. We are also beginning to ramp up our own blogging, so you can join the conversation if you like: blog.sendgrid.com.
如果您想要一个全面的解决方案，而无需进行大量故障排除/事实调查，只需查看
SendForensics.com。免责声明：我隶属于该公司。问候，
拉斯
If you want a comprehensive solution without having to do a lot of troubleshooting/fact-finding, just check out
SendForensics.com. Disclaimer: I am affiliated with the company.Regards,
Russ
如果以下任何或所有元素出现问题，通常会发生送达能力问题：
更多信息请点击此处
Deliverability issues generally happen if there is something wrong with any or all of the following elements:
More information here