A few weeks ago we released a free API for checking the spamscore of a message. The folks on HackerNews loved it, and it’s been really great to see people find ways to get more value from this API.

Some of our favorite usages have shown up in just the last week!

Spamscore.me

We released our Spam Checking API with an easy and beautiful UI, but it does require that you grab the full email contents including the headers. Simple as this is, it’s work. Wouldn’t it be great if you could just forward an email somewhere, and moments later, get back a nicely formatted report about your email’s spamscore?

That’s exactly what Jim Carter built with spamscore.me. The cool thing about spamscore.me is there’s no interface other than your email client! Just forward any email to go@spamscore.me and get one of these bad boys back.

It’s free (but no less awesome), so please be kind to Jim’s servers. Have other ideas for useful mashups with our spamscore API? Let us know in the comments, or better yet email me once you’ve launched so we can write about it here!

Christmas is saved on Reddit

Our hearts were warmed to find that someone recommended our spamscore checker to a Reddit user whose christmas eCards were being sent to spam. 

Chris was able to jump in and do a quick analysis of the person’s spamscore report, recommending the following to help with the resolution:

• Set your Return-Path header to a domain and address that you control. Then, add an SPF record to that domain with the permitted SMTP servers.
• Do not use your user’s email as the from address. This is spoofing and you can’t control the DKIM or SPF. Instead, use their “From name” but your email address.
• Make sure Reverse DNS is setup for your SMTP server.

While we can’t promise personal spamscore report interpretation for every problem, we’re thrilled to see that this tool is being used to help solve real world problems in people’s applications.

Have you used the spamscore API to successfully track down a problem? Let us know in the comments.

We work very hard to keep Postmark reliable and available for our customers, but sometimes things go wrong that are out of our control. We do our best to communicate the details of any issues we’re having, and make it a priority to prepare you for any planned maintenance or downtime.

Not everybody follows us on Twitter, and emailing our entire customer base isn’t always the best solution either. So today, we’re launching our new Postmark System Status page.

We’ll continue to post updates to Twitter and provide our in-app notices. We’ll still email you ahead of time for planned maintenance. But if you’re ever experiencing a problem and want to know if you’re the only one, you can now visit status.postmarkapp.com and look for recent updates about any known issues. If something is going on, the big banner on top will make that clear and the status updates below will provide more detailed information. 

You can also subscribe to these updates via RSS in your favorite RSS reader, or even subscribe to email updates in your inbox if you prefer.

This is just one more step we’re taking to make sure that you know we’re working hard to provide an easy, fast, and reliable service for delivering your transactional emails to the inbox!

You might have been one of the “lucky” few that tried to pass a comma separated list of email in the To field of a Postmark message just to get back the “Multiple recipients not supported” error. Or maybe you are one of the guys that have been wondering “How come they don’t support Cc?” We have been reluctant to add that feature because of two reasons: