sisimai 4.25.14 → 4.25.16

data/lib/sisimai/rhost/mimecast.rb

@@ -0,0 +1,290 @@
+module Sisimai
+  module Rhost
+    # Sisimai::Rhost detects the bounce reason from the content of Sisimai::Data object as an argu-
+    # ment of get() method when the value of "rhost" of the object is "*.mimecast.com". This class
+    # is called only Sisimai::Fact class.
+    module Mimecast
+      class << self
+        MessagesOf = {
+          # https://community.mimecast.com/s/article/Mimecast-SMTP-Error-Codes-842605754
+          'blocked' => [
+            # - The sender's IP address has been blocked by a Blocked Senders Policy.
+            # - Remove the entry from the policy.
+            [421, 'sender address blocked'],
+
+            # - The Sender's IP address has been placed on the block list due to too many invalid
+            #   connections.
+            # - The sender's mail server must retry the connection. The mail server performing the
+            #   connection says the recipient address validation isn't responding.
+            [451, 'recipient temporarily unavailable'],
+
+            # - You've reached your mail server's limit.
+            # - Wait and try again. The mail server won't accept any messages until you're under
+            #   the limit.
+            [451, 'ip temporarily blacklisted'],
+
+            # - The sending mail server is subjected to Greylisting. This requires the server to
+            #   retry the connection, between one minute and 12 hours. Alternatively, the sender's
+            #   IP address has a poor reputation.
+            # - These reputation checks can be bypassed with an Auto Allow or Permitted Senders
+            #   policy. If it's legitimate traffic, amend your Greylisting policy.
+            [451, 'internal resources are temporarily unavailable'],
+
+            # - Ongoing reputation checks have resulted in the message being rejected due to poor
+            #   IP reputation. This could occur after a 4xx error.
+            # - Create an Auto Allow or Permitted Senders policy.
+            #   Note:
+            #     You can request a review of your source IP ranges by completing our online form.
+            [550, 'local ct ip reputation - (reject)'],
+
+            # - The sender's IP address is listed in an RBL. The text displayed is specific to the
+            #   RBL which lists the sender's IP address.
+            # - Bypass the RBL with an Auto Allow or Permitted Senders policy. Additionally request
+            #   the associated IP address from the RBL.
+            #[550, '< details of RBL >'], NEED AN ACTUAL ERROR MESSAGE STRING
+
+            # - The inbound message has been rejected because the originated IP address isn't list-
+            #   ed in the published SPF records for the sending domain.
+            # - Ensure all the IP addresses for your mail servers are listed in your SPF records.
+            #   Alternatively, create a DNS Authentication (Inbound / Outbound) policy with the
+            #   "Inbound SPF" or "Reject on Hard Fail" option disabled. Messages that fail our SPF
+            #   checks are subjected to spam and RBL checks, instead of being rejected.
+            [550, 'spf sender invalid - envelope rejected'],
+
+            # - The DKIM key for the outbound message is broken and doesn't match the DNS record of
+            #   the registered sender.
+            # - Check your organization's DNS record is populated with the right public key as part
+            #   of the DNS Authentication Outbound Signing definition. The private key of the key-
+            #   pair must be populated in the DNS Authentication policy, along with the domain and
+            #   selector of that record.
+            [550, 'dkim sender invalid - envelope rejected'],
+
+            # - The inbound message has been rejected because the originated IP address isn't list-
+            #   ed in the published SPF records for the sending domain.
+            # - Ensure all the IP addresses for your mail servers are listed in your SPF records.
+            [550, 'dmarc sender invalid - envelope rejected'],
+          ],
+          'mesgtoobig' => [
+            # - The email size either exceeds an Email Size Limit policy or is larger than the
+            #   Mimecast service limit. The default is 100 MB for the Legacy MTA, and 200 MB for
+            #   "the Latest MTA".
+            # - Resend the message ensuring it's smaller than the limitation set. The transmission
+            #   and content-encoding can add significantly to the total message size (e.g. a mes-
+            #   sage with a 70 MB attachment, can have an overall size larger than 100 MB).
+            [554, 'maximum email size exceeded'],
+          ],
+          'networkerror' => [
+            # - The message has too many "received headers" as it has been forwarded across multi-
+            #   ple hops. Once 25 hops have been reached, the email is rejected.
+            # - Investigate the email addresses in the communication pairs, to see what forwarders
+            #   are configured on the mail servers.
+            [554, 'mail loop detected'],
+          ],
+          'norelaying' => [
+            # - Both the sender and recipient domains specified in the transmission are external to
+            #   Mimecast, and aren't allowed to relay through the Mimecast service and/or the con-
+            #   necting IP address isn't recognized as authorized.
+            # - Mimecast customers should contact Mimecast Support to add the Authorized Outbound
+            #   address, or to take other remedial action.
+            [451, 'open relay not allowed'],
+          ],
+          'notaccept' => [
+            # - The customer account Inbound emails are disabled in the Administration Console.
+            # - Contact Mimecast Support if the account's inbound traffic should be allowed.
+            [451, 'account inbounds disabled'],
+          ],
+          'onhold' => [
+            # - The customer account outbound emails are disabled in the Administration Console.
+            # - Contact Mimecast Support if the account's outbound traffic should be allowed.
+            [451, 'account outbounds disabled'],
+
+            # - Omni Directional hostnames are enabled.
+            # - Disable Omni Directional hostnames.
+            [451, 'hostname is not authorized'],
+
+            # - Attempts are being made to journal mail that is past the set expiry threshold. The
+            #   failure will be replaced by a retry response because the message is marked for re-
+            #   try if rejected, causing the journal queue to grow.
+            # - Check to confirm there are no significant time discrepancies on the mail server.
+            #   Discontinue journaling old messages past the expiry threshold.
+            [550, 'journal message past expiration'],
+          ],
+          'policyviolation' => [
+            # - The message has triggered an Anti-Spoofing policy.
+            # - Create an Anti-Spoofing policy to take no action for the sender's address or IP ad-
+            #   dress.
+            [550, 'anti-spoofing policy - inbound not allowed'],
+            [550, 'rejected by header-based anti-spoofing policy'],
+
+            # - The message has triggered a Content Examination policy.
+            # - Either create a Content Examination Bypass policy or adjust the Content Examination
+            #   policy as required.
+            [550, 'message bounced due to content examination policy'],
+
+            # - The message has triggered a Geographical Restriction policy.
+            # - Delete or amend the policy.
+            [554, 'host network not allowed'],
+          ],
+          'rejected' => [
+            # - The sender's email address or domain has triggered a Blocked Senders Policy or
+            #   there's an SPF hard rejection.
+            # - Delete or modify the Blocked Senders policy to exclude the sender address.
+            [550, 'administrative prohibition envelope blocked'],
+
+            # - A personal block policy is in place for the email address/domain.
+            # - Remove the email address/domain from the Managed Senders list.
+            [550, 'envelope blocked – user entry'],
+            [550, 'envelope blocked – user domain entry'],
+            [550, 'rejected by header-based manually blocked senders - block for manual block'],
+
+            # - A Block Sender Policy has been applied to reject emails based on the Header From or
+            #   Envelope From address.
+            # - Delete or change the Blocked Senders policy.
+            [550, 'rejected by header-based blocked senders - block policy for header from'],
+            [550, 'envelope rejected - block policy for envelope from address'],
+          ],
+          'securityerror' => [
+            # - Messages submitted to SMTP port 587 require authentication. This error indicates
+            #   the authentication details provided were incorrect.
+            # - Check your authentication details match an internal email address in Mimecast, with
+            #   a corresponding Mimecast cloud password. Alternatively, consider sending the mes-
+            #   sage on SMTP port 25.
+            [535, 'incorrect authentication data'],
+            [550, 'submitter failed to disabled'],
+
+            # - This email has been sent using SMTP, but TLS is required by policy.
+            # - Delete or change the Secure Receipt or Secure Delivery policy enforcing TLS.
+            #   Alternatively, ensure the certificates on the mail server haven't expired. If using
+            #   a proxy server, ensure it isn't intercepting the traffic and modifying encryption
+            #   parameters.
+            [553, 'this route requires encryption (tls)'],
+
+            # - A TLS connection has been attempted using a TLS version that is lower than TLS 1.2.
+            # - Delete or change the Secure Receipt or Secure Delivery policy enforcing TLS.
+            #   Alternatively, ensure the mail server attempting to connect is using the appropri-
+            #   ate version of TLS.
+            [553, 'this route requires tls version 1.2 or greater'],
+
+            # - A secure connection was attempted using ciphers that do not meet the configured ci-
+            #   pher strength.
+            # - Delete or change the Secure Receipt or Secure Delivery policy enforcing TLS. Alter-
+            #   natively, ensure the certificates on the mail server haven't expired. If using a
+            #   proxy server, ensure it isn't intercepting the traffic and modifying encryption
+            #   parameters.
+            [553, 'this route requires high-strength ciphers'],
+
+            # - Validation on your umbrella account's domain name does not conform to your DNS.
+            # - Check you DNS has the required umbrella accounts listed as comma-separated values.
+            [554, 'configuration is invalid for this certificate'],
+          ],
+          'systemerror' => [
+            # - The Mimecast server is under maximum load.
+            # - No action is required from the end-user. The message will retry 30 times and when
+            #   server resources are available, the message is processed.
+            [451, 'unable to process connection at this time'],
+
+            # - The message was incorrectly terminated. This can be caused by:
+            #   - Files that previously contained a virus, but haven't been cleaned by an anti-virus
+            #     product, leaving traces in the message.
+            #   - Firewall issues on the sender's side.
+            #   - Incorrectly configured content rules on a security device.
+            # - Investigate the Intrusion Detection software or other SMTP protocol analyzers. If
+            #   running a Cisco Firewall, ensure the Mail- guard or SMTP Fixup module is disabled.
+            [451, 'message ended early'],
+
+            # - Generic error if the reason is unknown
+            # - Contact Mimecast Support.
+            [451, 'unable to process command'],
+
+            # - Generic error if the reason is unknown
+            # - Contact Mimecast Support.
+            [451, 'unable to process an email at this time'],
+          ],
+          'toomanyconn' => [
+            # - There are too many concurrent inbound connections for the account. The default is 20.
+            # - The IP address is automatically removed from the block list after five minutes.
+            #   Continued invalid connections result in the IP being readded to the block list. En-
+            #   sure you don't route outbound or journal messages to Mimecast from an IP address
+            #   that hasn't been authorized to do so.
+            [451, 'account service is temporarily unavailable'],
+
+            # - The sending server issues more than 100 RCPT TO entries. By default, Mimecast only
+            #   accepts 100 RCPT TO entries per message body (DATA). The error triggers the sending
+            #   mail server to provide the DATA for the first 100 recipients before it provides the
+            #   next batch of RCPT TO entries.
+            # - Most mail servers respect the transient error and treat it as a "truncation request".
+            #   If your mail server, firewall, or on-site solution doesn't respect the error, you
+            #   must ensure that no more than 100 recipients are submitted.
+            #   Note:
+            #       Solutions like SMTP Fix-Up / MailGuard and ESMTP inspection on Cisco Pix and
+            #       ASA Firewalls are known not to respect the transient error. We advise you to
+            #       disable this functionality.
+            [452, 'too many recipients'],
+
+            # - There are too many concurrent outbound connections for the account.
+            # - Send the messages in smaller chunks to recipients.
+            [550, 'exceeding outbound thread limit'],
+          ],
+          'userunknown' => [
+            # - The email address isn't a valid SMTP address.
+            # - The sender must resend the message to a valid internal email address.
+            [501, 'invalid address'],
+
+            # - The server has encountered a bad sequence of commands, or it requires an authenti-
+            #   cation.
+            # - In case of a "bad sequence", the server has pulled off its commands in the wrong
+            #   order, usually because of a broken connection. If authentication is needed, enter
+            #   your username and password.
+            [503, 'user unknown'],
+
+            # - Known recipient, LDAP, or SMTP call forwarding recipient validation checks haven't
+            #   returned a valid internal user.
+            # - The sender must resend the message to a valid internal recipient address.
+            [550, 'invalid recipient'],
+          ],
+          'virusdetected' => [
+            # - A signature was detected that could either be a virus, or a spam score over the
+            #   maximum threshold. The spam score isn't available in the Administration Console. If
+            #   you aren't a Mimecast customer but have emails rejected with this error code, con-
+            #   tact the recipient to adjust their configuration and permit your address. If unsuc-
+            #   cessful, your IT department can submit a request to review these email rejections
+            #   via our Sender Feedback form.
+            # - Anti-virus checks cannot be bypassed. Contact the sender to see if they can stop
+            #   these messages from being blocked. Anti-spam checks can be bypassed using a Per-
+            #   mitted Senders or Auto Allow policy. Rejected emails can be viewed in your Outbound
+            #   Activity and searching for the required email address.
+            [554, 'email rejected due to security policies'],
+          ],
+        }.freeze
+
+        # Detect bounce reason from Mimecast
+        # @param    [Sisimai::Fact] argvs   Parsed email object
+        # @return   [String]                The bounce reason for mimecast.com
+        def get(argvs)
+          return '' unless argvs.replycode =~ /\A[245]\d\d\z/
+          return '' unless argvs.diagnosticcode
+
+          esmtperror = argvs.diagnosticcode.downcase || ''
+          esmtpreply = argvs.replycode.to_i
+          reasontext = ''
+
+          MessagesOf.each_key do |e|
+            # Try to match the error message with message patterns defined in "MessagesOf"
+            MessagesOf[e].each do |f|
+              # Find an error reason
+              next unless esmtpreply == f[0]
+              next unless esmtperror.include?(f[1])
+              reasontext = e
+              break
+            end
+            break unless reasontext.empty?
+          end
+
+          return reasontext
+        end
+
+      end
+    end
+  end
+end
+

