sisimai 4.22.2 → 4.22.3

data/set-of-emails/maildir/bsd/email-sendmail-48.eml

@@ -0,0 +1,101 @@
+Delivered-To: sironeko-nyaan@google.example.com
+Received: by 10.200.14.13 with SMTP id a13csp1701181qti;
+        Wed, 8 Nov 2017 09:02:07 -0800 (PST)
+X-Google-Smtp-Source: ABhQp+TVB71hnz/M9qRdm1xxgUICive1I5s96glaZ2sK+NVaBCD19J19uOPZ+vI9CZCkM7qvxwJU
+X-Received: by 10.84.232.76 with SMTP id f12mr996194pln.269.1510160527592;
+        Wed, 08 Nov 2017 09:02:07 -0800 (PST)
+ARC-Seal: i=1; a=rsa-sha256; t=1510160527; cv=none;
+        d=google.com; s=arc-20160816;
+        b=THBbkb3IO6QWQV9w/jJyWuSPm4W8ikAGVyAaOIOo3sBCb8ONZxJyvxyoIHFItMj1Di
+         iapH3JvMOeGatTefSYwjxH2/gGAGwKCEq8CE0qh3Xjz8AS/gjkLuWrgniaBkzMxG1Ojs
+         TIf2DczsEaldWAeZ+HImAF9Fhu04HRsuDaiXQM96mWqMtNsIIHj7KNHQKd+9RZI3tKgy
+         8DxYYSxEX/P7owaAvvViV/bVATkD+OBSe+DdbNxw4uuyh/bjt2emOsRwPopRcGx7qt09
+         qRW/EcSNe4lUDBwQbxYCM04WMCjKhd23XlOHUo7L6JePgHSUEz+M2o56Gsu4MciLDs4F
+         LwqA==
+ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
+        h=auto-submitted:subject:mime-version:to:message-id:from:date
+         :arc-authentication-results;
+        bh=v7JQ9/7DRIl7kut8RF3dpRnNI2t51NuZGyXTxFm5sCc=;
+        b=LX1JpTWPGYYynKV/kqdqShGOOitpkF0+aWtjAxTm1FpWonzWys9/0LWG+AvdE0Nn6u
+         JYbBQOD7J1L9mllfYOdOT21a9UeAmKX0TKn4PCbaY+2gjefAIbz1PgMqVj73kAOLLSJq
+         UlEeBrCuhTOyV+D6v413PtbT/RWJPKvfIpQgO7K+kEwgz3crJdDvK8OoQmDULUYnkFHo
+         5tBJpwM88GREX83CoCftt8tJJ8gaoguVNpIdjle6reVjKV6pKTtxw03HFRzHTi/lKtqw
+         sJpfva/BxDoS47tBi6wHhNkxtUF/fPnPftRRf9/4VHNLpstOqqYzWafNiNYF6PtMmuHb
+         ei7g==
+ARC-Authentication-Results: i=1; mx.google.com;
+       spf=pass (google.com: best guess record for domain of postmaster@nijo.cr.example.co.jp designates 192.0.2.2 as permitted sender) smtp.helo=nijo.cr.example.co.jp
+Return-Path: <>
+Received: from nijo.cr.example.co.jp (nijo.cr.example.co.jp. [192.0.2.2])
+        by mx.google.com with ESMTP id f67si4012437pgc.640.2017.11.08.09.02.06
+        for <sironeko-nyaan@google.example.com>;
+        Wed, 08 Nov 2017 09:02:07 -0800 (PST)
+Received-SPF: pass (google.com: best guess record for domain of postmaster@nijo.cr.example.co.jp designates 192.0.2.2 as permitted sender) client-ip=192.0.2.2;
+Authentication-Results: mx.google.com;
+       spf=pass (google.com: best guess record for domain of postmaster@nijo.cr.example.co.jp designates 192.0.2.2 as permitted sender) smtp.helo=nijo.cr.example.co.jp
+Received: from localhost (localhost)
+	by nijo.cr.example.co.jp (V8/cf) id vA8H25ix008330;
+	Thu, 9 Nov 2017 02:02:05 +0900
+Date: Thu, 9 Nov 2017 02:02:05 +0900
+From: Mail Delivery Subsystem <poostmaster@cr.example.co.jp>
+Message-Id: <201711081702.vA8H25ix008330@nijo.cr.example.co.jp>
+To: <sironeko@cr.example.co.jp>
+MIME-Version: 1.0
+Content-Type: multipart/report; report-type=delivery-status;
+	boundary="vA8H25ix008330.1510160525/nijo.cr.example.co.jp"
+Subject: Returned mail: see transcript for details
+Auto-Submitted: auto-generated (failure)
+
+This is a MIME-encapsulated message
+
+--vA8H25ix008330.1510160525/nijo.cr.example.co.jp
+
+The original message was received at Thu, 9 Nov 2017 02:02:00 +0900
+from c22-neko.kyoto.example.ne.jp [198.51.100.22]
+
+   ----- The following addresses had permanent fatal errors -----
+<pseudo-local-part-kijitora-nyaan@sfr.fr>
+    (reason: 550 5.7.1 <pseudo-local-part-kijitora-nyaan@sfr.fr>: Recipient address rejected: User unknown)
+
+   ----- Transcript of session follows -----
+... while talking to smtp-in.sfr.fr.:
+>>> DATA
+<<< 550 5.7.1 <pseudo-local-part-kijitora-nyaan@sfr.fr>: Recipient address rejected: User unknown
+550 5.1.1 <pseudo-local-part-kijitora-nyaan@sfr.fr>... User unknown
+<<< 554 5.5.1 Error: no valid recipients
+
+--vA8H25ix008330.1510160525/nijo.cr.example.co.jp
+Content-Type: message/delivery-status
+
+Reporting-MTA: dns; nijo.cr.example.co.jp
+Received-From-MTA: DNS; c22-neko.kyoto.example.ne.jp
+Arrival-Date: Thu, 9 Nov 2017 02:02:00 +0900
+
+Final-Recipient: RFC822; pseudo-local-part-kijitora-nyaan@sfr.fr
+Action: failed
+Status: 5.7.1
+Remote-MTA: DNS; smtp-in.sfr.fr
+Diagnostic-Code: SMTP; 550 5.7.1 <pseudo-local-part-kijitora-nyaan@sfr.fr>: Recipient address rejected: User unknown
+Last-Attempt-Date: Thu, 9 Nov 2017 02:02:04 +0900
+
+--vA8H25ix008330.1510160525/nijo.cr.example.co.jp
+Content-Type: message/rfc822
+
+Return-Path: <sironeko@cr.example.co.jp>
+Received: from [203.0.113.222] (c22-neko.kyoto.example.ne.jp [198.51.100.22])
+	(authenticated bits=128)
+	by nijo.cr.example.co.jp (V8/cf) with ESMTP id vA8H1Vj1008317
+	for <pseudo-local-part-kijitora-nyaan@sfr.fr>; Thu, 9 Nov 2017 02:02:00 +0900
+From: "Azuma, Kuniyuki" <sironeko@cr.example.co.jp>
+Content-Type: text/plain; charset=us-ascii
+Content-Transfer-Encoding: 7bit
+Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
+Subject: Nyaan
+Message-Id: <8EC9A623-6663-44B2-A947-3B370B040645@cr.example.co.jp>
+Date: Thu, 9 Nov 2017 02:02:00 +0900
+To: pseudo-local-part-kijitora-nyaan@sfr.fr
+X-Mailer: Apple Mail (2.3273)
+
+Nyaan
+
+--vA8H25ix008330.1510160525/nijo.cr.example.co.jp--
+

