- Developer Hub
- SparkPost API
- Free Tools for Email Teams and Developers
- Slack Channel
- User Guides & Migrations
- Submit a Ticket
- SparkPost Academy
- Email Deliverability Resources
- Email Explained
- White Papers & Guides
- Webinars & Videos
- SparkPost vs. SendGrid
- Customers Stories
- Contact Us
What do you want to see in 2018?
We hope you’ve all thoroughly enjoyed the holidays with friends, family and loved ones. As we ramp up for an incredible 2018, we want to hear from you!
At SparkPost, the goal with each blog that we publish is to be helpful, informative or just plain entertaining. Sometimes we totally nail it, and other times we might miss the mark a bit. That’s why we’d like to hear what you think! What kind of content do you enjoy reading the most on our blog? How-to’s on more technical skills? Features on community members using cool technologies? Thought leadership showcasing trends in the email and messaging industries?
We’ve put together a very short survey so you can let us know what you think – there’s room at the end for comments, suggestions, etc. We appreciate your feedback and promise to incorporate it into our plan for next year. For fun, I’ve listed below our top 5 posts from 2017 – they might help refresh you on what types of content we regularly publish here on the blog:
Europe’s GDPR privacy law is an issue for almost every company with an app, SaaS product, or other service. Learn exactly what email senders need to know before the changes go into effect.
Learn some successful strategies we use to build our microservices architecture and how they allow us to evolve our API during rapid growth.
Whether you are new to coding, want to brush up on skills or just network, CodeNewbie is an incredible resource. Check out this Q&A with founder Saron Yitbarek, and get excited for some fun upcoming projects we’ve got in store with them in the new year.
Breaking changes can result in frustration and loss of trust between an API provider and their users. API versioning is one way to avoid that frustration.
Email headers host a treasure trove of information. Learn how to read them and understand more about the mail you’re sending and receiving.
Any industry trends or topics you think were under-represented? Be sure to list that feedback in the survey or tweet us with your thoughts!
Happy New Year!
So you want to decode email headers
So you’re looking to boost your email game, get your hands dirty and stay in the running to be the world’s best email sender — or something like that. This post will give you a practical understanding of email headers, their importance, how to access them and how to read them.
Why should you read on?
Email headers provide rich information to help with any number of investigations. Most importantly, email headers provide a means of verifying the origin of a message. Other cool beans things headers help with are;
- Authentication results (SPF/DKIM). These are critical to solid deliverability!
- Any hops the message may have taken along the way
- Timestamps from when the message reached certain waypoints
Anyone working in the following areas should know the basics about email headers:
- Security/Abuse teams
- Fellow dorm-room nerds (I thought you looked familiar!)
Step 1: Get to the Choppa! (e.g. head on over to your personal inbox)
Depending on which email client you use, mail headers can be presented with some variation, I’m a numbers guy, you’re a numbers guy…so, we’ll just pick Gmail. Find a message that was ‘promotional’ or ‘notification’ in nature, as this will yield the best demonstration use case. I’ve chosen the fine folks over at Pinterest. If your company already sends mail, those would be fine samples to use as well.
Step 2: Open the email in the reading pane
Adjacent the ‘Reply to button’ hit the down arrow (1), then ‘show original’ (2)
Eh voila, headers!. What you’re actually looking at here is a combination of headers and the message itself, in all of its parts (html, plain text version, to, from, subject, yada yada). For the purpose of this how-to, we’re going to avoid getting overtly technical and focus solely on the header portion. At the bottom of this post, I’ve included links some awesome extra credit reading.
Step 3: Who dis? (e.g. Finding the sender)
Let’s look for ‘who’ sent the message. This isn’t as easy to answer, as you’d think. Reason being is that some of the coolest companies on the planet actually make a living at helping other companies send their email (see what I did there? snort snort). In the spirit of keeping things basic, we’re going to show you a single-party example. You should know however that it’s not uncommon that a single message references multiple responsible parties. In the case of my example, it was transmitted using SparkPost.
Here are the three header values that carry the ‘who’ part.
- ‘From’: This is the entity that the recipient see’s in their email client.
- ‘Mail From’: This is the entity that is used for Sender Policy Framework (SPF). The SPF entity uses special DNS entries to ensure that the IP address used to transmit the message is authenticated. This header field has a few other names; Return-Path, envelope-sender and bounce domain.
- DKIM domain: This is the entity that has signed the message. Signing a message is an important practice to ensure that the message was not altered in transit. DKIM also uses special DNS entries to ensure authenticity.
Step 4: I think he’s Five-oh (e.g. Checking Authentication results)
Now we know who sent it, let’s make sure this message was really sent by Pinterest.
- SPF: You want to see a string match for ‘spf=pass’
- DKIM: You want to see a string match for ‘dkim=pass’
- DMARC: (separate blog post coming on this one. Be sure to bookmark our blog and check back in)
Congrats! You now know about 1000% times more about email then your downstairs neighbor.
Looking for other resources on email headers or email in general? Check out these articles:
SparkPost © 2018 All Rights Reserved
- How to Explain DKIM to your Grandmother
- Cool Email Headers Parsing tool
- Accessing Headers in other email clients (AOL/Hotmail/Yahoo/more)