Return-Path: <
[email protected]>
Received: from somehost.example.com (somehost.example.com [192.168.120.100])
	by somehost.example.com (8.12.11.20060308/8.12.11) with ESMTP id k56Lshgd012896
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <
[email protected]>; Tue, 6 Jun 2006 14:54:49 -0700
Received: from localhost (localhost)
	by somehost.example.com (8.12.11.20060308/8.12.11) id k56LshjZ000347;
	Tue, 6 Jun 2006 14:54:43 -0700
Date: Tue, 6 Jun 2006 14:54:43 -0700
From: Mail Delivery Subsystem <
[email protected]>
Message-Id: <
[email protected]>
To: <
[email protected]>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
	boundary="k56LshjZ000347.1149630883/somehost.example.com"
Content-Transfer-Encoding: binary
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)
This is a MIME-encapsulated message
--k56LshjZ000347.1149630883/somehost.example.com
The original message was received at Tue, 6 Jun 2006 14:54:42 -0700
from localhost [127.0.0.1]
   ----- The following addresses had permanent fatal errors -----
<
[email protected]>
    (reason: 550 5.1.1 <
[email protected]>: Recipient address rejected: User unknown in local recipient table)
   ----- Transcript of session follows -----
... while talking to c.mx.voyager.net.:
>>> DATA
<<< 550 5.1.1 <
[email protected]>: Recipient address rejected: User unknown in local recipient table
550 5.1.1 <
[email protected]>... User unknown
<<< 554 5.5.1 Error: no valid recipients
--k56LshjZ000347.1149630883/somehost.example.com
Content-Type: message/delivery-status
Reporting-MTA: dns; somehost.example.com
Received-From-MTA: DNS; localhost
Arrival-Date: Tue, 6 Jun 2006 14:54:42 -0700
Final-Recipient: RFC822; 
[email protected]
Action: failed
Status: 5.1.1
Remote-MTA: DNS; c.mx.voyager.net
Diagnostic-Code: SMTP; 550 5.1.1 <
[email protected]>: Recipient address rejected: User unknown in local recipient table
Last-Attempt-Date: Tue, 6 Jun 2006 14:54:42 -0700
--k56LshjZ000347.1149630883/somehost.example.com
Content-Type: message/rfc822
Content-Transfer-Encoding: binary
Return-Path: <
[email protected]>
Received: from somehost.example.com (localhost [127.0.0.1])
	by somehost.example.com (8.12.11.20060308/8.12.11) with ESMTP id k56LsJpH032469
	for <
[email protected]>; Tue, 6 Jun 2006 14:54:42 -0700
Received: (from sender@localhost)
	by somehost.example.com (8.12.11.20060308/8.12.11/Submit) id k56LA4MN021347
	for 
[email protected]; Tue, 6 Jun 2006 14:10:04 -0700
Date: Tue, 6 Jun 2006 14:10:04 -0700
Message-Id: <
[email protected]>
Content-Type: multipart/alternative;
 boundary="----------=_1149628204-19504-578"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.415 (Entity 5.415)
From: Sender Address <
[email protected]>
To: Sender Address <
[email protected]>
Subject: Test Bounce Message
This is a multi-part message in MIME format...
------------=_1149628204-19504-578
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Plaintext here.
------------=_1149628204-19504-578
Content-Type: text/html
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
        "http://www.w3.org/TR/html4/loose.dtd"><html>
  <head>
 <title>Test Bounce Message</title>
<body>
<b>Test HTML part here.</b>
</body>
</html>
------------=_1149628204-19504-578--
--k56LshjZ000347.1149630883/somehost.example.com--