Return-Path: Date: Mon, 9 Feb 2009 15:31:29 +0900 From: Mail Delivery Subsystem Message-Id: <200902090631.n196VTQA0001134@mta007.example.jp> To: postmaster MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="n196VTQA0001134.1234161089/mta007.example.jp" Subject: Postmaster notify: see transcript for details Auto-Submitted: auto-generated (postmaster-notification) This is a MIME-encapsulated message --n196VTQA0001134.1234161089/mta007.example.jp The original message was received at Mon, 9 Feb 2009 15:31:29 +0900 from [192.0.2.254] ----- The following addresses had permanent fatal errors ----- (reason: 550 5.7.1 Relaying denied. IP name lookup failed [192.0.2.254]) ----- Transcript of session follows ----- ... while talking to smtp.sancon.jp.: >>> MAIL From: <<< 550 5.7.1 Relaying denied. IP name lookup failed [192.0.2.254] 554 5.0.0 Service unavailable --n196VTQA0001134.1234161089/mta007.example.jp Content-Type: message/delivery-status Reporting-MTA: dns; mta007.example.jp Received-From-MTA: DNS; 254.0.2.192.host.example.jp Arrival-Date: Mon, 9 Feb 2009 15:31:29 +0900 Final-Recipient: RFC822; the-postmaster-and-webmaster@example.com Action: failed Status: 5.7.1 Diagnostic-Code: SMTP; 550 5.7.1 Relaying denied. IP name lookup failed [192.0.2.254] Last-Attempt-Date: Mon, 9 Feb 2009 15:31:29 +0900 --n196VTQA0001134.1234161089/mta007.example.jp Content-Type: text/rfc822-headers Return-Path: From: the-postmaster@example.org To: the-postmaster-and-webmaster@example.com Subject: TEST Date: Mon, 9 Feb 2009 15:31:30 +0900 MIME-Version: 1.0 Content-Type: test/plain --n196VTQA0001134.1234161089/mta007.example.jp--