sisimai 4.25.16-java → 5.0.2-java

data/lib/sisimai/rhost/kddi.rb

@@ -1,27 +1,25 @@
 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 "lsean.ezweb.ne.jp" or "msmx.au.com".
-    # This class is called only Sisimai::Data class.
+    # Sisimai::Rhost detects the bounce reason from the content of Sisimai::Fact object as an argument
+    # of get() method when the value of "rhost" of the object is "lsean.ezweb.ne.jp" or "msmx.au.com".
+    # This class is called only Sisimai::Fact class.
     module KDDI
       class << self
-        # Imported from p5-Sisimail/lib/Sisimai/Rhost/KDDI.pm
         MessagesOf = {
           'filtered'    => '550 : User unknown',  # The response was: 550 : User unknown
           'userunknown' => '>: User unknown',     # The response was: 550 <...>: User unknown
         }.freeze
 
         # Detect bounce reason from au (KDDI)
-        # @param    [Sisimai::Data] argvs   Parsed email object
+        # @param    [Sisimai::Fact] argvs   Parsed email object
         # @return   [String]                The bounce reason for au.com or ezweb.ne.jp
         def get(argvs)
-          statusmesg = argvs.diagnosticcode
+          statusmesg = argvs['diagnosticcode']
           reasontext = ''
 
           MessagesOf.each_key do |e|
             # Try to match the error message with message patterns defined in $MessagesOf
-            next unless statusmesg.end_with?(MessagesOf[e])
+            next unless statusmesg.include?(MessagesOf[e])
             reasontext = e
             break
           end

data/lib/sisimai/rhost/{exchangeonline.rb → microsoft.rb}

@@ -1,15 +1,70 @@
 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 "*.protection.outlook.com". This class is called only Sisimai::Data class.
-    # 
+    # Sisimai::Rhost detects the bounce reason from the content of Sisimai::Fact object as an argument
+    # of get() method when the value of "rhost" of the object is *.protection.outlook.com. This class
+    # is called only Sisimai::Fact class.
+    #
     # https://technet.microsoft.com/en-us/library/bb232118
     # https://learn.microsoft.com/en-us/Exchange/mail-flow-best-practices/non-delivery-reports-in-exchange-online/non-delivery-reports-in-exchange-online
     # https://learn.microsoft.com/en-us/Exchange/mail-flow/non-delivery-reports-and-bounce-messages/non-delivery-reports-and-bounce-messages