data/set-of-emails/maildir/bsd/rfc3464-33.eml

@@ -0,0 +1,38 @@
+From Mailer-Daemon@example.co.uk  Mon Apr 29 23:34:45 2013
+From: Mailer-Daemon@example.co.uk (Mail Delivery System)
+Date: Mon, 29 Apr 2013 23:34:45 +0000
+Subject: Mail delivery failed: returning message to sender
+Message-ID: <NEKO222-NEKO00-C1@example.co.uk>
+
+This message was created automatically by mail delivery software.
+
+A message that you sent could not be delivered to one or more of its
+recipients. This is a permanent error. The following address(es) failed:
+
+  pseudo-local-part-kijitora@wanadoo.fr
+    (generated from noraneko.nyaan@example.com)
+    SMTP error from remote mail server after end of data:
+    host smtp.wanadoo.fr [192.0.2.1]: 550 5.2.0 Mail rejete. Mail rejected. OFR_506 [506]
+
+------ This is a copy of the message, including all the headers. ------
+
+Return-path: <noranyaans@lists.example.net>
+Received: from [198.51.100.102] (helo=198.51.100.102.static-user.example.br)
+	by example.co.uk with esmtp (Exim 4.69)
+	(envelope-from <noranyaans@lists.example.net>)
+	id NEKO22-NEKO30-FF
+	for noraneko.nyaan@example.com; Mon, 29 Apr 2013 23:34:45 +0000
+Received: from 198.51.100.102(helo=neko.nyaan.example.org)
+	by 198.51.100.102.static-user.example.br with esmtpa (Exim 4.69)
+	(envelope-from )
+	id NEKO42-2222CC-F0
+	for noraneko.nyaan@example.com; Mon, 29 Apr 2013 23:34:45 +0000
+From:  <noraneko.nyaan@example.com>
+To: <noraneko.nyaan@example.com>
+Subject: Nyaan
+Mime-Version: 1.0
+Content-type: text/html; charset="utf-8"
+Content-Transfer-Encoding: 7bit
+
+Nyaaaaaaaaaaaaaan
+

