发送大量请求电子邮件
我们公司做工作环境调查，这些调查都是在网上填写的。所有参与者都会通过电子邮件发送其调查的链接（包括个人代码）。
我们的一些客户拥有数百名员工，有时甚至数千名。
我们当前的解决方案只是使用我们的 SMTP 服务器发送此消息，没有任何形式的限制（VB6、CDO）。 （所有收件人通常都在同一域“内部”，[电子邮件受保护] ） 正如您可能想象的那样，这不是一个好的解决方案，这会触发客户端环境中的每个反垃圾邮件/防火墙/网守事件。我们事先与他们的 IT 部门联系，让他们将我们的发送服务器和发件人邮件地址列入白名单。
我们遇到的最常见问题是：
- 接收服务器仅抓取 20-50 封第一封邮件，并拒绝其余邮件（反垃圾邮件措施）。有时我们可以通过让 IT 公司将我们列入白名单来解决这个问题。然而，有时这不起作用。
- 禁用错误邮件地址的退回变得越来越普遍。这并没有告诉我们邮件是否已送达。不管你相信与否，大多数客户从他们的人力资源系统而不是他们的邮件系统向我们提供他们的电子邮件列表。
有人对更好的方法有什么建议吗？我们不可能是唯一一家发送合法群发电子邮件的公司吧？ :)
Our company does work environment surveys, and these surveys are filled in online. All participants are sent a link to their survey in an email (personal code included).
Some of our clients have employee counts in the hundreds and sometimes in the thousands.
Our current solution is just using our SMTP-server to send this, without any form of throttling (VB6, CDO). (All recipients are usually "inside" the same domain, [email protected])
This is not a good solution, as you may imagine, this triggers every anti-spam/firewall/gatekeeper event in the clients environment. We are put in contact with their IT-department beforehand and get them to whitelist our sending server and sender-mail address.
The most usual problems we run in to are:
- Receiving server only grabs the 20-50 first mails and rejects the rest (anti-spam measure). We sometimes can get by this by getting the it-company to whitelist us. Sometimes however, this does not work.
- It's getting more and more normal to disable bouncing of incorrect mail addresses. This gives us no indication of whether a mail has been delivered or not. And believe it or not, most clients gives us their email list from their HR-system, not their mailsystem.
Does anyone have any suggestions for a better way to do this? We can't be the only company sending legitimate mass emails? :)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
有一个 关于 Coding Horror 的好文章详细介绍了发送电子邮件的过程。简而言之：
您还可以使用外部邮件发送服务，例如 Campaign Monitor，它会为您检查这些设置。
There is a good article on Coding Horror that details the process of sending e-mail. In short:
You could also use an external mail sending service like Campaign Monitor, which checks these settings for you.
您可以尝试使用
Bcc:标头字段（按域分组）来指定收件人。这样，邮件服务器只会收到一封邮件，并将其复制到所有提到的地址。这样，邮件服务器就不会被来自您的服务器的流量淹没；它自己的流量泛滥成灾。我尝试过的另一件事是将以下标头添加到外发电子邮件中：
From: [NAME] <[VALID EMAIL]>Organization: [YOUR COMPANY]滥用报告收件人：[有效电子邮件]投诉收件人：[有效电子邮件]优先级：批量这些标头通常不会被用户注意到，可以帮助垃圾邮件过滤器安心（而不是拟人化），因为它知道电子邮件来自哪里，发件人知道它被发送给很多人，并且如果出现问题，应该联系谁。如果垃圾邮件过滤器是人，这相当于使电子邮件听起来很正式（使用公司信纸、带有公司徽标的印刷信封等）。
拥有准确的
Date:标头也很有帮助。You could try using the
Bcc:header field (grouped by domain) to specify recipients. That way, the mail server only gets one message, which it copies to all the addresses mentioned. That way, the mail server isn't flooded with traffic from your server; it's flooded with its own traffic.Another thing I've tried is adding the following headers to outgoing emails:
From: [NAME] <[VALID EMAIL]>Organization: [YOUR COMPANY]Abuse-Reports-To: [VALID EMAIL]Complaints-To: [VALID EMAIL]Precedence: bulkThese headers, while generally not noticed by the user, can help give the spam filter peace of mind (not to anthropomorphize) in that it knows where the email came from, the sender knows it's being sent to many people, and that, if there's a problem, who to contact. If the spam filter were a human, this would be the equivalent of making the email sound official (using company stationery, printed envelope with the company logo, etc.).
It also helps to have an accurate
Date:header.我建议让您的客户将您的服务器列入白名单将是最合适的状态，毕竟您与他们具有合同关系，因此某些配置是合理的。
您发送的电子邮件地址列表的有效性必须由客户负责，特别是如果他们没有从实时电子邮件地址列表中提取该列表。如果客户端没有提供适当的响应，您几乎无能为力或应该做的事情来验证这些地址。
另外，即使是远程，这也不是一个编程问题（好吧，如果您将电子邮件限制到一个公共域，您就有更大的机会通过它，但这与编程无关，更多的是关于 SMTP 的性质和操作以及其中的保护系统）。像这样的问题更适合超级用户。
I'd suggest that getting your clients to whitelist your server would be the most appropriate state, after all you are in a contractual relationship with them so some configuration as a result would be reasonable.
The validity of the email address list that you are sent must lie with the client, particularly if they aren't pulling it from their live email address list. There's little you can do, or should be expected to do, to validate those addresses if the client doesn't provide the appropriate responses.
Also, this isn't a programming question even remotely (okay, if you throttled your emails to a common domain you've more chance of getting it through but that's nothing to do with the programming, more about the nature and operation of SMTP and the protection systems therein). Questions like this are more suited to SuperUser.
我唯一能想到的就是给每个公司送一台装有专业软件的电脑。该计算机需要连接回您的公司，但该连接不必是专用的。将各个公司的电子邮件数据作为压缩数据格式的批量数据发送到该计算机。在部署的盒子上运行的专业软件必须足够智能，能够解压缩数据以释放电子邮件并将它们推送到本地电子邮件服务器进行部署。复杂的部分是了解如何发送以接收来自本地电子邮件服务器的授权以及如何将电子邮件排队以供该电子邮件服务器分发。
这应该可行，因为如果电子邮件来自内部邮件服务器，那么该服务器不会将数据标记为垃圾邮件。您必须将发件人字段更改为客户端提供的指定地址，而不是电子邮件服务器自动应用的通用服务地址。
The only thing I can think of is to send a computer to each company with specialty software. That computer needs a connection back to your company, but the connection does not have to be dedicated. Send the email data for a respective company to that computer as bulk data in a compressed data format. The specialty software running on the deployed box has to be smart enough to decompress the data to release the emails and push them to the local email server for deployment. The complicated part is knowing how to send to receive authorization from the local email server and queue the email for distribution by that email server.
That should work because if the email originates from the internal mail server then that server will not mark the data as spam. You have to change the from field to be the designated address provided from the client and not a generic service address automatically applied by the email server.
您需要使用第三方电子邮件提供商，例如 aweber 或 icontact。这些公司只需支付非常合理的费用即可解决您的电子邮件发送问题。您可以对标头和白名单服务器大惊小怪，直到看到斑点，但您仍然会遇到问题。
这是值得花钱的事情。
You need use a third party email provider such as aweber or icontact. For a very reasonable fee these companies will make your email delivery issues go away. You can fuss with headers and white listing servers until you see spots, but you will continue to have problems.
This is something that is worth spending money on.