data/lib/sisimai/rhost/nttdocomo.rb

@@ -0,0 +1,118 @@
+module Sisimai
+  module Rhost
+    # Sisimai::Rhost detects the bounce reason from the content of Sisimai::Data object as an argument
+    # of get() method when the value of "rhost" of the object is "mfsmax.docomo.ne.jp". This class
+    # is called only Sisimai::Data class.
+    module NTTDOCOMO
+      class << self
+        MessagesOf = {
+          'mailboxfull' => %r/552 too much mail data/,
+          'toomanyconn' => %r/552 too many recipients/,
+          'syntaxerror' => %r/(?:503 bad sequence of commands|504 command parameter not implemented)/,
+        }.freeze
+
+        # Detect bounce reason from NTT DOCOMO
+        # @param    [Sisimai::Data] argvs   Parsed email object
+        # @return   [String]                The bounce reason for docomo.ne.jp
+        def get(argvs)
+          statuscode = argvs.deliverystatus          || ''
+          commandtxt = argvs.smtpcommand             || ''
+          esmtperror = argvs.diagnosticcode.downcase || ''
+          reasontext = ''
+
+          # Check the value of Status: field, an SMTP Reply Code, and the SMTP Command
+          if statuscode == '5.1.1' || statuscode == '5.0.911'
+            #    ----- Transcript of session follows -----
+            # ... while talking to mfsmax.docomo.ne.jp.:
+            # >>> RCPT To:<***@docomo.ne.jp>
+            # <<< 550 Unknown user ***@docomo.ne.jp
+            # 550 5.1.1 <***@docomo.ne.jp>... User unknown
+            # >>> DATA
+            # <<< 503 Bad sequence of commands
+            reasontext = 'userunknown'
+
+          elsif statuscode == '5.2.0'
+            #    ----- The following addresses had permanent fatal errors -----
+            # <***@docomo.ne.jp>
+            # (reason: 550 Unknown user ***@docomo.ne.jp)
+            # 
+            #    ----- Transcript of session follows -----
+            # ... while talking to mfsmax.docomo.ne.jp.:
+            # >>> DATA
+            # <<< 550 Unknown user ***@docomo.ne.jp
+            # 554 5.0.0 Service unavailable
+            # ...
+            # Final-Recipient: RFC822; ***@docomo.ne.jp
+            # Action: failed
+            # Status: 5.2.0
+            reasontext = 'filtered'
+
+          else
+            # The value of "Diagnostic-Code:" field is not empty
+            MessagesOf.each_key do |e|
+              # Try to match the error message with message patterns defined in "MessagesOf"
+              next unless esmtperror =~ MessagesOf[e]
+              reasontext = e
+              break
+            end
+          end
+
+          if reasontext.empty?
+            # A bounce reason did not decide from a status code, an error message.
+            if statuscode == '5.0.0'
+              # Status: 5.0.0
+              if commandtxt == 'RCPT'
+                # Your message to the following recipients cannot be delivered:
+                #
+                # <***@docomo.ne.jp>:
+                # mfsmax.docomo.ne.jp [203.138.181.112]:
+                # >>> RCPT TO:<***@docomo.ne.jp>
+                # <<< 550 Unknown user ***@docomo.ne.jp
+                # ...
+                #
+                # Final-Recipient: rfc822; ***@docomo.ne.jp
+                # Action: failed
+                # Status: 5.0.0
+                # Remote-MTA: dns; mfsmax.docomo.ne.jp [203.138.181.112]
+                # Diagnostic-Code: smtp; 550 Unknown user ***@docomo.ne.jp
+                reasontext = 'userunknown'
+
+              elsif commandtxt == 'DATA'
+                # <***@docomo.ne.jp>: host mfsmax.docomo.ne.jp[203.138.181.240] said:
+                # 550 Unknown user ***@docomo.ne.jp (in reply to end of DATA
+                # command)
+                # ...
+                # Final-Recipient: rfc822; ***@docomo.ne.jp
+                # Original-Recipient: rfc822;***@docomo.ne.jp
+                # Action: failed
+                # Status: 5.0.0
+                # Remote-MTA: dns; mfsmax.docomo.ne.jp
+                # Diagnostic-Code: smtp; 550 Unknown user ***@docomo.ne.jp
+                reasontext = 'rejected'
+
+              else
+                # Rejected by other SMTP commands: AUTH, MAIL,
+                #   もしもこのブロックを通過するNTTドコモからのエラーメッセージを見つけたら
+                #   https://github.com/sisimai/p5-sisimai/issues からご連絡ねがいます。
+                #
+                #   If you found a error message from mfsmax.docomo.ne.jp which passes this block,
+                #   please open an issue at https://github.com/sisimai/p5-sisimai/issues .
+              end
+            else
+              # Status: field is neither 5.0.0 nor values defined in code above
+              #   もしもこのブロックを通過するNTTドコモからのエラーメッセージを見つけたら
+              #   https://github.com/sisimai/p5-sisimai/issues からご連絡ねがいます。
+              #
+              #   If you found a error message from mfsmax.docomo.ne.jp which passes this block,
+              #
+            end
+          end
+
+          return reasontext
+        end
+
+      end
+    end
+  end
+end
+

