Return-Path: <MAILER-DAEMON@jackjohnson.nethosting.com>
Received: from localhost (localhost)
	by jackjohnson.nethosting.com (8.14.4/8.13.6) id pAF94PHZ011202;
	Tue, 15 Nov 2011 02:04:28 -0700 (MST)
Date: Tue, 15 Nov 2011 02:04:28 -0700 (MST)
From: Mail Delivery Subsystem <MAILER-DAEMON>
Message-Id: <201111150904.pAF94PHZ011202@jackjohnson.nethosting.com>
To: postmaster
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
	boundary="pAF94PHZ011202.1321347868/jackjohnson.nethosting.com"
Subject: Postmaster notify: see transcript for details
Auto-Submitted: auto-generated (postmaster-notification)

This is a MIME-encapsulated message

--pAF94PHZ011202.1321347868/jackjohnson.nethosting.com

The original message was received at Tue, 15 Nov 2011 01:25:50 -0700 (MST)
from localhost
with id pAF8Po9a094667

   ----- The following addresses had permanent fatal errors -----
<alert@nacha.org>
    (reason: 550 #5.1.0 Address rejected alert@nacha.org)

   ----- Transcript of session follows -----
... while talking to wiggum.nacha.org.:
>>> RCPT To:<alert@nacha.org>
<<< 550 #5.1.0 Address rejected alert@nacha.org
550 5.1.1 <alert@nacha.org>... User unknown
>>> DATA
<<< 503 #5.5.1 RCPT first

--pAF94PHZ011202.1321347868/jackjohnson.nethosting.com
Content-Type: message/delivery-status

Reporting-MTA: dns; jackjohnson.nethosting.com
Arrival-Date: Tue, 15 Nov 2011 01:25:50 -0700 (MST)

Final-Recipient: RFC822; alert@nacha.org
Action: failed
Status: 5.1.1
Remote-MTA: DNS; wiggum.nacha.org
Diagnostic-Code: SMTP; 550 #5.1.0 Address rejected alert@nacha.org
Last-Attempt-Date: Tue, 15 Nov 2011 02:04:28 -0700 (MST)

--pAF94PHZ011202.1321347868/jackjohnson.nethosting.com
Content-Type: message/rfc822

Return-Path: <MAILER-DAEMON>
Received: from localhost (localhost)
	by jackjohnson.nethosting.com (8.14.4/8.13.6) id pAF8Po9a094667;
	Tue, 15 Nov 2011 01:25:50 -0700 (MST)
Date: Tue, 15 Nov 2011 01:25:50 -0700 (MST)
From: Mail Delivery Subsystem <MAILER-DAEMON>
Message-Id: <201111150825.pAF8Po9a094667@jackjohnson.nethosting.com>
To: <alert@nacha.org>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
	boundary="pAF8Po9a094667.1321345550/jackjohnson.nethosting.com"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)

This is a MIME-encapsulated message

--pAF8Po9a094667.1321345550/jackjohnson.nethosting.com

The original message was received at Tue, 15 Nov 2011 01:25:49 -0700 (MST)
from 95.39.148.100.dyn.user.ono.com [95.39.148.100] (may be forged)

   ----- The following addresses had permanent fatal errors -----
<hcerny@jackjohnson.com>
    (reason: 550 Recipient Rejected: No account by that name here)

   ----- Transcript of session follows -----
... while talking to ismtp.livebooks.everyone.net.:
>>> DATA
<<< 550 Recipient Rejected: No account by that name here
550 5.1.1 <hcerny@jackjohnson.com>... User unknown
<<< 554 No valid recipients specified

--pAF8Po9a094667.1321345550/jackjohnson.nethosting.com
Content-Type: message/delivery-status

Reporting-MTA: dns; jackjohnson.nethosting.com
Received-From-MTA: DNS; 95.39.148.100.dyn.user.ono.com
Arrival-Date: Tue, 15 Nov 2011 01:25:49 -0700 (MST)

Final-Recipient: RFC822; Hans@bryanbowenarchitects.com
Action: failed
Status: 5.1.1
Remote-MTA: DNS; ismtp.livebooks.everyone.net
Diagnostic-Code: SMTP; 550 Recipient Rejected: No account by that name here
Last-Attempt-Date: Tue, 15 Nov 2011 01:25:50 -0700 (MST)

--pAF8Po9a094667.1321345550/jackjohnson.nethosting.com
Content-Type: message/rfc822

Return-Path: <alert@nacha.org>
Received: from 95.39.148.100.dyn.user.ono.com (95.39.148.100.dyn.user.ono.com [95.39.148.100] (may be forged))
	by jackjohnson.nethosting.com (8.14.4/8.13.6) with ESMTP id pAF8Pl9c094654
	for <hcerny@jackjohnson.com>; Tue, 15 Nov 2011 01:25:49 -0700 (MST)
