Why Forwarding Emails is So Bad
When testing emails, forwarding can be the bane of a designer’s existence. This is especially true if you’re working with a 3rd party and don’t have access to their sending service. Perhaps the email you so carefully coded is being forwarded around the office for “quality assurance.” Now you’re hearing about all of the broken buttons and unstyled links. This is because each email client puts its own unique code modifications on an email when forwarding it, instead of forwarding the code it originally received.
Pay it Forward
Forwarding emails can cause all kinds of wonky rendering issues. These issues are usually caused by the sending email client, but can be compounded by the one that receives the email as well. Check out the examples below to see what kind of havoc forwarding can wreak on your emails.
Take this stackable 3 column section from our free responsive template. This is how it should look.
When an Outlook.com user forwards it to Yahoo, it might come out missing all the images!
Or if an Outlook.com user forwards to Office 365, it can break all of the buttons.
Even worse, when a Gmail user forwards to Outlook 2007, it can mess up your carefully coded tables.
Take a look at how this section’s vertical alignment was altered by an Outlook 2013 user who forwarded to Gmail.
How should you send an email for review?
Avoid forwarding emails for testing or review, otherwise you’ll spend your time fixing issues that don’t really exist. Here are a few ways to share an email that don’t require forwarding.
- Run a test in our comprehensive email testing system, and share the test results. This will allow anybody with the link to see how the email renders in 70+ desktop clients, mobile clients and web clients with just a click of the mouse.
- Enter your HTML into your ESP and send it the same way that you’ll send it to your customers. This will make sure that your tests are completely accurate, and save you valuable time. If you don’t have access to your sending service or ESP, ask a person who does have access to send you the email.
- Send your code as an html file, and let the recipient open it in a browser. This won’t show how it looks in email clients, but it can let them take a look at the email’s design. They’ll also be able to see responsive behaviors triggering as they resize their browser window.
- Send the email to yourself, take a screen capture of it, and then send that to others for review. This is a clunky way of doing things, but it ensures that they’re seeing exactly what you are.
What’s your review process?
Have you been bitten by the forwarding bugs? Let us know about your review process, and how you share emails, in the comments down below.
Try our tool free for 7 days and see what email testing can do for you.