Understanding Reputation, NodeJS Documentation, and Integrated Support

We have a small batch of new features for you this week. Reputation improvement helps you understand the factors leading to poor account or tag reputation, reputation history has been expanded to include tag-specific reputation, the NodeJS API client has been added to the API docs, and we've integrated support into the Mandrill application.

Reputation Improvement

When your reputation starts dropping, it can sometimes be hard to understand why. Mandrill uses a large number of factors to determine your account or tag's reputation, and it's not always obvious what the major problems are. Starting this week, accounts and tags with poor reputation will include a section breaking down what the major problems are along with information on what you can do to improve. We've also published a series of guides about common reputation issues in the knowledge base.

Tag Reputation History

Last week we expanded the reputation system to include reputation for specific tags. That's been expanded to include reputation history as well, so you can identify when a specific tag's reputation started to go bad. Just click on the reputation in the tag list to get a dialog with the history and any improvement information available.

NodeJS API Client Documentation

If you're using NodeJS to interact with the Mandrill API, you might already know that we have an official NPM module. We've added Node-specific instructions in our official API docs: https://mandrillapp.com/api/docs/index.nodejs.html. This gives you detailed information on how to make each call with the Node API client and what results you can expect.

List-Unsubscribe Header Changes

Previously, Mandrill always added a List-Unsubscribe header to all outbound emails. We did this to get better anti-spam signals, particularly when the recipient's ISP doesn't support sending us spam complaints - Gmail being the biggest example of this.

While this is useful, it never really made sense to add an unsubscribe link to something like a password reset email. Starting this week, we're only including the List-Unsubscribe header if you also include our automatic unsubscribe link in your email. If you manage your own unsubscribes, you can now provide your own List-Unsubscribe header in your SMTP or API call and we'll use it. By default, we won't include a List-Unsubscribe header at all.

Integrated Support

We've added support features to the app (look for the Help link in the footer) to make it easier to search the knowledge base without interrupting your workflow. And if you can't find what you're looking for in the KB, we've also streamlined the process of filing a support ticket. Since you're already logged in, you don't have to worry about identifying yourself - we already know who you are. This makes it easier for us to help you quickly and accurately, since in many cases we need specific details about your account in order to answer questions.