对于非自定义批量电子邮件,是使用 BCC 字段更好,还是为每个收件人生成带有“收件人”标头的单独电子邮件?
我每天都会为想要接收每日优惠的用户生成批量邮件。我可以发送一封单独的物理电子邮件,并在每个用户自己唯一的“收件人”标头中指定,也可以发送一封电子邮件,其中包含密件抄送行上的所有用户。
显然,如果我想创建特定于用户的内容,我需要自定义每个用户的电子邮件并单独发送它们,但如果我现在不想要自定义电子邮件,我是否应该只发送单个电子邮件通过 BCC 与所有人发送电子邮件?有任何理由不这样做。
编辑:我正在使用第三方作为我的网关,专门从事符合 CAN-SPAM 合规性的交付等...而不是尝试在我自己的邮件服务器上执行此操作...
更新:我想我真的也在寻找一些指标在这里。密件抄送电子邮件与“收件人”字段电子邮件的打开率是否有差异?可以根据 BCC 字段进行预分类的垃圾邮件过滤规则怎么样?
I'm generating a bulk mailing each day for users who want to receive the daily deals. I can either send a separate physical email with each user specified on their own unique To header, or I can send one email with all the users on the BCC line.
Obviously if I ever want to create user specific content I will need to customize the emails per user and send them individually, but if I don't want customized email right now, should I just send out the single email with everyone on BCC? Any reason to NOT do that.
Edit: I'm using a third party as my gateway that specializes in delivery with CAN-SPAM compliance, etc.. not trying to do this off my own mail server...
Update: I guess I'm really also looking for some metrics here. Is there a difference in open rates of BCC'ed email vs To field email? What about spam filtering rules that might pre-classify based on the BCC field?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
我没有理由认为不这样做。使用密件抄送是发送批量电子邮件的礼貌方式。
No reason I can think off for NOT doing it. Using BCC is the polite way to send bulk emails.
在这种情况下,事实证明正确答案都不是。网关提供了一个自定义标头 API,允许我在辅助“收件人”字段中指定所有收件人。然后,API 处理了电子邮件的盲投,并为我进行了变量替换,这样我就不必多次传输所有重复的内容。然后,API 处理“电子邮件传送的最佳实践”。
In this case, it turns out that the correct answer was neither. The gateway provided a custom header API that allowed me to specify all the recipients in a secondary "To" field. The API then handled the blind delivery of the emails, and also did variable substitution for me so I didn't have to transmit all the duplicate content multiple times. The API then handled doing "best practices delivery of the email".