sisimai 5.4.1-java → 5.6.0-java

data/lib/sisimai/rhost/microsoft.rb

@@ -131,12 +131,21 @@ module Sisimai
             ['5.4.11', 0, 0, 'agent generated message depth exceeded'],
             ['5.5.6',  0, 0, 'invalid message content'],
           ],
-          'exceedlimit' => [
+          'emailtoolarge' => [
             # Exchange Server 2019 ----------------------------------------------------------------
             # - The message is too large. Send the message again without any attachments, or confi-
             #   gure a larger message size limit for the recipient. For more information, see Re-
             #   cipient limits.
             ['5.2.3', 0, 0, 'resolver.rst.recipsizelimit; message too large for this recipient'],
+
+            # - The message is too large. This error can be generated by the source or destination
+            #   messaging system. Send the message again without any attachments, or configure a
+            #   larger message size limit. For more information, see Message size and recipient
+            #   limits in Exchange Server.
+            ['5.3.4', 0, 0, 'message size exceeds fixed maximum message size'],
+
+            # Previous versions of Exchange Server ------------------------------------------------
+            ['5.3.4', 0, 0, 'message too big for system'],
           ],
           'expired' => [
             # Exchange Server 2019 ----------------------------------------------------------------
@@ -205,9 +214,9 @@ module Sisimai
             # - 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.51',  0, 0, 'restrictdomainstoipaddresses or restrictdomainstocertificate'],
-            ['4.7.321', 0, 0, 'starttls-not-supported: destination mail server must support tls to receive mail'],
-            ['5.7.321', 0, 0, 'starttls-not-supported: destination mail server must support tls to receive mail'],
-            ['5.7.322', 0, 0, "certificate-expired: destination mail server's certificate is expired"],
+            ['4.7.321', 0, 0, 'starttls-not-supported:'],
+            ['5.7.321', 0, 0, 'starttls-not-supported:'],
+            ['5.7.322', 0, 0, "certificate-expired:"],
 
             # - 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
@@ -219,13 +228,13 @@ module Sisimai
             #   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'],
+            ['4.7.323', 0, 0, 'tlsa-invalid:'],
+            ['5.7.323', 0, 0, 'tlsa-invalid:'],
 
             # - 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'],
+            ['4.7.324', 0, 0, 'dnssec-invalid:'],
+            ['5.7.324', 0, 0, 'dnssec-invalid:'],
 
             # - 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.
@@ -233,8 +242,8 @@ module Sisimai
             #   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)'],
+            ['4.7.325', 0, 0, 'certificate-host-mismatch:'],
+            ['5.7.325', 0, 0, 'certificate-host-mismatch:'],
           ],
           'mailboxfull' => [
             # Exchange Server 2019 ----------------------------------------------------------------
@@ -243,17 +252,6 @@ module Sisimai
             #   figure storage quotas for a mailbox.
             ['5.2.2', 0, 0, 'mailbox full'],
           ],
-          'mesgtoobig' => [
-            # Exchange Server 2019 ----------------------------------------------------------------
-            # - The message is too large. This error can be generated by the source or destination
-            #   messaging system. Send the message again without any attachments, or configure a
-            #   larger message size limit. For more information, see Message size and recipient
-            #   limits in Exchange Server.
-            ['5.3.4', 0, 0, 'message size exceeds fixed maximum message size'],
-
-            # Previous versions of Exchange Server ------------------------------------------------
-            ['5.3.4', 0, 0, 'message too big for system'],
-          ],
           'networkerror' => [
             # Exchange Server 2019 ----------------------------------------------------------------
             # - There's a DNS or network adapter configuration issue on the Exchange server. Verify
@@ -372,6 +370,78 @@ module Sisimai
             #   Mail flow rule actions in Exchange Server.
             ['5.7.', 900, 999, 'delivery not authorized, message refused'],
           ],
+          'ratelimited' => [
+            # Exchange Server 2019 ----------------------------------------------------------------
+            # - The combined total of recipients on the To, Cc, and Bcc lines of the message ex-
+            #   ceeds the total number of recipients allowed in a single message for the organiza-
+            #   tion, Receive connector, or sender. For more information, see Message size and re-
+            #   cipient limits in Exchange Server.
+            ['5.5.3', 0, 0, 'too many recipients'],
+
+            # 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 message has more than 200 SMTP envelope recipients from the same domain.
+            # - An envelope recipient is the original, unexpanded recipient that's used in the RCPT
+            #   TO command to transmit the message between SMTP servers. When this error is return-
+            #   ed by Microsoft 365 or Office 365, the sending server must break up the number of
+            #   envelope recipients into smaller chunks (chunking) and resend the message.
+            ['4.5.3', 0, 0, 'too many recipients'],
+
+            # - 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, "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"],
+
+            # - 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"],
+
+            # - 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, 'tenant has exceeded threshold'],
+            ['5.7.', 700, 749, 'traffic not accepted from this ip'],
+
+            # - 451 4.7.652 The mail server [192.0.2.251] has exceeded the maximum number of
+            #   connections. (S3115) [Name=Protocol Filter Agent][AGT=PFA][MxId=11BA9B3FA168ABBF]
+            #   [BN3PEPF0000B370.namprd21.prod.outlook.com 2025-02-20T14:30:32.425Z 08DD4D9FD5AFF45C]
+            #   (in reply to MAIL FROM command))
+            ["4.7.652", 0, 0, "has exceeded the maximum number of connections"],
+
+            # Previous versions of Exchange Server ------------------------------------------------
+            ['5.2.122', 0, 0, 'the recipient has exceeded their limit for'],
+          ],
           'rejected' => [
             # Exchange Server 2019 ----------------------------------------------------------------
             # - There's a problem with the sender's email address. Verify the sender's email ad-
@@ -490,55 +560,6 @@ module Sisimai
             #   sender exceptions for content filtering.
             ['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 ---------------------------------------------------------------------
             # - The recipient address that you're attempting to contact isn't valid.
@@ -595,7 +616,7 @@ module Sisimai
             #   is disabled. For this scenario to work, the organization's Office 365 administrator
             #   should either enable Journaling Archive or change the journaling rule to journal
             #   messages to a different location.
-            ['5.3.190', 0, 0, 'journaling on-premises messages to microsoft 365 or office 365 not supported when journaling archive is disabled'],
+            ['5.3.190', 0, 0, 'when journaling archive is disabled'],
 
             # Previous versions of Exchange Server ------------------------------------------------
             ['5.0.0',  0, 0, 'helo / ehlo requires domain address'],
@@ -641,31 +662,6 @@ module Sisimai
             #   machines.
             ['4.3.1', 0, 0, 'insufficient system resources'],
           ],
-          'toomanyconn' => [
-            # Exchange Server 2019 ----------------------------------------------------------------
-            # - The combined total of recipients on the To, Cc, and Bcc lines of the message ex-
-            #   ceeds the total number of recipients allowed in a single message for the organiza-
-            #   tion, Receive connector, or sender. For more information, see Message size and re-
-            #   cipient limits in Exchange Server.
-            ['5.5.3', 0, 0, 'too many recipients'],
-            
-            # Exchange Online ---------------------------------------------------------------------
-            # - The message has more than 200 SMTP envelope recipients from the same domain.
-            # - An envelope recipient is the original, unexpanded recipient that's used in the RCPT
-            #   TO command to transmit the message between SMTP servers. When this error is return-
-            #   ed by Microsoft 365 or Office 365, the sending server must break up the number of
-            #   envelope recipients into smaller chunks (chunking) and resend the message.
-            ['4.5.3', 0, 0, 'too many recipients'],
-
-            # - 451 4.7.652 The mail server [192.0.2.251] has exceeded the maximum number of
-            #   connections. (S3115) [Name=Protocol Filter Agent][AGT=PFA][MxId=11BA9B3FA168ABBF]
-            #   [BN3PEPF0000B370.namprd21.prod.outlook.com 2025-02-20T14:30:32.425Z 08DD4D9FD5AFF45C]
-            #   (in reply to MAIL FROM command))
-            ["4.7.652", 0, 0, "has exceeded the maximum number of connections"],
-
-            # Previous versions of Exchange Server ------------------------------------------------
-            ['5.2.122', 0, 0, 'the recipient has exceeded their limit for'],
-          ],
           'userunknown' => [
             # Exchange Server 2019 ----------------------------------------------------------------
             # - The recipient's email address is incorrect (the recipient doesn't exist in the des-
@@ -728,6 +724,55 @@ module Sisimai
             ['5.1.2', 0, 0, 'invalid x.400 address'],
           ],
         }.freeze
+        ErrorCodes = {
+          #  The mail server IP connecting to Outlook.com server has exceeded the rate limit allowed.
+          #  Reason for rate limitation is related to IP/domain reputation.
+          "RP-001" => ["421", "badreputation"],
+
+          #  The mail server IP connecting to Outlook.com server has exceeded the rate limit allowed
+          #  on this connection. Reason for rate limitation is related to IP/domain reputation.
+          "RP-002" => ["421", "badreputation"],
+
+          #  The mail server IP connecting to Outlook.com server has exceeded the connection limit
+          #  allowed. Reason for limitation is related to IP/domain reputation.
+          "RP-003" => ["421", "badreputation"],
+
+          #  Mail rejected by Outlook.com for policy reasons. Reasons for rejection may be related
+          #  to content with spam-like characteristics or IP/domain reputation. 
+          "SC-001" => ["550", "badreputation"],
+
+          #  Mail rejected by Outlook.com for policy reasons. The mail server IP connecting to
+          #  Outlook.com has exhibited namespace mining behavior.
+          "SC-002" => ["550", "policyviolation"],
+
+          #  Mail rejected by Outlook.com for policy reasons. Your IP address appears to be an
+          #  open proxy/relay.
+          "SC-003" => ["550", "blocked"],
+
+          #  Mail rejected by Outlook.com for policy reasons. A block has been placed against your
+          #  IP address because we have received complaints concerning mail coming from that IP
+          #  address. We recommend enrolling in our Junk Email Reporting Program (JMRP), a free
+          #  program intended to help senders remove unwanted recipients from their email list
+          "SC-004" => ["550", "blocked"],
+
+          #  Mail rejected by Outlook.com for policy reasons. We generally do not accept email
+          #  from dynamic IP's as they are not typically used to deliver unauthenticated SMTP email
+          #  to an Internet mail server. (Spamhaus)
+          "DY-001" => ["550", "blocked"],
+
+          #  Mail rejected by Outlook.com for policy reasons. The likely cause is a compromised or
+          #  virus infected server/personal computer.
+          "DY-002" => ["550", "virusdetected"],
+
+          #  Mail rejected by Outlook.com for policy reasons. If you are not an email/network admin
+          #  please contact your Email/Internet Service Provider for help. For more information
+          #  about this block and to request removal please go to: Spamhaus.
+          "OU-001" => ["550", "blocked"],
+
+          #  Mail rejected by Outlook.com for policy reasons. Reasons for rejection may be related
+          #  to content with spam-like characteristics or IP/domain reputation.
+          "OU-002" => ["550", "badreputation"],
+        }.freeze
 
         # Detect bounce reason from Exchange Server 2019 or older and Exchange Online
         # @param    [Sisimai::Fact] argvs   Decoded email object
@@ -735,12 +780,11 @@ module Sisimai
         # @since v4.17.2
         def find(argvs)
           return '' if argvs['deliverystatus'].empty?
-          return '' unless Sisimai::SMTP::Status.test(argvs['deliverystatus'])
+          return '' if Sisimai::SMTP::Status.test(argvs['deliverystatus']) == false
 
           statuscode = argvs['deliverystatus']
           issuedcode = argvs['diagnosticcode'].downcase
           thirddigit = statuscode.split('.')[-1].to_i
-          reasontext = ''
 
           MessagesOf.each_key do |e|
             # Each key is a reason name
@@ -748,22 +792,25 @@ module Sisimai
               # ["status-code", min, max, "error message"]
               if f[1] == f[2]
                 # This error code have no range
-                next unless statuscode == f[0]
+                next if statuscode != f[0]
               else
                 # This error code has a range
-                next unless statuscode.start_with?(f[0])
-                next if     thirddigit < f[1]
-                next if     thirddigit > f[2]
+                next if statuscode.start_with?(f[0]) == false
+                next if thirddigit < f[1] || thirddigit > f[2]
               end
 
-              next unless issuedcode.include?(f[3])
-              reasontext = e
-              break
+              return e if issuedcode.include?(f[3])
             end
-            break unless reasontext.empty?
           end
 
-          return reasontext
+          ErrorCodes.each_key do |e|
+            # The key name is an error code described at Outlook.com Postmaster/Troubleshooting
+            # https://substrate.office.com/ip-domain-management-snds/postmaster/troubleshooting
+            next if argvs['diagnosticcode'].include?(e) == false
+            return ErrorCodes[e][1] if argvs['replycode'] == ErrorCodes[e][0]
+          end
+
+          return ""
         end
 
       end

data/lib/sisimai/rhost/mimecast.rb

@@ -6,8 +6,8 @@ module Sisimai
     module Mimecast
       class << self
         MessagesOf = {
-          # https://community.mimecast.com/s/article/Mimecast-SMTP-Error-Codes-842605754
-          # https://community.mimecast.com/s/article/email-security-cloud-gateway-mimecast-smtp-error-codes
+          # - https://community.mimecast.com/s/article/email-security-cloud-gateway-mimecast-smtp-error-codes
+          # - https://mimecastsupport.zendesk.com/hc/en-us/articles/34000709564691-Policies-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.
@@ -46,6 +46,8 @@ module Sisimai
             [550, 'local ct ip reputation - (reject)'],
           ],
           'blocked' => [
+            # - Sender address blocked.
+            #   A Blocked Senders Policy has blocked the sender's IP address.
             # - The sender's IP address has been blocked by a Blocked Senders Policy.
             # - Remove the entry from the policy.
             [421, 'sender address blocked'],
@@ -67,6 +69,15 @@ module Sisimai
             #   the associated IP address from the RBL.
             #[550, '< details of RBL >'], NEED AN ACTUAL ERROR MESSAGE STRING
           ],
+          'emailtoolarge' => [
+            # - 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'],
+          ],
           'expired' => [
             # - Journal messages past the expiration
             # - Attempts are being made to journal mail past the set expiry threshold.
@@ -74,9 +85,17 @@ module Sisimai
             #   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 messages past the expiration'],
+            [550, 'journal messages past the expiration'],
           ],
           'failedstarttls' => [
+            # - SMTP inbound TLS has been enabled but no SSL certificate (or no valid certificate)
+            #   has been selected to be used. 
+            # - 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.
+            ["454", "tls not available due to temporary reason"],
+
             # - 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
@@ -102,15 +121,6 @@ module Sisimai
             # - Check you DNS has the required umbrella accounts listed as comma-separated values.
             [554, 'configuration is invalid for this certificate'],
           ],
-          '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 recipients' domains have MX records configured incorrectly
             # - Check and remove any MX records that point to hostnames with outbound references.
@@ -171,6 +181,31 @@ module Sisimai
             [554, 'host network not allowed'],
             [554, 'host network, not allowed'],
           ],