-    module ExchangeOnline
+    module Microsoft
       class << self
         MessagesOf = {
+          'authfailure' => [
+            # - Access denied, a message sent over IPv6 [2a01:111:f200:2004::240] must pass either
+            #   SPF or DKIM validation, this message is not signed
+            # - The sending message sent over IPv6 must pass either SPF or DKIM.
+            ['4.7.26', 0, 0, 'must pass either spf or dkim validation, this message is not signed'],
+
+            # - Records are DNSSEC authentic, but one or multiple of these scenarios occurred:
+            #   - The destination mail server's certificate doesn't match with what is expected per
+            #     the authentic TLSA record.
+            #   - Authentic TLSA record is misconfigured.
+            #   - Destination domain is being attacked.
+            #   - Any other DANE failure.
+            # - This message usually indicates an issue on the destination email server. Check the
+            #   validity of recipient address and determine if the destination server is configured
+            #   correctly to receive messages. 
+            # - For more information about DANE, see: https://datatracker.ietf.org/doc/html/rfc7671
+            ['4.7.323', 0, 0, 'tlsa-invalid: The domain failed dane validation'],
+            ['5.7.323', 0, 0, 'tlsa-invalid: The domain failed dane validation'],
+
+            # - The destination domain indicated it was DNSSEC-authentic, but Exchange Online was 
+            #   not able to verify it as DNSSEC-authentic.
+            ['4.7.324', 0, 0, 'dnssec-invalid: destination domain returned invalid dnssec records'],
+            ['5.7.324', 0, 0, 'dnssec-invalid: destination domain returned invalid dnssec records'],
+
+            # - This happens when the presented certificate identities (CN and SAN) of a destina-
+            #   tion SMTP target host don't match any of the domains or MX host.
+            # - This message usually indicates an issue on the destination email server. Check the
+            #   validity of recipient address and determine if the destination server is configured
+            #   correctly to receive messages. For more information, see How SMTP DNS-based Authen-
+            #   tication of Named Entities (DANE) works to secure email communications.
+            ['4.7.325', 0, 0, 'certificate-host-mismatch: remote certificate must have a common name or subject alternative name matching the hostname (dane)'],
+            ['5.7.325', 0, 0, 'certificate-host-mismatch: remote certificate must have a common name or subject alternative name matching the hostname (dane)'],
+
+            # - The destination email system uses SPF to validate inbound mail, and there's a prob-
+            #   lem with your SPF configuration.
+            ['5.7.23', 0, 0, 'the message was rejected because of sender policy framework violation'],
+
+            # - DNSSEC checks have passed, yet upon establishing the connection the destination
+            #   mail server provides a certificate that is expired.
+            # - A valid X.509 certificate that isn't expired must be presented. X.509 certificates
+            #   must be renewed after their expiration, commonly annually.
+            ['5.7.322', 0, 0, "certificate-expired: destination mail server's certificate is expired"],
+
+            # - Access denied, sending domain [$SenderDomain] does not pass DMARC verification
+            # - The sender's domain in the 5322.From address doesn't pass DMARC.
+            ['5.7.509', 0, 0, 'does not pass dmarc verification'],
+          ],
+          'badreputation' => [
+            # Undocumented error messages ---------------------------------------------------------
+            # - status=deferred (host outlook-com.olc.protection.outlook.com[192.0.2.255] said:
+            #   451 4.7.650 The mail server [192.0.2.5] has been temporarily rate limited due to IP
+            #   reputation. For e-mail delivery information, see https://postmaster.live.com (S775)
+            #   [***.prod.protection.outlook.com] (in reply to MAIL FROM command))
+            ['4.7.650', 0, 0, 'has been temporarily rate limited due to ip reputation'],
+          ],
           'blocked' => [
             # Exchange Server 2019 ----------------------------------------------------------------
             # - Transient network issues or server problems that might eventually correct them-
@@ -87,58 +142,6 @@ module Sisimai
             # - 550 5.7.1 Unfortunately, messages from [10.0.2.5] weren't sent. Please contact your
             #   Internet service provider since part of their network is on our block list (S3150). 
             ['5.7.1', 0, 0, 'part of their network is on our block list (s3150)'],
-
-            # - Access denied, a message sent over IPv6 [2a01:111:f200:2004::240] must pass either
-            #   SPF or DKIM validation, this message is not signed
-            # - The sending message sent over IPv6 must pass either SPF or DKIM.
-            ['4.7.26', 0, 0, 'must pass either spf or dkim validation, this message is not signed'],
-
-            # - Records are DNSSEC authentic, but one or multiple of these scenarios occurred:
-            #   - The destination mail server's certificate doesn't match with what is expected per
-            #     the authentic TLSA record.
-            #   - Authentic TLSA record is misconfigured.
-            #   - Destination domain is being attacked.
-            #   - Any other DANE failure.
-            # - This message usually indicates an issue on the destination email server. Check the
-            #   validity of recipient address and determine if the destination server is configured
-            #   correctly to receive messages. 
-            # - For more information about DANE, see: https://datatracker.ietf.org/doc/html/rfc7671
-            ['4.7.323', 0, 0, 'tlsa-invalid: The domain failed dane validation'],
-            ['5.7.323', 0, 0, 'tlsa-invalid: The domain failed dane validation'],
-
-            # - The destination domain indicated it was DNSSEC-authentic, but Exchange Online was 
-            #   not able to verify it as DNSSEC-authentic.
-            ['4.7.324', 0, 0, 'dnssec-invalid: destination domain returned invalid dnssec records'],
-            ['5.7.324', 0, 0, 'dnssec-invalid: destination domain returned invalid dnssec records'],
-
-            # - This happens when the presented certificate identities (CN and SAN) of a destina-
-            #   tion SMTP target host don't match any of the domains or MX host.
-            # - This message usually indicates an issue on the destination email server. Check the
-            #   validity of recipient address and determine if the destination server is configured
-            #   correctly to receive messages. For more information, see How SMTP DNS-based Authen-
-            #   tication of Named Entities (DANE) works to secure email communications.
-            ['4.7.325', 0, 0, 'certificate-host-mismatch: remote certificate must have a common name or subject alternative name matching the hostname (dane)'],
-            ['5.7.325', 0, 0, 'certificate-host-mismatch: remote certificate must have a common name or subject alternative name matching the hostname (dane)'],
-
-            # - The destination email system uses SPF to validate inbound mail, and there's a prob-
-            #   lem with your SPF configuration.
-            ['5.7.23', 0, 0, 'the message was rejected because of sender policy framework violation'],
-
-            # - DNSSEC checks have passed, yet upon establishing the connection the destination
-            #   mail server provides a certificate that is expired.
-            # - A valid X.509 certificate that isn't expired must be presented. X.509 certificates
-            #   must be renewed after their expiration, commonly annually.
-            ['5.7.322', 0, 0, "certificate-expired: destination mail server's certificate is expired"],
-
-            # - Access denied, sending domain [$SenderDomain] does not pass DMARC verification
-            # - The sender's domain in the 5322.From address doesn't pass DMARC.
-            ['5.7.509', 0, 0, 'does not pass dmarc verification'],
-            # Undocumented error messages ---------------------------------------------------------
-            # - status=deferred (host outlook-com.olc.protection.outlook.com[192.0.2.255] said:
-            #   451 4.7.650 The mail server [192.0.2.5] has been temporarily rate limited due to IP
-            #   reputation. For e-mail delivery information, see https://postmaster.live.com (S775)
-            #   [***.prod.protection.outlook.com] (in reply to MAIL FROM command))
-            ['4.7.650', 0, 0, 'has been temporarily rate limited due to ip reputation'],
           ],
           'contenterror' => [
             # Exchange Server 2019 ----------------------------------------------------------------
@@ -477,6 +480,53 @@ module Sisimai
             ['5.2.1', 0, 0, 'content filter agent quarantined this message'],
           ],
           'speeding' => [
+            # Exchange Online ---------------------------------------------------------------------
+	        # - The recipient mailbox's ability to accept messages is being throttled because it's
+            #   receiving too many messages too quickly. This is done so a single recipient's mail
+            #   processing doesn't unfairly impact other recipients sharing the same mailbox data-
+            #   base.
+            ['4.3.2', 0, 0, 'storedrv.deliver; recipient thread limit exceeded'],
+
+            # - The sender has exceeded the recipient rate limit as described in Sending limits.
+            # - This could indicate the account has been compromised and is being used to send
+            #   spam.
+            ['5.1.90', 0, 0, "your message can't be sent because you've reached your daily limit for message recipients"],
+
+            # - The sender has exceeded the recipient rate limit or the message rate limit as de-
+            #   scribed in Sending limits.
+            # - This could indicate the account has been compromised and is being used to send
+            #   spam.
+            ['5.2.2', 0, 0, 'submission quota exceeded'],
+
+            # - The sender has exceeded the maximum number of messages they're allowed to send per
+            #   hour to a specific recipient in Exchange Online.
+            # - The automated mailer or sender should try again later, and reduce the number of
+            #   messages they send per hour to a specific recipient. This limit helps protect
+            #   Microsoft 365 or Office 365 users from rapidly filling their inboxes with a large
+            #   number of messages from errant automated notification systems or other single-send-
+            #   er mail storms.
+            ['5.2.121', 0, 0, "recipient's per hour message receive limit from specific sender exceeded"],
+
+            # - The Microsoft 365 or Office 365 recipient has exceeded the number of messages they
+            #   can receive per hour from all senders.
+            # - The automated mailer or sender should try again later, and reduce the number of
+            #   messages they send per hour to a specific recipient. This limit helps protect
+            #   Microsoft 365 and Office 365 users from rapidly filling their inboxes with a large
+            #   number of messages from errant automated notification systems or other mail storms.
+            ['5.2.122', 0, 0, "recipient's per hour message receive limit exceeded"],
+
+            # - Access denied, [$SenderIPAddress] has exceeded permitted limits within $range range
+            # - The sender's IPv6 range has attempted to send too many messages in too short a time
+            #   period.
+            ['5.7.508', 0, 0, 'has exceeded permitted limits within'],
+
+            # - The majority of traffic from this tenant has been detected as suspicious and has
+            #   resulted in a ban on sending ability for the tenant.
+            # - Ensure that any compromises or open relays have been resolved, and then contact
+            #   support through your regular channel. For more information, see Fix email delivery
+            #   issues for error codes 5.7.700 through 5.7.750 in Exchange Online.
+            ['5.7.', 700, 749, 'access denied, tenant has exceeded threshold'],
+            ['5.7.', 700, 749, 'access denied, traffic not accepted from this ip'],
           ],
           'suspend' => [
             # Exchange Online ---------------------------------------------------------------------
@@ -588,54 +638,6 @@ module Sisimai
 
             # Previous versions of Exchange Server ------------------------------------------------
             ['5.2.122', 0, 0, 'the recipient has exceeded their limit for'],
-
-            # Exchange Online ---------------------------------------------------------------------
-            # - The recipient mailbox's ability to accept messages is being throttled because it's
-            #   receiving too many messages too quickly. This is done so a single recipient's mail
-            #   processing doesn't unfairly impact other recipients sharing the same mailbox data-
-            #   base.
-            ['4.3.2', 0, 0, 'storedrv.deliver; recipient thread limit exceeded'],
-
-            # - The sender has exceeded the recipient rate limit as described in Sending limits.
-            # - This could indicate the account has been compromised and is being used to send
-            #   spam.
-            ['5.1.90', 0, 0, "your message can't be sent because you've reached your daily limit for message recipients"],
-
-            # - The sender has exceeded the recipient rate limit or the message rate limit as de-
-            #   scribed in Sending limits.
-            # - This could indicate the account has been compromised and is being used to send
-            #   spam.
-            ['5.2.2', 0, 0, 'submission quota exceeded'],
-
-            # - The sender has exceeded the maximum number of messages they're allowed to send per
-            #   hour to a specific recipient in Exchange Online.
-            # - The automated mailer or sender should try again later, and reduce the number of
-            #   messages they send per hour to a specific recipient. This limit helps protect
-            #   Microsoft 365 or Office 365 users from rapidly filling their inboxes with a large
-            #   number of messages from errant automated notification systems or other single-send-
-            #   er mail storms.
-            ['5.2.121', 0, 0, "recipient's per hour message receive limit from specific sender exceeded"],
-
-            # - The Microsoft 365 or Office 365 recipient has exceeded the number of messages they
-            #   can receive per hour from all senders.
-            # - The automated mailer or sender should try again later, and reduce the number of
-            #   messages they send per hour to a specific recipient. This limit helps protect
-            #   Microsoft 365 and Office 365 users from rapidly filling their inboxes with a large
-            #   number of messages from errant automated notification systems or other mail storms.
-            ['5.2.122', 0, 0, "recipient's per hour message receive limit exceeded"],
-
-            # - Access denied, [$SenderIPAddress] has exceeded permitted limits within $range range
-            # - The sender's IPv6 range has attempted to send too many messages in too short a time
-            #   period.
-            ['5.7.508', 0, 0, 'has exceeded permitted limits within'],
-
-            # - The majority of traffic from this tenant has been detected as suspicious and has
-            #   resulted in a ban on sending ability for the tenant.
-            # - Ensure that any compromises or open relays have been resolved, and then contact
-            #   support through your regular channel. For more information, see Fix email delivery
-            #   issues for error codes 5.7.700 through 5.7.750 in Exchange Online.
-            ['5.7.', 700, 749, 'access denied, tenant has exceeded threshold'],
-            ['5.7.', 700, 749, 'access denied, traffic not accepted from this ip'],
           ],
           'userunknown' => [
             # Exchange Server 2019 ----------------------------------------------------------------
@@ -700,17 +702,17 @@ module Sisimai
           ],
         }.freeze
 
-        # Detect bounce reason from Exchange Online
-        # @param    [Sisimai::Data] argvs   Parsed email object
+        # Detect bounce reason from Exchange Server 2019 or older and Exchange Online
+        # @param    [Sisimai::Fact] argvs   Parsed email object
         # @return   [String]                The bounce reason for Exchange Online
         def get(argvs)
-          return argvs.reason unless argvs.reason.empty?
-          return '' if argvs.diagnosticcode.empty?
-          return '' if argvs.deliverystatus.empty?
-          return '' unless argvs.deliverystatus =~ /\A[245][.]\d[.]\d+\z/
+          return argvs['reason'] unless argvs['reason'].empty?
+          return '' if argvs['diagnosticcode'].empty?
+          return '' if argvs['deliverystatus'].empty?
+          return '' unless Sisimai::SMTP::Status.test(argvs['deliverystatus'])
 
-          statuscode = argvs.deliverystatus
-          esmtperror = argvs.diagnosticcode.downcase
+          statuscode = argvs['deliverystatus']
+          esmtperror = argvs['diagnosticcode'].downcase
           thirddigit = statuscode.split('.')[-1].to_i
           reasontext = ''
 
@@ -735,7 +737,6 @@ module Sisimai
             break unless reasontext.empty?
           end
 
-
           return reasontext
         end
 

data/lib/sisimai/rhost/mimecast.rb

@@ -1,28 +1,36 @@
 module Sisimai
   module Rhost
-    # Sisimai::Rhost detects the bounce reason from the content of Sisimai::Data object as an argu-
+    # Sisimai::Rhost detects the bounce reason from the content of Sisimai::Fact 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'],
+          # https://community.mimecast.com/s/article/email-security-cloud-gateway-mimecast-smtp-error-codes
+          'authfailure' => [
+            # - 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'],
 
-            # - 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 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'],
+          ],
+          'badreputation' => [
             # - 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.
@@ -36,33 +44,28 @@ module Sisimai
             #   Note:
             #     You can request a review of your source IP ranges by completing our online form.
             [550, 'local ct ip reputation - (reject)'],
+          ],
+          '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 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
@@ -74,6 +77,12 @@ module Sisimai
             [554, 'maximum email size exceeded'],
           ],
           'networkerror' => [
+            # - The recipients' domains have MX records configured incorrectly
+            # - Check and remove any MX records that point to hostnames with outbound references.
+            #   Only Inbound smart hosts are supported on MX records.
+            [451, 'the incorrect hostname used for inbounds'],
+            [550, 'the incorrect hostname used for inbounds'],
+
             # - 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
@@ -133,8 +142,8 @@ module Sisimai
 
             # - 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, '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
@@ -261,11 +270,11 @@ module Sisimai
         # @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
+          return '' unless Sisimai::SMTP::Reply.test(argvs['replycode'])
+          return '' unless argvs['diagnosticcode']
 
-          esmtperror = argvs.diagnosticcode.downcase || ''
-          esmtpreply = argvs.replycode.to_i
+          esmtperror = argvs['diagnosticcode'].downcase || ''
+          esmtpreply = argvs['replycode'].to_i
           reasontext = ''
 
           MessagesOf.each_key do |e|

data/lib/sisimai/rhost/nttdocomo.rb

@@ -1,23 +1,23 @@
 module Sisimai
   module Rhost
-    # Sisimai::Rhost detects the bounce reason from the content of Sisimai::Data object as an argument
+    # Sisimai::Rhost detects the bounce reason from the content of Sisimai::Fact 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.
+    # is called only Sisimai::Fact 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)/,
+          'mailboxfull' => ['552 too much mail data'],
+          'toomanyconn' => ['552 too many recipients'],
+          'syntaxerror' => ['503 bad sequence of commands', '504 command parameter not implemented'],
         }.freeze
 
         # Detect bounce reason from NTT DOCOMO
