sisimai 5.4.1-java → 5.5.0-java

data/lib/sisimai/rhost/messagelabs.rb

@@ -6,8 +6,166 @@ module Sisimai
     module MessageLabs
       class << self
         MessagesOf = {
+          "authfailure" => [
+            # - 553 DMARC domain authentication fail
+            # - https://knowledge.broadcom.com/external/article/175407
+            #   An email has failed delivery and the reason provided in Track and Trace is due
+            #   to SPF Record. 553-SPF (Sender Policy Framework) domain authentication fail.
+            "domain authentication fail",
+          ],
+          "badreputation" => [
+            # - https://knowledge.broadcom.com/external/article/164955
+            #   "501 Connection rejected by policy [7.7]" 20805, please visit www.messagelabs.com/support
+            #   for more details about this error message.
+            #   My IP has a negative reputation with Symantec. To check the reputation of a
+            #   specific IP address, go to https://ipremoval.sms.symantec.com/.
+            # - https://knowledge.broadcom.com/external/article/384503
+            #   Users are receiving a non-delivery receipt (NDR) when sending an email to a
+            #   Symantec Email Security.cloud customer:
+            "Connection rejected by policy",
+          ],
+          "blocked" => [
+            # - https://knowledge.broadcom.com/external/article/165165
+            #   You are sending an email to a domain protected by the Symantec Email Security.Cloud
+            #   service and are receiving a non delivery receipt (NDR) stating the email delivery failed.
+            #   553-mail rejected because your IP is in the PBL. See http://www.spamhaus.org/pbl
+            # - Sorry, your IP address has been blocked
+            #   * This error message indicates that your public IP address has been put on a
+            #     block list by the Spamhaus PBL block list. To resolve this issue, request to
+            #     have your IP removed at http://www.spamhaus.org/pbl/.
+            #   * The delisting process is normally quicker than an hour. Once an hour has passed
+            #     try to resend your email.
+            #   * If the problem persists, contact the recipient by other means (e.g. phone)
+            #     and request that your email address is added to their Email Security.cloud
+            #     approved sender's list.
+            # - Sorry, your email address (addr) has been blocked
+            #   * Check with your administrator or ISP that your mail server is not in open relay.
+            #     Search “Open Relay Test” for an independent testing tool. If your mail server
+            #     is an open relay, please fix the open relay, wait 24 hours, and then try to
+            #     resend your email.
+            #   * Check with your administrator or ISP that your IP address is not on any spam
+            #     block lists. Search “email blacklist check” to check using an independent tool.
+            #     If your IP address is on any block lists, please request for removal, wait 24
+            #     hours, and then try to resend your email.
+            #     If the problem persists, contact the recipient by other means (e.g. phone) for
+            #     further assistance.
+            # - Sorry, your IP address (ip-addr) has been blocked
+            "mail rejected because your IP is in the PBL",
+            "your IP address has been ",
+            "your IP address (ip-addr) has been blocked",
+            "your email address (addr) has been blocked",
+          ],
+          "contenterror" => [
+            # - 553 Stray linefeeds in message (#5.6.2)
+            #   This error message happens because we strictly enforce the Internet Message Format
+            #   standard RFC 5322 (and its predecessor RFC 2822) which state, "CR and LF MUST
+            #   only occur together as CRLF; they MUST NOT appear independently in the body.
+            "Stray linefeeds in message",
+          ],
+          "failedstarttls" => [
+            # - https://knowledge.broadcom.com/external/article/162152
+            #   You are sending to a domain protected by the Symantec Email Security.cloud
+            #   service, or you are a customer subscribed to Symantec Email Security.cloud
+            #   sending outbound through the service. The Email Security.cloud server responds
+            #   to the SMTP RCPT TO: command with "451 TLS/SSLv3 Connection required. (#4.7.1)".
+            #   - 451 TLS/SSLv3 Connection required. (#4.7.1)
+            #   - Within the ClientNet portal, the Email Track and Trace tool shows "Not Delivered"
+            #     in the Delivered column and "Boundary Encryption" in the "Service" column.
+            "TLS/SSLv3 Connection required",
+          ],
+          "norelaying" => [
+            # - https://knowledge.broadcom.com/external/article/162137
+            #   You received a Non-Delivery Report (NDR) for email sent through the Symantec
+            #   Email Security.cloud infrastructure, with the message "You are trying to use
+            #   me [server-X.tower-x.messagelabs.com] as a relay, but I have not been configured
+            #   to let you [IP, address] do this."
+            " as a relay, ",
+          ],
+          "notcompliantrfc" => [
+            # - The format of your message did not comply with RFC 2822.
+            # - Contact your IT administrator or ISP.
+            # - If the problem persists, contact the recipient by other means (e.g. phone).
+            #
+            # - 550 [XX.XX.XX.XX] has detected that this message is not RFC 5322
+            #   * Ensure that the message complied to RFC 5322.
+            "550 Requested action aborted [4]",
+            "has detected that this message is not RFC 5322",
+          ],
+          "rejected" => [
+            #  - 550 sender envelope domain not allowed for sender IP address (#5.1.8)
+            #    This error occurs when a sender attempts to send an email and any one of the
+            #    following are true:
+            #    * The sending domain has not been registered under My Domains or Third-Party Domains.
+            #    * The sending domain is inactive.
+            #    * The sending IP is not in Outbound Routes.
+            #  - 553 Sorry, your domain has been blocked
+            #    The error message indicates that your IP address is on the recipient’s private
+            #    block list. Contact the recipient and request that your email address is added
+            #    to their Email Security.cloud approved sender's list.
+            #  - 553 Sorry, your email address has been blocked
+            #    The error message indicates that your domain is on the recipient’s private block
+            #    list. Contact the recipient by other means (e.g. phone) and request that your
+            #    email address is added to their Email Security.cloud approved senders list.
+            #  - https://knowledge.broadcom.com/external/article/162232
+            #    You have received an email notification from Symantec Email Security.cloud:
+            #    * An individual end user account is either sending spam through Symantec Email
+            #      Security.cloud or is receiving a bounceback error message indicating they are
+            #      on the "badmailfrom" list.
+            #    * The error message received is: "553 sorry, your envelope sender is in my
+            #      badmailfrom list. Please visit www.symanteccloud.com/troubleshooting for more
+            #      details about this error message and instructions to resolve this issue. (#5.7.1)."
+            #  - https://knowledge.broadcom.com/external/article/173082
+            #    Emails from a sender are blocked by the Anti-Spam service stating that they are
+            #    in your company's blacklist.
+            #    * 553-Sorry, your email address has been blacklisted
+            #    * 553-Sorry, your domain has been blacklisted
+            #    * 553-Sorry, your IP address has been blacklisted
+            "sender envelope domain not allowed for sender IP address",
+            "your domain has been blocked",
+            "your email address has been blocked",
+            "your envelope sender is in my badmailfrom list",
+            "your email address has been blacklisted",
+            "your domain has been blacklisted",
+          ],
           "securityerror" => ["Please turn on SMTP Authentication in your mail client"],
-          "userunknown"   => ["542 ", " Rejected", "No such user"],
+          "spamdetected" => [
+            #  - https://knowledge.broadcom.com/external/article/173867
+            #    Legitimate email, either outbound or inbound, is incorrectly flagged as spam
+            #    (false positive) by Email Security.cloud. This email may have the following errors:
+            #    * 553 - Message Filtered
+            #    * filtered by Outbound scanning.
+            "Message Filtered",
+            "filtered by Outbound scanning",
+          ],
+          "toomanyconn" => [
+            #  - https://knowledge.broadcom.com/external/article/385809
+            #    Email Security Cloud is attempting to deliver the email and recipient MTA is
+            #    responding "452 Too many recipients received this hour".
+            #  - https://knowledge.broadcom.com/external/article/164767
+            #    This error can occur when sending outbound or inbound emails through Email
+            #    Security.Cloud. A non-delivery receipt (NDR) stating delivery contains a message
+            #    that the intended recipient has failed with error:
+            #    "460 too many messages (#4.3.0)"
+            "Too many recipients received this hour",
+            "too many messages",
+          ],
+          "userunknown" => [
+            #  - https://knowledge.broadcom.com/external/article/165163
+            #    When sending email to a user on the Symantec Email Security.cloud service, the
+            #    message is rejected. The sender receives a non-delivery email with a 500 series
+            #    error code indicating that the recipient is invalid.
+            #    <username@example.com>: 550-Invalid recipient <username@example.com> 550 (#5.1.1)
+            #  - 553 Recipient mailbox is not allowed
+            #    The error message indicates that you have sent an email to an invalid address
+            #    in the recipient’s domain. Double-check the email address for any spelling errors.
+            #  - https://knowledge.broadcom.com/external/article/175710
+            #    This error indicates that you have sent an email to an invalid address to the
+            #    recipient’s domain. "Recipient mailbox is not allowed"
+            "No such user",
+            "Invalid recipient",
+            "mailbox is not allowed",
+            "Recipient mailbox is not allowed",
+          ],
         }.freeze
 
         # Detect bounce reason from Email Security (formerly MessageLabs.com)
@@ -22,7 +180,7 @@ module Sisimai
 
           MessagesOf.each_key do |e|
             # Try to match the error message with message patterns defined in $MessagesOf
-            next unless MessagesOf[e].any? { |a| issuedcode.include?(a) }
+            next if MessagesOf[e].none? { |a| issuedcode.include?(a) }
             reasontext = e
             break
           end

data/lib/sisimai/rhost/microsoft.rb

@@ -205,9 +205,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 +219,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 +233,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 ----------------------------------------------------------------
@@ -501,7 +501,7 @@ module Sisimai
             # - 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"],
+            ['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.
@@ -516,7 +516,7 @@ module Sisimai
             #   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"],
+            ['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.
@@ -524,7 +524,7 @@ module Sisimai
             #   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"],
+            ['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
@@ -536,8 +536,8 @@ module Sisimai
             # - 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'],
+            ['5.7.', 700, 749, 'tenant has exceeded threshold'],
+            ['5.7.', 700, 749, 'traffic not accepted from this ip'],
           ],
           'suspend' => [
             # Exchange Online ---------------------------------------------------------------------
@@ -595,7 +595,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'],
@@ -728,6 +728,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 +784,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 +796,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'],
@@ -74,9 +76,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
@@ -199,6 +209,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
@@ -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