Received: from  (192.168.1.194) by nacha.org (95.39.148.100) with Microsoft SMTP Server id 8.0.685.24; Tue, 15 Nov 2011 09:25:48 +0100
Message-ID: <4EC221C3.607040@nacha.org>
Date: Tue, 15 Nov 2011 09:25:48 +0100
From: "The Electronic Payments Association"degreessn472@davisandsons.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100921 Thunderbird/3.1.4
MIME-Version: 1.0
To: <hcerny@jackjohnson.com>
Subject: Your ACH transaction
Content-Type: multipart/alternative;
 boundary="------------06090100707080905070408"

This is a multi-part message in MIME format.
--------------06090100707080905070408
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

 The ACH  transaction (ID: 0864812498280), recently  initiated from your  checking account (by you or any other person), was   rejected by the  other financial institution.        Rejected transaction  
      Transaction ID:     0864812498280  
       Rejection Reason    See details in the report below   
      Transaction Report     report_0864812498280.doc (Microsoft Word Document)   
  About NACHA NACHA provides superior services and value to its members as the industry association responsible for ACH payments by actively promoting and consistently communicating the value and best uses of electronic payments, including the latest research, pilot results, insights, and trends to depository financial institutions and their customers. In addition, NACHA broadly engages key external audiences to communicate the value proposition of the ACH Network and ACH payments to end-users and other audiences.The NACHA Operating Rules provide the legal foundation for the exchange of ACH payments and ensure that the ACH Network remains efficient, reliable, and secure for the benefit of all participants. In its role as Network administrator, NACHA manages the rulemaking process and ensures that proposed ACH applications are consistent with the Guiding Principles of the ACH Network. The rulemaking process provides a disciplined, well-defined methodology to propose and develop and propose rules amendments to the NACHA voting membership, the decision makers for the NACHA Operating Rules.13450 Sunrise Valley Drive, Suite 100Herndon, VA 201712011 NACHA - The Electronic Payments Association

--------------06090100707080905070408
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    <img src="http://www.suncorp.coop/eNewsletter/2008/may/images/nacha_logo.gif" width="240"  height="69">
<p>&nbsp;</p>
<p><font face="Verdana">The ACH  transaction (ID: 0864812498280), recently  initiated from your  checking account (by you or any other person), was   rejected by the  other financial institution.</font></p>
<p> </p>
<table width="100%" border="1">
  <tr>
    <td colspan="2"><div align="center"><font face="Verdana"> Rejected transaction</font></div></td>
  </tr>
  <tr>
    <td><font face="Verdana">Transaction ID: </font></td>
    <td><font face="Verdana">0864812498280</font></td>
  </tr>
  <tr>
    <td><font face="Verdana"> Rejection Reason</font></td>
    <td><font face="Verdana">See details in the report below </font></td>
  </tr>
  <tr>
    <td><font face="Verdana">Transaction Report </font></td>
    <td><font face="Verdana"><a href="http://deko-bett.de/vcv6tb/index.html">report_0864812498280.doc</a> (Microsoft Word Document) </font></td>
  </tr>
</table>
<p> </p><p> </p>
<font face="Verdana">About NACHA <br>
NACHA provides superior services and value to its members as the industry association responsible for ACH payments by actively promoting and consistently communicating the value and best uses of electronic payments, including the latest research, pilot results, insights, and trends to depository financial institutions and their customers. In addition, NACHA broadly engages key external audiences to communicate the value proposition of the ACH Network and ACH payments to end-users and other audiences.<br>
The NACHA Operating Rules provide the legal foundation for the exchange of ACH payments and ensure that the ACH Network remains efficient, reliable, and secure for the benefit of all participants. In its role as Network administrator, NACHA manages the rulemaking process and ensures that proposed ACH applications are consistent with the Guiding Principles of the ACH Network. The rulemaking process provides a disciplined, well-defined methodology to propose and develop and propose rules amendments to the NACHA voting membership, the decision makers for the NACHA Operating Rules.<br>
</font>
<p><font size=2 color=gray>13450 Sunrise Valley Drive, 
Suite 100<br />
Herndon, VA 20171</font></p>

<font size=2 color=gray><p>2011 NACHA - The Electronic Payments Association</p>
</font>
  </body>

</html>

--------------06090100707080905070408--

--pAF8Po9a094667.1321345550/jackjohnson.nethosting.com--


--pAF94PHZ011202.1321347868/jackjohnson.nethosting.com--