Mandrill和浏览器功能

本文介绍了Mandrill和浏览器功能的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述 任何人都知道Mandrill是否支持查看浏览器功能，如MailChimp | ARCHIVE | 变量。如果没有，我可以使用搜索功能来获取发送邮件（例如，如果我知道有关邮件的某些特定元数据）？或者我必须渲染模板并自己存储以供以后检索？

解决方案

最好的办法是将副本存储在您可以在电子邮件中链接到您的服务器，例如批量电子邮件。 Mandrill不支持ARCHIVE合并标记，因为它特定于MailChimp中可能一次发送到大量收件人的广告系列。为成千上万的收件人存储单个副本是相当简单的。但是，Mandrill跟踪您发送的每封电子邮件，因此需要将每封电子邮件的唯一副本以公开访问的方式进行存储，从而增加了大量数据存储（以及数据存储成本和高架）。

我们还注意到，大量的交易电子邮件是高度个性化的，可能包含机密信息，因此创建每个电子邮件的可公开访问的版本没有意义在很多情况下。

电子邮件内容可以在您的帐户中查看24小时后发送电子邮件，但内容不可访问长期和他们通过API无法使用（关于观看内容的Mandrill KB中的更多信息）。有关数据存储时间的更多一般信息，请参阅这里有一些这个。

Anyone know if Mandrill support a "View in browser" functionality like the MailChimp |ARCHIVE| variable. If not, can I use the search functionality to fetch a send mail (for example if I know some specific metadata for the mail in question)? Or would I have to render the template and store it myself for later retrieval?

解决方案

The best bet is to store a copy on your server that you can link to from within an email when it makes sense, such as for bulk emails. The ARCHIVE merge tag isn't supported in Mandrill automatically, as that's specific for a campaign in MailChimp that may be sent to a large number of recipients at once. Storing a single copy for thousands of recipients is fairly straightforward. Mandrill, though, tracks every individual email you send, so it would require a single unique copy of every email to be stored in a way that' publicly-accessible, which adds up to extremely large amounts of data storage (and data storage costs and overhead).

We're also aware that a lot of transactional email is highly personalized and may contain confidential information, so creating a publicly-accessible version of each email doesn't make sense in a lot of cases.

Email contents can be viewed within your account for 24 hours after an email is sent, but the contents aren't accessible longer-term and they're not available via the API (more info in the Mandrill KB here about viewing contents). For more general info about how long data is stored, here's a bit more here about that.