← Retour au blog
tech 6 August 2026

Stop Sending Me Your Errors

Misusing multipart/alternative to send errors in emails complicates users' lives. Learn why and how to improve email communication.

Article inspired by the original source
Stop Sending Me Your Errors ↗ kramkow.ski

Introduction

In the world of development and IT management, errors are inevitable. However, the way these errors are communicated can make all the difference. If you use emails to convey information, it's crucial to understand how to correctly format messages, especially when it comes to handling errors.

The Problem with multipart/alternative

The multipart/alternative standard was created to allow sending the same content in multiple formats, usually HTML and plain text. The idea is for the email client to choose the format best suited to its capabilities. Yet, this feature is often misused to send error messages.

A common example is sending an email with an error message in the plain text part, saying "Plain text version not available," prompting the user to switch to the HTML version. This is not just frustrating; it also complicates the user experience, especially if the client doesn't handle these formats well.

Usage Scenarios

Scenario 1: Ancient Client

Imagine a user with an old email client that doesn't support MIME. They will see gibberish followed by "Plain text version not available." This won't help them resolve the issue.

Scenario 2: Modern MIME Client

For a modern client that handles MIME but not HTML, the error displays with no clear recovery option. In this case, the absence of a text part would probably have been preferable.

Scenario 3: Plain Text Preference

For those who prefer plain text, receiving an error instead of meaningful content is an obstacle. They then have to manually switch to HTML, which goes against their preferences.

User Impact

According to a Litmus study, 46% of email users prefer reading their emails in plain text rather than HTML. Sending errors instead of content in the plain text part only frustrates these users. Additionally, it increases the risk that the message will be ignored or misinterpreted.

Best Practices

  1. Provide Complete Content Versions: Don't leave the plain text part empty or with an error. Include a readable version of the message.
  1. Automate Content Generation: Use automation tools to automatically convert HTML to plain text.
  1. Cross-Client Testing: Ensure that your content renders well on the most common email clients, including those that favor plain text.

Conclusion

To err is human, but the way to communicate them must be optimized. By improving how errors are sent via email, you can significantly enhance the user experience.

Let's discuss your project in 15 minutes.

email multipart/alternative error communication user experience email best practices
Deepthix newsletter · 100% AI · every Monday 8am

An AI agent reads tech for you.

Our AI agent scans ~200 sources per week and ships the best articles to your inbox Monday 8am. Free. One click to unsubscribe.

Visit the newsletter page →

Want to automate your operations?

Let's talk about your project in 15 minutes.

Book a call