-        # @param    [Sisimai::Data] argvs   Parsed email object
+        # @param    [Sisimai::Fact] 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 || ''
+          statuscode = argvs['deliverystatus']          || ''
+          thecommand = argvs['smtpcommand']             || ''
+          esmtperror = argvs['diagnosticcode'].downcase || ''
           reasontext = ''
 
           # Check the value of Status: field, an SMTP Reply Code, and the SMTP Command
@@ -51,7 +51,7 @@ module Sisimai
             # 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]
+              next unless MessagesOf[e].any? { |a| esmtperror.include?(a) }
               reasontext = e
               break
             end
@@ -61,7 +61,7 @@ module Sisimai
             # 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'
+              if thecommand == 'RCPT'
                 # Your message to the following recipients cannot be delivered:
                 #
                 # <***@docomo.ne.jp>:
@@ -77,7 +77,7 @@ module Sisimai
                 # Diagnostic-Code: smtp; 550 Unknown user ***@docomo.ne.jp
                 reasontext = 'userunknown'
 
-              elsif commandtxt == 'DATA'
+              elsif thecommand == '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)

data/lib/sisimai/rhost/spectrum.rb

@@ -1,21 +1,19 @@
 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 "destination" of
-    # the object is "charter.net". This class is called only Sisimai::Data class.
+    # Sisimai::Rhost detects the bounce reason from the content of Sisimai::Fact object as an argument
+    # of get() method when the value of "destination" of the object is "charter.net".  This class is
+    # called only Sisimai::Fact class.
     module Spectrum
       class << self
