Home / Industry

To Where are Bounce Messages Sent?

This seems to be one of the greatest mysteries to new postmasters. It can be confusing as the messages go to the SMTP MAIL FROM address, which can be different from, or the same as the from header. If you're reading this article, we would first suggest reviewing the article, "How to check an SMTP connection with a manual telnet session” as it covers the basics of the SMTP dialog.

The key to understanding bounces (sometimes referred to as DSNs, Delivery Status Notifications or NDRs, Non-Delivery Reports) is that they should always be sent to the SMTP MAIL FROM address. Some mail platforms may not adhere to this rule, but most do, so we'll focus on the majority of what you're likely to see. From review of the above mentioned post, there is the following sample SMTP session:

==================START SESSION==================
telnet mail.port25.com 25
Trying 69.63.149.30…
Connected to mail.port25.com (69.63.149.30).
Escape character is '^]'.
220 mail.port25.com (PowerMTA(TM) v4.0) ESMTP service ready
EHLO server.example.com
250-mail.port25.com says hello
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-CHUNKING
250-8BITMIME
250-XACK
250-XMRG
250-SIZE 54525952
250-VERP
250 DSN
MAIL FROM: <support@port25.com>
250 2.1.0 MAIL ok
RCPT TO: <support@port25.com>
250 2.1.5 <support@port25.com> ok
DATA
354 send message
From: "John Smith" <jsmith@port25.com>
To: "Jane Doe" <jdoe@port25.com>
Subject: test message sent from manual telnet session
Date: Wed, 11 May 2011 16:19:57 -0400

Hello World,
This is a test message sent from a manual telnet session.

Yours truly,
SMTP administrator

.
250 2.6.0 message received
QUIT
221 2.0.0 mail.port25.com says goodbye
====================END SESSION==================

In the above example there are two from addresses:

MAIL FROM: <support@port25.com>

And:

From: "John Smith" <jsmith@port25.com>

It is the former, the MAIL FROM address, to which bounces are sent. The latter, the 'from:' header, is part of the body of the message and is what shows in the email client as the sender of the message.

Of course, one might ask, how do I check the message to see where the bounces would be sent? This is easily done by checking the full headers of the message. Here are some examples of well known email clients and how to check the headers (assuming you are already viewing the given email in question:

  • Yahoo – Click More -> View Full Header
  • Gmail – Click the dropdown arrow next to the reply button -> Show original
  • Hotmail – Click Actions -> View message source
  • Outlook desktop client – Right click on the message and select Message Options
  • Mac Mail – Command+Shift+H or View Menu -> Message -> All Headers

Once you have the headers in front of you, they should look something like the following:

From "Scott Habicht" Fri Nov 14 19:57:42 2014
Return-Path: <support@port25.com>
Received: by mail.port25.com id hcpfbm11u8kk for <example@yahoo.com>; Fri, 14 Nov 2014 14:57:47 -0500 (envelope-from <support@port25.com>)
From: "Scott Habicht" <support@port25.com>
To: <example@yahoo.com>
Subject: testing headers
Date: Fri, 14 Nov 2014 14:57:42 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary=" — -=_NextPart_000_0075_01D0001B.57BC7570″
Content-Language: en-us
Content-Length: 2066

In the above example, it is very easy to the see the From: header, but what happened to the SMTP MAIL FROM address? Well, it is now shown as the Return-Path header:

The top entry was added by Yahoo:

Return-Path: <support@port25.com>

The Return-Path header represents the SMTP MAIL FROM address, where bounces would be sent. From section 4.4. "Trace Information" of RFC 5321:

"When the delivery SMTP server makes the "final delivery" of a message, it inserts a return-path line at the beginning of the mail data. This use of return-path is required; mail systems MUST support it. The return-path line preserves the information in the <reverse-path> from the MAIL command. Here, final delivery means the message has left the SMTP environment. Normally, this would mean it had been delivered to the destination user or an associated mail drop, but in some cases it may be further processed and transmitted by another mail system."

It is important to note that the Return-Path header should NOT be added by the application that creates the email as they would be ignored. The Return-Path header should only be added by a given SMTP server.

Additional reading: http://en.wikipedia.org/wiki/Bounce_address

Evaluate PowerMTA (Free Trial) — PowerMTA compliments your technology stack whether it's on premise or in the cloud. Increasingly, cloud based senders and enterprises are integrating PowerMTA with other front end applications for maximum delivery and granular controls. Learn More

Port25

About Port25 – Port25, A Message Systems Company, provides highly focused email delivery software that addresses the ever-expanding needs of client communications and digital messaging apps. Port25's flagship product, PowerMTA™, has a global footprint, with over 4,000 installations in more than 51 countries. Learn More

Related topics: Email

 
   

Don't miss a thing – get the Weekly Wrap delivered to your inbox.

Related Blogs

Related News

Explore Topics

Dig Deeper

Mobile Internet

Sponsored by Afilias Mobile & Web Services

DNS Security

Sponsored by Afilias

IP Addressing

Sponsored by Avenue4 LLC

Cybersecurity

Sponsored by Verisign

Promoted Posts

Buying or Selling IPv4 Addresses?

ACCELR/8 is a transformative IPv4 market solution developed by industry veterans Marc Lindsey and Janine Goodman that enables organizations buying or selling blocks as small as /20s to keep pace with the evolving demands of the market by applying processes that have delivered value for many of the largest market participants. more»

Industry Updates – Sponsored Posts

Government Guidance for Email Authentication Has Arrived in USA and UK

ValiMail Raises $12M for Its Email Authentication Service

Port25 Announces Release of PowerMTA V4.5r5

New Case Study: Jobtome.com Replaces 30 Postfix Servers with a Single PowerMTA

An Update on Port25 and the Future of PowerMTA - One Year Later​

Encrypting Inbound and Outbound Email Connections with PowerMTA

V12 Group Sustains Customer Satisfaction by Deploying PowerMTA for Launchpad Platform

PowerMTA Now Offers Scheduled Delivery Control

DKIM for ESPs: The Struggle of Living Up to the Ideal

Reactivation Campaign: Shared vs. Dedicated IPs

An Open Source Perspective on Commercial MTAs

Five Essential PowerMTA Configuration Tips

What's New With Port25's PowerMTA v4.5

New Feature in PowerMTA v4.5: IP Based Rate Limiting

Case Study: Emergency Response Systems Rely on Timely Messaging Through PowerMTA

Port25 Announces Next Major Release of Its Email Delivery Solution, PowerMTA

Case Study: How PowerMTA Transparent Deliverability Metrics Paves Way for Email Service Provider

Case Study: MailChimp Achieves Efficient Execution and Reliability with PowerMTA

Case Study: Emma Swaps Its SMTP Infrastructure for PowerMTA to Handle Growing Mail Volume

Case Study: Email Service Provider GetResponse Scales with PowerMTA