+          'ratelimited' => [
+            # - 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'],
+          ],
           'rejected' => [
             # - The sender's email address or domain has triggered a Blocked Senders Policy or
             #   there's an SPF hard rejection.
@@ -199,6 +234,19 @@ module Sisimai
             [550, 'submitter failed to disabled'],
             [550, 'submitter failed to authenticate'],
           ],
+          'spamdetected' => [
+            # - 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'],
+          ],
           'systemerror' => [
             # - The Mimecast server is under maximum load.
             # - No action is required from the end-user. The message will retry 30 times and when
@@ -222,31 +270,6 @@ module Sisimai
             # - 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.
@@ -264,27 +287,14 @@ module Sisimai
             # - 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   Decoded email object
         # @return   [String]                The bounce reason for mimecast.com
         def find(argvs)
-          return argvs['reason'] unless argvs['reason'].empty?
-          return '' unless Sisimai::SMTP::Reply.test(argvs['replycode'])
+          return argvs['reason'] if argvs['reason'].empty? == false
+          return '' if Sisimai::SMTP::Reply.test(argvs['replycode']) == false
 
           issuedcode = argvs['diagnosticcode'].downcase || ''
           esmtpreply = argvs['replycode'].to_i
@@ -294,12 +304,11 @@ module Sisimai
             # 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 issuedcode.include?(f[1])
+              next if esmtpreply != f[0] || issuedcode.include?(f[1]) == false
               reasontext = e
               break
             end
-            break unless reasontext.empty?
+            break if reasontext.empty? == false
           end
 
           return reasontext