view release on metacpan or  search on metacpan

lib/Sisimai/Rhost/Microsoft.pm  view on Meta::CPAN

            #   to RCPT TO command))
            ['4.7.500', 0, 0, 'server busy. please try again later from '],

            # - status=deferred (host apc.olc.protection.outlook.com[192.0.2.1] said:
            #   451 4.7.700 PFA agent busy, please try again. [***.***.prod.protection.outlook.com]
            #   (in reply to MAIL FROM command))
            ['4.7.700', 0, 0, 'pfa agent busy, please try again.'],
        ],
        'systemfull' => [
            # Exchange Server 2019 ----------------------------------------------------------------
            # - Free disk space is low (for example, the disk that holds the queue database doesn't
            #   have the required amount of free space). For more information, see Understanding
            #   back pressure. To move the queue database to a different disk, see Change the loca-
            #   tion of the queue database.
            # - Available memory is low (for example, Exchange installed on a virtual machine that
            #   is configured to use dynamic memory). Always use static memory on Exchange virtual
            #   machines.
            ['4.3.1', 0, 0, 'insufficient system resources'],
        ],
        'userunknown' => [
            # Exchange Server 2019 ----------------------------------------------------------------
            # - The recipient's email address is incorrect (the recipient doesn't exist in the des-
            #   tination messaging system). Verify the recipient's email address. You recreated a
            #   deleted mailbox, and internal users are addressing email messages in Outlook or
            #   Outlook on the web using old entries in their autocomplete cache (the X.500 values
            #   or LegacyExchangeDN values for the recipient are now different). Tell users to de-
            #   lete the entry from their autocomplete cache and select the recipient again.
            ['5.1.1', 0, 0, 'resolver.adr.exrecipnotfound; not found'],
            ['5.1.1', 0, 0, 'user unknown'],

            # - The recipient's email address is incorrect (for example, it contains unsupported
            #   characters or invalid formatting).
            ['5.1.3', 0, 0, 'storedrv.submit; invalid recipient address'],

            # - Receive connectors reject SMTP connections that contain the top level domains de-
            #   fined in RFC 2606 (.test, .example, .invalid, or .localhost), This behavior is con-
            #   trolled by the RejectReservedTopLevelRecipientDomains parameter on the New-Receive-
            #   Connector and Set-ReceiveConnector cmdlets.
            ['5.1.', 4, 5, 'recipient address reserved by rfc 2606'],

            # - Receive connectors reject SMTP connections that contain single label domains (for
            #   example, chris@contoso instead of chris@contoso.com) This behavior is controlled by
            #   the RejectSingleLabelRecipientDomains parameter on the New-ReceiveConnector and
            #   Set-ReceiveConnector cmdlets.
            ['5.1.6', 0, 0, 'recipient addresses in single label domains not accepted'],

            # Exchange Online ---------------------------------------------------------------------
            # - This failure might be caused by the following conditions:
            #   - The recipient's email address was entered incorrectly by the sender.
            #   - No recipient's exists in the destination email system.
            #   - The recipient's mailbox has been moved and the Outlook recipient cache on the
            #     sender's computer hasn't updated.
            #   - An invalid legacy domain name (DN) exists for the recipient's mailbox Active Di-
            #     rectory Domain Service.
            # - This error typically occurs when the sender of the message incorrectly enters the
            #   email address of the recipient. The sender should check the recipient's email ad-
            #   dress and send again. This error can also occur if the recipient email address was
            #   correct in the past but has changed or has been removed from the destination email
            #   system. If the sender of the message is in the same organization as the recipient,
            #   and the recipient's mailbox still exists, determine whether the recipient's mailbox
            #   has been relocated to a new email server. If this is the case, Outlook might not
            #   have updated the recipient cache correctly. Instruct the sender to remove the re-
            #   cipient's address from sender's Outlook recipient cache and then create a new mes-
            #   sage. Resending the original message will result in the same failure. 
            ['5.1.1', 0, 0, 'bad destination mailbox address'],

            # - The recipient's <SMTP Address> wasn't found by SMTP address lookup.
            ['5.1.10', 0, 0, 'recipient not found'],

            # - The recipient's address doesn't exist.
            ['5.4.1', 0, 0, 'recipient address rejected: access denied'],

            # - The recipient's <SMTP Address> domain is @hotmail.com or @outlook.com and it wasn't
            #   found by SMTP address lookup.
            # - Similar to 550 5.1.10.
            ['5.5.0', 0, 0, 'requested action not taken: mailbox unavailable'],

            # Previous versions of Exchange Server ------------------------------------------------
            ['5.1.2', 0, 0, 'invalid x.400 address'],

            # Imported from Sisimai::/Lhost::Office365
            ['5.1.351', 0, 0, 'remote server returned unknown recipient or mailbox unavailable'],
        ],
    };
    state $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