data/set-of-emails/maildir/bsd/rfc3464-34.eml

@@ -0,0 +1,53 @@
+Subject: Delayed Mail (still being retried)
+From: MAILER-DAEMON@neko.example.org (Mail Delivery System)
+Date: 29-04-2017 23:34
+To: sironeko@neko.example.org
+
+This is the mail system at host smtp.neko.example.org.
+
+####################################################################
+# THIS IS A WARNING ONLY.  YOU DO NOT NEED TO RESEND YOUR MESSAGE. #
+####################################################################
+
+Your message could not be delivered for more than 2 hour(s).
+It will be retried until it is 4 day(s) old.
+
+For further assistance, please send mail to postmaster.
+
+If you do so, please include this problem report. You can
+delete your own text from the attached returned message.
+
+                   The mail system
+
+<kijitora@example.com>: connect to
+    nyaan.example.com[192.0.2.2]:25: No route to host
+
+
+
+Reporting-MTA: dns; smtp.neko.example.org
+X-Postfix-Queue-ID: FFFFFFFFFF
+X-Postfix-Sender: rfc822; sironeko@neko.example.org
+Arrival-Date: Thu, 29 Apr 2017 23:34:45 +0900 (JST)
+
+Final-Recipient: rfc822; kijitora@example.com
+Original-Recipient: rfc822;kijitora@example.com
+Action: delayed
+Status: 4.4.1
+Diagnostic-Code: X-Postfix; connect to
+    nyaan.example.com[192.0.2.2]:25: No route to host
+Will-Retry-Until: Sun, 05 May 2017 23:34:45 +0900 (JST)
+
+
+
+Return-Path: <sironeko@neko.example.org>
+Received: from neko (unknown [213.0.113.2])
+	by smtp.neko.example.org (Postfix) with ESMTPSA id 22222222ee;
+	Thu, 29 Apr 2017 23:34:45 +0900 (JST)
+Content-Type: multipart/mixed; boundary="===============002200002222=="
+MIME-Version: 1.0
+Date: Thu, 29 Apr 2017 23:34:45 +0900
+Subject: Nyaan
+From: sironeko@neko.example.org
+To: kijitora@example.com
+Message-Id: <20170429233445.FFFFFFFF02@smtp.neko.example.org>
+

data/set-of-emails/maildir/bsd/rhost-exchange-online-02.eml

