针对此问题推荐一个灵活的群发邮件系统
每天有 1200 名订阅者收到电子邮件。每个用户的个人资料可能会根据他们的兴趣（地理、市场领域甚至产品类型）而有所不同。
研究人员每天会创建多达 20 份新报告，并且每天都会向用户发送一封电子邮件，其中包含他们感兴趣的报告的前言（带有返回显示完整报告的网站的链接）。
[报告还按地理位置、市场领域和产品类型进行分类]
电子邮件目前通过 smtp 服务器广播。每个用户的电子邮件都是根据他们的个人资料和报告类别之间的匹配来构建的。
有没有灵活的群发邮件系统可以替代smtp服务器？如果是这样，人们会推荐什么。
我们使用 dotNet 技术。每个订阅者的数量不太可能超过 5000 个。我面临着将其与公司使用的其他群发邮件系统集成的压力。他们对 smp 不满意。该公司在全球拥有 3 万名员工。上述应用程序是自定义新闻服务而不是营销系统。他们在 Solaris/Java/etc 上进行标准化，但很乐意保留当前技术（除了 smtp 位）。
1200 subscribers are being emailed each day. Each user's profile may vary according to their interests be it geographic, market sector or even product type.
Each day up to 20 new reports are created by researchers and users are sent a daily email with the report prefaces of those reports they're interested in (with a link back to a website showing the full report).
[Reports are also categorised by geography, market sector and product type]
Emails are currently broadcast via an smtp server. Each user has their email contructed according to the match between their profile and the report categories.
Is there a flexible mass mailing system which can replace the smtp server? If so, what do people recommend.
We use dotNet technology. It's unlikely that the number of subscribers will every be more than 5000. I am under pressure to integrate this with the other mass-mailing systems used by the company. They are not happy with smpt. This company employs 30k worldwide. The application described above is a custom news service NOT a marketing system. They standardise on Solaris/Java/etc but are happy to keep the current technology (apart from the smtp bit).
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
你没有看错。使用 smtp 不是我的想法。在用户配置文件的设计中提供这种程度的灵活性并不是我的想法。
该应用程序属于一家小公司，后来被大公司收购了。该系统最初使用 smpt（现在仍然如此）。我见过的群发邮件系统[Lyris. Pure360]似乎不会在每次登录时构建电子邮件，并且似乎面向营销（而不是自定义新闻报道）。
我能想象完成此操作的唯一方法是拥有一个用户属性（用户当天将收到的报告的 ID 列表），并在发送电子邮件之前更新该用户属性。
我不可能将计算出哪个用户获得哪个报告的逻辑（发送给群发邮件程序）交给别人。
You're not mistaken. Not my idea to use smtp. Not my idea to provide this degree of flexibility in the design of the user profile.
This application belonged to a tiny company who were bought out by the larger one. The system originally used smpt (and still does). The mass-mailing systems I've seen [Lyris. Pure360] don't seem to construct emails per login and seem oriented to marketing (not custom news reporting).
The only way I can imagine this being done is to have a user property (a list of IDs of the reports a user will get that day) and have that user property updated just before the emailing.
There's not way I will palm off the logic (to the mass-mailer) which figures out which user gets which reports.