data/lib/sisimai/rhost.rb

@@ -7,6 +7,7 @@ module Sisimai
     class << self
       # Imported from p5-Sisimail/lib/Sisimai/Rhost.pm
       RhostClass = {
+        'cox.net'                     => 'Cox',
         '.prod.outlook.com'           => 'ExchangeOnline',
         '.protection.outlook.com'     => 'ExchangeOnline',
         'laposte.net'                 => 'FrancePTT',
@@ -19,8 +20,9 @@ module Sisimai
         '.email.ua'                   => 'IUA',
         'lsean.ezweb.ne.jp'           => 'KDDI',
         'msmx.au.com'                 => 'KDDI',
+        '.mimecast.com'               => 'Mimecast',
+        'mfsmax.docomo.ne.jp'         => 'NTTDOCOMO',
         'charter.net'                 => 'Spectrum',
-        'cox.net'                     => 'Cox',
         '.qq.com'                     => 'TencentQQ',
       }.freeze
 

data/lib/sisimai/string.rb

@@ -66,8 +66,8 @@ module Sisimai
           # 3. <a href = 'http://...'>...</a> to " http://... "
           # 4. <a href = 'mailto:...'>...</a> to " Value <mailto:...> "
           plain.scrub!('?')
-          plain.gsub!(%r|<head>.+</head>|im, '')
-          plain.gsub!(%r|<style.+?>.+</style>|im, '')
+          plain.gsub!(%r|<head>.*?</head>|im, '')
+          plain.gsub!(%r|<style.*?>.*?</style>|im, '')
           plain.gsub!(%r|<a\s+href\s*=\s*['"](https?://.+?)['"].*?>(.*?)</a>|i, '[\2](\1)')
           plain.gsub!(%r|<a\s+href\s*=\s*["']mailto:([^\s]+?)["']>(.*?)</a>|i, '[\2](mailto:\1)')
 

data/lib/sisimai/version.rb

@@ -1,4 +1,4 @@
 # Define the version number of Sisimai
 module Sisimai
-  VERSION = '4.25.14'.freeze
+  VERSION = '4.25.16'.freeze
 end

data/set-of-emails/maildir/bsd/rhost-mimecast-01.eml

@@ -0,0 +1,88 @@
+Return-Path: <>
+Delivered-To: kijitora@example.co.jp
+Received: from smtp.example.co.jp
+	by neko.example.co.jp (Dovecot) with LMTP id YZv2MOmWGmDvLgAA4iEyMQ
+	for <kijitora@example.co.jp>; Thu, 02 Feb 2021 23:34:45 +0900
+Received: by smtp.example.co.jp (Postfix)
+	id PcWLPhBbNNzq4GD0; Thu,  2 Feb 2021 23:34:45 +0900 (JST)
+Date: Thu,  2 Feb 2021 23:34:45 +0900 (JST)
+From: MAILER-DAEMON@smtp.example.co.jp (Mail Delivery System)
+Subject: Undelivered Mail Returned to Sender
+To: kijitora@example.co.jp
+Auto-Submitted: auto-replied
+MIME-Version: 1.0
+Content-Type: multipart/report; report-type=delivery-status;
+	boundary="XkB0QWwjfhzQcf0c.160000000/smtp.example.co.jp"
+Content-Transfer-Encoding: 8bit
+Message-Id: <PcWLPhBbNNzq4GD0@smtp.example.co.jp>
+
+This is a MIME-encapsulated message.
+
+--XkB0QWwjfhzQcf0c.160000000/smtp.example.co.jp
+Content-Description: Notification
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 8bit
+
+This is the mail system at host smtp.example.co.jp.
+
+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
+
+<sabatora@example.com>: host
+    us-smtp-inbound-1.mimecast.com[207.211.30.221] said: 554 Host network not
+    allowed - https://community.mimecast.com/docs/DOC-1369#554
+    [z7qZw5BPd1zlDYHka4589ru.us222] (in reply to RCPT TO command)
+
+--XkB0QWwjfhzQcf0c.160000000/smtp.example.co.jp
+Content-Description: Delivery report
+Content-Type: message/delivery-status
+
+Reporting-MTA: dns; smtp.example.co.jp
+X-Postfix-Queue-ID: XkB0QWwjfhzQcf0c
+X-Postfix-Sender: rfc822; kijitora@example.co.jp
+Arrival-Date: Thu,  2 Feb 2021 23:34:45 +0900 (JST)
+
+Final-Recipient: rfc822; sabatora@example.com
+Original-Recipient: rfc822;sabatora@example.com
+Action: failed
+Status: 5.0.0
+Remote-MTA: dns; us-smtp-inbound-1.mimecast.com
+Diagnostic-Code: smtp; 554 Host network not allowed -
+    https://community.mimecast.com/docs/DOC-1369#554
+    [z7qZw5BPd1zlDYHka4589ru.us222]
+
+--XkB0QWwjfhzQcf0c.160000000/smtp.example.co.jp
+Content-Description: Undelivered Message
+Content-Type: message/rfc822
+Content-Transfer-Encoding: 8bit
+
+Return-Path: <kijitora@example.co.jp>
+Received: from 6bBckZSRc0zMvk9Z (unknown [192.0.2.2])
+	(Authenticated sender: kijitora@example.co.jp)
+	by smtp.example.co.jp (Postfix) with ESMTPSA id XkB0QWwjfhzQcf0c
+	for <sabatora@example.com>; Thu,  2 Feb 2021 23:34:45 +0900 (JST)
+From: Automated Message <kijitora@example.co.jp>
+Date: Thu, 2 Feb 2021 23:34:45 +0100
+Subject: Automatic reply : domain owner (Reg-C)
+Message-ID: <7B0s8rbG08zYDdPt.WaOHIQht053802@NEKO-NYAAN-22.LOCAL>
+To: sabatora@example.com
+X-Mailer: NEKO-NYAAN
+MIME-Version: 1.0
+Content-Type: multipart/alternative;
+	boundary="=-QX/4rTBwaN4065581=="
+Content-Transfer-Encoding: 8bit
+
+--=-QX/4rTBwaN4065581==
+Content-Type: text/plain; charset=us-ascii
+
+--=-QX/4rTBwaN4065581==--
+
+
+--XkB0QWwjfhzQcf0c.160000000/smtp.example.co.jp--

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

@@ -0,0 +1,90 @@
+Delivered-To: automated-bounces+feffeeff-0002-ebbb-8192-00101100ffefee@email.example.com
+Received: by 192.0.2.117 with SMTP id UfAUHGQO080319;
+        Thu, 29 Apr 2022 23:34:45 -0800 (PST)
+Received: by 192.0.2.116 with SMTP id zwKF2wfslXzPbG51.22.20220022322;
+        Thu, 29 Apr 2022 23:34:45 -0800 (PST)
+Return-Path: <>
+Received: from nyaan2.example.co.uk (nyaan2.example.co.uk. [192.0.2.117])
+        by mx.google.com with ESMTP id 2mcBI4Uh025855.114.2022.04.29.23.34.45;
+        Thu, 29 Apr 2022 23:34:45 -0800 (PST)
+Received-SPF: pass (google.com: domain of nyaan2.example.co.uk designates 192.0.2.117 as permitted sender) client-ip=192.0.2.117;
+Authentication-Results: mx.google.com; spf=pass (google.com: domain of nyaan2.example.co.uk designates 192.0.2.117 as permitted sender) smtp.mail=
+Received: by nyaan2.example.co.uk (Postfix)
+	id zyrWXqvX71zdjmrD; Thu, 29 Apr 2022 23:34:45 +0000 (GMT)
+Date: Thu, 29 Apr 2022 23:34:45 +0000 (GMT)
+From: MAILER-DAEMON@nyaan2.example.co.uk (Mail Delivery System)
+Subject: Undelivered Mail Returned to Sender
+To: automated-bounces+7BE1D472-4B2D-11E1-9E82-A342CB4AA966@email.example.com
+Auto-Submitted: auto-replied
+MIME-Version: 1.0
+Content-Type: multipart/report; report-type=delivery-status;
+	boundary="316C411E8435.000000000/nyaan2.example.co.uk"
+Message-Id: <20220429233445.zyrWXqvX71zdjmrD@nyaan2.example.co.uk>
+
+This is a MIME-encapsulated message.
+
+--316C411E8435.000000000/nyaan2.example.co.uk
+Content-Description: Notification
+Content-Type: text/plain; charset=us-ascii
+
+This is the mail system at host nyaan2.example.co.uk.
+
+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@sample.co.uk>: host service222.mimecast.com[91.220.42.51] said: 554
+    email rejected due to security policies - MCSpamSignature.sa.2.2 (in reply
+    to end of DATA command)
+
+--316C411E8435.000000000/nyaan2.example.co.uk
+Content-Description: Delivery report
+Content-Type: message/delivery-status
+
+Reporting-MTA: dns; nyaan2.example.co.uk
+X-Postfix-Queue-ID: 316C411E8435
+X-Postfix-Sender: rfc822; automated-bounces+FFFFFFFF-0000-EEEE-EEEE-00000000EEEE@email.example.com
+Arrival-Date: Thu, 29 Apr 2022 23:34:45 +0000 (GMT)
+
+Final-Recipient: rfc822; kijitora@sample.co.uk
+Action: failed
+Status: 5.0.0
+Remote-MTA: dns; service222.mimecast.com
+Diagnostic-Code: smtp; 554 email rejected due to security policies -
+    MCSpamSignature.sa.2.2
+
+--316C411E8435.000000000/nyaan2.example.co.uk
+Content-Description: Undelivered Message
+Content-Type: message/rfc822
+
+Received: by nyaan2.example.co.uk (Postfix, from userid 222)
+	id 316C411E8435; Thu, 29 Apr 2022 23:34:45 +0000 (GMT)
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7bit
+Content-Type: multipart/related; boundary="_----------=_1055808412000000"
+Date: Thu, 29 Apr 2022 23:34:45 +0000
+From: Neko <neko@email.example.com>
+Subject: Nyaan
+To: Kijitora Nyaan <kijitora@sample.co.uk>
+Message-Id: <20220429.0000.316C411E8435@nyaan2.example.co.uk>
+
+This is a multi-part message in MIME format.
+
+--_----------=_1055808412000000
+Content-Disposition: inline
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/html
+
+Nyaan
+
+--_----------=_1055808412000000--
+
+
+--316C411E8435.000000000/nyaan2.example.co.uk--
+