@@ -0,0 +1,89 @@
+Return-Path: <MAILER-DAEMON>
+Received: from email110.example.com (unknown [192.0.2.222])
+	by s151v.example.com (Bossmail) with ESMTP id FFF222EEE22
+	for <sironeko@example.co.jp>; Thu, 29 Apr 2017 23:34:45 +0900 (JST)
+Received: from email2.example.com ([192.0.2.22])
+  by email110.example.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Apr 2017 23:34:45 +0900
+Received: by email2.example.com (Postfix)
+	id EEEEEEEEEE2; Thu, 29 Apr 2017 23:34:45 +0900 (JST)
+Date: Thu, 29 Apr 2017 23:34:45 +0900 (JST)
+From: MAILER-DAEMON@email2.example.com (Mail Delivery System)
+Subject: Undelivered Mail Returned to Sender
+To: sironeko@example.co.jp
+MIME-Version: 1.0
+Content-Type: multipart/report; report-type=delivery-status;
+	boundary="2222FFFFEEEE.0000000000/email2.example.com"
+Content-Transfer-Encoding: 8bit
+Message-Id: <20170429233445.00000000000@email2.example.com>
+
+This is a MIME-encapsulated message.
+
+--2222FFFFEEEE.0000000000/email2.example.com
+Content-Description: Notification
+Content-Type: text/plain; charset=us-ascii
+
+This is the mail system at host email2.example.com.
+
+I'm sorry to have to inform you that your message could not
+be delivered to one or more recipients. It's attached below.
+
+For further assistance, please send mail to postmaster.
+
+If you do so, please include this problem report. You can
+delete your own text from the attached returned message.
+
+                   The mail system
+
+<kijitora@example.org>: host
+    example.org.mail.protection.outlook.com[198.51.100.2] said: 550
+    5.4.1 [kijitora@example.org]: Recipient address rejected: Access
+    denied [NEKOCHAN.cat-neko22.prod.protection.outlook.com] (in reply to
+    RCPT TO command)
+
+--2222FFFFEEEE.0000000000/email2.example.com
+Content-Description: Delivery report
+Content-Type: message/delivery-status
+
+Reporting-MTA: dns; email2.example.com
+X-Postfix-Queue-ID: 00000000000
+X-Postfix-Sender: rfc822; sironeko@example.co.jp
+Arrival-Date: Thu, 29 Apr 2017 23:34:45 +0900 (JST)
+
+Final-Recipient: rfc822; kijitora@example.org
+Original-Recipient: rfc822;kijitora@example.org
+Action: failed
+Status: 5.4.1
+Remote-MTA: dns; example.org.mail.protection.outlook.com
+Diagnostic-Code: smtp; 550 5.4.1 [kijitora@example.org]: Recipient
+    address rejected: Access denied
+    [NEKOCHAN.cat-neko22.prod.protection.outlook.com]
+
+--2222FFFFEEEE.0000000000/email2.example.com
+Content-Description: Undelivered Message
+Content-Type: message/rfc822
+Content-Transfer-Encoding: 8bit
+
+Received: from smtp2.example.com (smtp2.example.com [203.0.113.2])
+	by email2.example.com (Postfix) with ESMTP id eeeeeeeeeee
+	for <kijitora@example.org>; Thu, 29 Apr 2017 23:34:45 +0900 (JST)
+Received: from [192.0.2.2] (unknown [203.0.113.22])
+	(Authenticated sender: sironeko@example.co.jp)
+	by relay1.example.com (nekomail) with ESMTP id fffffffff22
+	for <kijitora@example.org>; Thu, 29 Apr 2017 23:34:45 +0900 (JST)
+Content-Type: multipart/mixed; boundary="===============222222220000222=="
+MIME-Version: 1.0
+Subject: Nyaan
+From: "Sironeko" <sironeko@example.co.jp>
+To: kijitora@example.org
+Date: Thu, 29 Apr 2017 23:34:45 +0900
+Message-ID: <222222222000.2222.2222222222220000000@NEKO-Nyaan>
+
+--===============222222220000222==
+Content-Type: text/plain; charset="utf-8"
+MIME-Version: 1.0
+
+Nyaan
+
+--===============222222220000222==--
+
+--2222FFFFEEEE.0000000000/email2.example.com--

data/set-of-emails/maildir/bsd/rhost-exchange-online-03.eml

@@ -0,0 +1,205 @@
+X-Apparently-To: sironeko@example.net; Thu, 29 Apr 2017 23:34:45 +0000
+Return-Path: <>
+Received-SPF: none (domain of a2-222.smtp-out.amazonses.com does not designate permitted sender hosts)
+X-Originating-IP: [192.0.2.222]
+Received: from 127.0.0.1  (EHLO a2-222.smtp-out.amazonses.com) (192.0.2.222)
+  by relay2.mail.neko2.example.org with SMTP; Thu, 29 Apr 2017 23:34:45 +0000
+MIME-Version: 1.0
+From: MAILER-DAEMON@amazonses.com
+To: sironeko@example.net
+Date: Thu, 29 Apr 2017 23:34:45 +0000
+Content-Type: multipart/report; report-type=delivery-status;
+	boundary="22ffee22-2222-2222-2222-2222aaaabbbb"
+X-MS-Exchange-Message-Is-Ndr:
+Content-Language: en-US
+Message-ID: <0000002222002222-22222222-2222-2222-ffff@email.amazonses.com>
+Subject: Undeliverable: Nyaan
+Auto-Submitted: auto-replied
+X-MS-PublicTrafficType: Email
+X-MS-TrafficTypeDiagnostic: 0000000000002:
+X-MS-Office365-Filtering-Correlation-Id: 00002222-2222-2200-222200220000
+Received-SPF: None (protection.outlook.com:  does not designate permitted
+ sender hosts)
+Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=<>; 
+X-SES-Outgoing: 2017.04.29-192.0.2.222
+Content-Length: 1022
+
+--22ffee22-2222-2222-2222-2222aaaabbbb
+Content-Type: multipart/alternative; differences=Content-Type;
+	boundary="00002200-0022-2222-2002-222200220000"
+
+--00002200-0022-2222-2002-222200220000
+Content-Type: text/plain; charset="us-ascii"
+Content-Transfer-Encoding: quoted-printable
+
+[http://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versio=
+n=3Db8d100a9-0a8b-8e6a-88e1-ef488fee0470]
+Your message to kijitora@example.com couldn't be delivered.
+
+kijitora wasn't found at example.com.
+
+2222222222220000-222. . .       Office 365      kijitora
+Action Required                 Recipient
+
+
+Unknown To address
+
+
+How to Fix It
+The address may be misspelled or may not exist. Try one or more of the foll=
+owing:
+
+  *   Send the message again following these steps: In Outlook, open this n=
+on-delivery report (NDR) and choose Send Again from the Report ribbon. In O=
+utlook on the web, select this NDR, then select the link "To send this mess=
+age again, click here." Then delete and retype the entire recipient address=
+ If prompted with an Auto-Complete List suggestion don't select it. After =
+typing the complete address, click Send.
+  *   Contact the recipient (by phone, for example) to check that the addre=
+ss exists and is correct.
+  *   The recipient may have set up email forwarding to an incorrect addres=
+s. Ask them to check that any forwarding they've set up is working correctl=
+y.
+  *   Clear the recipient Auto-Complete List in Outlook or Outlook on the w=
+eb by following the steps in this article: Fix email delivery issues for er=
+ror code 5.1.10 in Office 365<http://go.microsoft.com/fwlink/?LinkId=3D5329=
+72>, and then send the message again. Retype the entire recipient address b=
+efore selecting Send.
+
+
+If the problem continues, forward this message to your email admin. If you'=
+re an email admin, refer to the More Info for Email Admins section below.
+
+
+Was this helpful? Send feedback to Microsoft<http://go.microsoft.com/fwlink=
+/?LinkId=3D525921>.
+________________________________
+
+
+More Info for Email Admins
+Status code: 550 5.1.10
+
+This error occurs because the sender sent a message to an email address hos=
+ted by Office 365 but the address is incorrect or doesn't exist at the dest=
+ination domain. The error is reported by the recipient domain's email serve=
+r, but most often it must be fixed by the person who sent the message. If t=
+he steps in the How to Fix It section above don't fix the problem, and you'=
+re the email admin for the recipient, try one or more of the following:
+
+The email address exists and is correct - Confirm that the recipient addres=
+s exists, is correct, and is accepting messages.
+
+Synchronize your directories - If you have a hybrid environment and are usi=
+ng directory synchronization make sure the recipient's email address is syn=
+ced correctly in both Office 365 and in your on-premises directory.
+
+Errant forwarding rule - Check for forwarding rules that aren't behaving as=
+ expected. Forwarding can be set up by an admin via mail flow rules or mail=
+box forwarding address settings, or by the recipient via the Inbox Rules fe=
+ature.
+
+Recipient has a valid license - Make sure the recipient has an Office 365 l=
+icense assigned to them. The recipient's email admin can use the Office 365=
+ admin center to assign a license (Users > Active Users > select the recipi=
+ent > Assigned License > Edit).
+
+Mail flow settings and MX records are not correct - Misconfigured mail flow=
+ or MX record settings can cause this error. Check your Office 365 mail flo=
+w settings to make sure your domain and any mail flow connectors are set up=
+ correctly. Also, work with your domain registrar to make sure the MX recor=
+ds for your domain are configured correctly.
+
+For more information and additional tips to fix this issue, see Fix email d=
+elivery issues for error code 5.1.10 in Office 365<http://go.microsoft.com/=
+fwlink/?LinkId=3D532972>.
+
+
+Original Message Details
+Created Date:   4/29/2017 11:34:45 PM
+Sender Address: 0000002222002222-22222222-2222-2222-ffff@amazonses.com
+Recipient Address:      kijitora@example.com
+Subject:        Nyaan
+
+
+Error Details
+Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not fo=
+und by SMTP address lookup
+DSN generated by:       NEKO220022.namprd22.prod.outlook.com
+
+
+Message Hops
+HOP     TIME (UTC)      FROM    TO      WITH    RELAY TIME
+1       4/29/2017
+11:34:45 PM      a2-22.smtp-out.amazonses.com    NEKO22NYAAN0.mail.protecti=
+on.outlook.com       Microsoft SMTP Server (version=3DTLS1_0, cipher=3DTLS_=
+ECDHE_RSA_WITH_AES_256_CBC_SHA_P384)  2 sec
+2       4/29/2017
+11:34:45 PM      NEKO22NYAAN0.eop-NAM03.prod.protection.outlook.com     CAT=
+NEKO0022.outlook.office365.com     Microsoft SMTP Server (version=3DTLS1_=
+2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256)       2 sec
+
+Original Message Headers
+
+Received: from NEKO22NYAAN22.namprd22.prod.outlook.com (198.51.100.2) by
+ NEKO220022.namprd22.prod.outlook.com (203.0.113.2) with Microsoft SMT=
+P
+ Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P=
+256) id
+ 15.20.13.10; Thu, 29 Apr 2017 23:34:45 +0000
+Received: from NEKO22NYAAN0.eop-NAM03.prod.protection.outlook.com
+ (2222:2222:2222:2222::2222) by NEKO22NYAAN22.outlook.office365.com
+ (2022:2222:2222:2222::2222) with Microsoft SMTP Server (version=3DTLS1_2,
+ cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.13.10 via
+ Frontend Transport; Thu, 29 Apr 2017 23:34:45 +0000
+Authentication-Results: spf=3Dpass (sender IP is 192.0.2.2)
+ smtp.mailfrom=3Damazonses.com; example.com; dkim=3Dpass (signature was veri=
+fied)
+ header.d=3Damazonses.com;example.com; dmarc=3Dnone action=3Dnone
+ header.from=3Dexample.net;
+Received-SPF: Pass (protection.outlook.com: domain of amazonses.com designa=
+tes
+ 192.0.2.2 as permitted sender) receiver=3Dprotection.outlook.com;
+ client-ip=3D192.0.2.2; helo=3Da2-222.smtp-out.amazonses.com;
+Received: from a2-222.smtp-out.amazonses.com (192.0.2.222) by
+ NEKO22NYAAN0.mail.protection.outlook.com (203.0.113.2) with Microsoft S=
+MTP
+ Server (version=3DTLS1_0, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384=
+) id
+ 15.1.1222.22 via Frontend Transport; Thu, 29 Apr 2017 23:34:45 +0000
+Content-Type: text/html; charset=3Dutf-8
+MIME-Version: 1.0
+Date: Thu, 29 Apr 2017 23:34:45 +0000
+Content-Transfer-Encoding: quoted-printable
+Subject: Nyaan
+From: "Sironeko, Nyaan" <sironeko@example.net>
+Message-ID: <2222222222220000-00000000-2222-2222-2222-000000002222-000000@e=
+mail.amazonses.com>
+To: kijitora@example.com
+X-SES-Outgoing: 2017.04.29-192.0.2.2
+Return-Path: 2222222222221111-22222222-2222-0000-eeeeeeeeeeee@amazonses.com
+X-MS-PublicTrafficType: Email
+X-DkimResult-Test: Passed
+
+--00002200-0022-2222-2002-222200220000
+Content-Type: text/plain; charset="us-ascii"
+Content-Transfer-Encoding: quoted-printable
+
+Nyaan
+
+--00002200-0022-2222-2002-222200220000--
+
+--22ffee22-2222-2222-2222-2222aaaabbbb
+Content-Type: message/delivery-status
+
+Reporting-MTA: dns;NEKO220022.namprd22.prod.outlook.com
+Received-From-MTA: dns;a2-22.smtp-out.amazonses.com
+Arrival-Date: Thu, 29 Apr 2017 23:34:45 +0000
+
+Final-Recipient: rfc822;kijitora@example.com
+Action: failed
+Status: 5.1.10
+Diagnostic-Code: smtp;550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup
+
+
+--22ffee22-2222-2222-2222-2222aaaabbbb--
+