-        # Imported from p5-Sisimail/lib/Sisimai/Rhost/Spectrum.pm
         ErrorCodes = {
           # https://www.spectrumbusiness.net/support/internet/understanding-email-error-codes
           #   Error codes are placed in one of two categories: incoming or outgoing.
-          #   1. If you’re trying to send an email to a Charter email address from
-          #      a non-Charter email address (such as Gmail, Yahoo, Hotmail, etc.),
-          #      you may receive an error that begins with AUP#I, followed by four numbers.
+          #   1. If you are trying to send an email to a Charter email address from a non-Charter email
+          #      address (such as Gmail, Yahoo, Hotmail, etc.), you may receive an error that begins
+          #      with AUP#I, followed by four numbers.
           #
-          #   2. If you are trying to send an email from a Charter email address
-          #      to an outgoing recipient, you may get an error code beginning with
-          #      AUP#O, also followed by four numbers.
+          #   2. If you are trying to send an email from a Charter email address to an outgoing recipient,
+          #      you may get an error code beginning with AUP#O, also followed by four numbers.
           #
           1000 => 'blocked',         # Your IP address has been blocked due to suspicious activity. 
           1010 => 'rejected',        # This email account has been blocked from sending emails due to suspicious activity.
@@ -39,11 +37,11 @@ module Sisimai
         ].freeze
 
         # Detect bounce reason from https://www.spectrum.com/
-        # @param    [Sisimai::Data] argvs   Parsed email object
+        # @param    [Sisimai::Fact] argvs   Parsed email object
         # @return   [String, Nil]           The bounce reason at Spectrum
         # @since v4.25.8
         def get(argvs)
-          statusmesg = argvs.diagnosticcode
+          statusmesg = argvs['diagnosticcode']
           codenumber = 0
 
           if cv = statusmesg.match(/AUP#[-A-Za-z]*(\d{4})/)

data/lib/sisimai/rhost/{tencentqq.rb → tencent.rb}

@@ -1,11 +1,10 @@
 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 "mx*.qq.com". This class is called only Sisimai::Data class.
-    module TencentQQ
+    # Sisimai::Rhost detects the bounce reason from the content of Sisimai::Fact object as an argument
+    # of get() method when the value of "rhost" of the object is "mx*.qq.com". This class is called
+    # only Sisimai::Fact class.
+    module Tencent
       class << self
-        # Imported from p5-Sisimail/lib/Sisimai/Rhost/TencentQQ.pm
         MessagesOf = {
           # https://service.mail.qq.com/cgi-bin/help?id=20022
           'dmarc check failed'                    => 'blocked',
@@ -27,12 +26,12 @@ module Sisimai
         }.freeze
 
         # Detect bounce reason from Tencent QQ
-        # @param    [Sisimai::Data] argvs   Parsed email object
+        # @param    [Sisimai::Fact] argvs   Parsed email object
         # @return   [String]                The bounce reason at Tencent QQ
         def get(argvs)
-          return argvs.reason unless argvs.reason.empty?
+          return argvs['reason'] unless argvs['reason'].empty?
 
-          statusmesg = argvs.diagnosticcode.downcase
+          statusmesg = argvs['diagnosticcode'].downcase
           reasontext = ''
 
           MessagesOf.each_key do |e|