Sisimai/Rhost/Microsoft.pm

filter: Statementstmt 97.0% 33 / 34 Branchbran 85.0% 17 / 20 Conditioncond 100% 2 / 2 MC/DCmcdc 100% 1 / 1 Subroutinesub 100% 5 / 5 Podpod 0.0% 0 / 1 totaltotal 92.0% 58 / 63 CC 15 SCAR 25.0
CC
15
Cov
93%
find
15.2
BEGIN
1.0
BEGIN
1.0
CRAP 12.2
« Sisimai/Lhost/OpenSMTPD.pm ↑ Summary Sisimai/Reason/Rejected.pm »
1 package Sisimai::Rhost::Microsoft;
2 10 ▶use v5.26;
Subroutine BEGIN: called CC=1 SCAR=0.0
3 10 ▶use strict;
Subroutine BEGIN: called CC=1 SCAR=0.0
4 10 ▶use warnings;
Subroutine BEGIN: called CC=1 SCAR=0.0
5 10 ▶use Sisimai::SMTP::Status;
Subroutine BEGIN: called CC=1 SCAR=0.0
6  
7 # https://technet.microsoft.com/en-us/library/bb232118
8 # https://learn.microsoft.com/en-us/Exchange/mail-flow-best-practices/non-delivery-reports-in-exchange-online/non-delivery-reports-in-exchange-online
9 # https://learn.microsoft.com/en-us/Exchange/mail-flow/non-delivery-reports-and-bounce-messages/non-delivery-reports-and-bounce-messages
10 122 ▶sub find {
Subroutine find: called CC=15 SCAR=27.2
Pod undocumented
11 # Detect bounce reason from Exchange Server 2019 or older and Exchange Online
12 # @param [Sisimai::Fact] argvs Decoded email object
13 # @return [String] The bounce reason for Exchange Online
14 # @see https://technet.microsoft.com/en-us/library/bb232118
15 # @since v4.17.2
16 122 my $class = shift;
17 122 ▶ my $argvs = shift // return "";
Condition100%2/2
shift() // (return "")
l!l
1211
MC/DC100%1/1
shift() // (return "")
shift()
Truth table100%2/2
A
A= shift()
Aresult
11
00
18 121 ▶ return '' unless $argvs->{'deliverystatus'};
Branch: 1 branch
BranchTrueFalseTotal
unless $argvs->{"deliverystatus"} 2 119 121
19 119 ▶ return '' unless Sisimai::SMTP::Status->test($argvs->{'deliverystatus'});
Branch: 1 branch
BranchTrueFalseTotal
unless "Sisimai::SMTP::Status"->test($argvs->{"deliverystatus"}) 1 118 119
20  
21 118 require Sisimai::Eb;
22 118 state $messagesof = {
23 $Sisimai::Eb::ReAUTH => [
24 # - Access denied, a message sent over IPv6 [2a01:111:f200:2004::240] must pass either
25 # SPF or DKIM validation, this message is not signed
26 # - The sending message sent over IPv6 must pass either SPF or DKIM.
27 ['4.7.26', 0, 0, 'must pass either spf or dkim validation, this message is not signed'],
28  
29 # - The destination email system uses SPF to validate inbound mail, and there's a prob-
30 # lem with your SPF configuration.
31 ['5.7.23', 0, 0, 'the message was rejected because of sender policy framework violation'],
32  
33 # - Access denied, sending domain [$SenderDomain] does not pass DMARC verification
34 # - The sender's domain in the 5322.From address doesn't pass DMARC.
35 ['5.7.509', 0, 0, 'does not pass dmarc verification'],
36  
37 # - 550 5.7.515 Access denied, sending domain EXAMPLE.JP doesn't meet the required
38 # authentication level. The sender's domain in the 5322.From address doesn't meet
39 # the authentication requirements defined for the sender. To learn how to fix this
40 # see: https://go.microsoft.com/fwlink/p/?linkid=2319303
41 # Spf= Fail , Dkim= Pass , DMARC= Pass ...
42 ["5.7.515", 0, 0, "doesn't meet the required authentication level"],
43 ],
44 $Sisimai::Eb::ReFAMA => [
45 # Undocumented error messages ---------------------------------------------------------
46 # - status=deferred (host outlook-com.olc.protection.outlook.com[192.0.2.255] said:
47 # 451 4.7.650 The mail server [192.0.2.5] has been temporarily rate limited due to IP
48 # reputation. For e-mail delivery information, see https://postmaster.live.com (S775)
49 # [***.prod.protection.outlook.com] (in reply to MAIL FROM command))
50 ['4.7.650', 0, 0, 'has been temporarily rate limited due to ip reputation'],
51 ],
52 $Sisimai::Eb::ReBLOC => [
53 # Exchange Server 2019 ----------------------------------------------------------------
54 # - Transient network issues or server problems that might eventually correct them-
55 # selves. The sending server will retry delivery of the message, and will generate
56 # further status reports. The message size limit for the connection has been reached,
57 # or the message submission rate for the source IP address has exceeded the configur-
58 # ed limit. For more information, see Message rate limits and throttling. Antispam,
59 # SMTP proxy, or firewall configuration issues are blocking email from the Exchange
60 # server.
61 ['4.4.2', 0, 0, 'connection dropped'],
62  
63 # Exchange Online ---------------------------------------------------------------------
64 # - Suspicious activity has been detected on the IP in question, and it has been tempo-
65 # rarily restricted while it's being further evaluated.
66 # - If this activity is valid, this restriction will be lifted shortly.
67 ['4.7.', 850, 899, 'access denied, please try again later'],
68  
69 # - Access denied, the sending IPv6 address [2a01:111:f200:2004::240] must have a re-
70 # verse DNS record
71 # - The sending IPv6 address must have a reverse DNS record in order to send email over
72 # IPv6.
73 ['5.7.25', 0, 0, 'must have a reverse dns record'],
74  
75 # - Your server is attempting to introduce itself (HELO according to RFC 821) as the
76 # server it's trying to connect to, rather than its own fully qualified domain name.
77 # - This isn't allowed, and it's characteristic of typical spambot behavior.
78 ['5.7.506', 0, 0, 'access denied, bad helo'],
79  
80 # - The IP that you're attempting to send from has been blocked by the recipient's or-
81 # ganization.
82 # - Contact the recipient in order to resolve this issue.
83 ['5.7.507', 0, 0, 'access denied, rejected by recipient'],
84  
85 # - Access denied, [contoso.com] does not accept email over IPv6
86 # - The sender is attempting to transmit a message to the recipient over IPv6, but the
87 # recipient doesn't accept email messages over IPv6.
88 ['5.7.510', 0, 0, 'does not accept email over ipv6'],
89  
90 # - The IP that you're attempting to send from has been banned.
91 # - To delist the address, email delist@messaging.microsoft.com and provide the full
92 # NDR code and IP address to delist. For more information, see Use the delist portal
93 # to remove yourself from the blocked senders list.
94 ['5.7.511', 0, 0, 'access denied, banned sender'],
95  
96 # - Service unavailable, Client host [$ConnectingIP] blocked by $recipientDomain using
97 # Customer Block list (AS16012607)
98 # - The recipient domain has added your sending IP address to its custom blocklist.
99 # - The domain that received the email has blocked your sender's IP address. If you
100 # think your IP address has been added to the recipient domain's custom blocklist in
101 # error, you need to contact them directly and ask them to remove it from the block-
102 # list.
103 ['5.7.513', 0, 0, 'using customer block list'],
104  
105 # - 5.7.606-649 Access denied, banned sending IP [IP1.IP2.IP3.IP4]
106 # - The IP that you're attempting to send from has been banned.
107 # - Verify that you're following the best practices for email deliverability, and en-
108 # sure your IPs' reputations haven't been degraded as a result of compromise or mali-
109 # cious traffic. If you believe you're receiving this message in error, you can use
110 # the self-service portal to request to be removed from this list.
111 # - For more information, see Use the delist portal to remove yourself from the blocked
112 # senders list.
113 ['5.7.', 606, 649, 'access denied, banned sending ip '],
114  
115 # Previous versions of Exchange Server ------------------------------------------------
116 # - Suspicious activity has been detected and sending has been temporarily restricted
117 # for further evaluation.
118 # - If this activity is valid, this restriction will be lifted shortly.
119 ['4.7.', 500, 699, 'access denied, please try again later'],
120  
121 # Previous versions of Exchange Server ------------------------------------------------
122 ['5.5.4', 0, 0, 'invalid domain name'],
123  
124 # Undocumented error messages ---------------------------------------------------------
125 # - 550 5.7.1 Unfortunately, messages from [10.0.2.5] weren't sent. Please contact your
126 # Internet service provider since part of their network is on our block list (S3150).
127 ['5.7.1', 0, 0, 'part of their network is on our block list (s3150)'],
128 ],
129 $Sisimai::Eb::ReBODY => [
130 # Exchange Server 2019 ----------------------------------------------------------------
131 # - The message was determined to be malformed, and was moved to the poison message
132 # queue. For more information, see Types of queues.
133 ['5.3.0', 0, 0, 'too many related errors'],
134  
135 # Exchange Online ---------------------------------------------------------------------
136 # - Your email program added invalid characters (bare line feed characters) into a mes-
137 # sage you sent.
138 ['5.6.11', 0, 0, 'invalid characters'],
139  
140 # Previous versions of Exchange Server ------------------------------------------------
141 ['5.4.11', 0, 0, 'agent generated message depth exceeded'],
142 ['5.5.6', 0, 0, 'invalid message content'],
143 ],
144 $Sisimai::Eb::ReSIZE => [
145 # Exchange Server 2019 ----------------------------------------------------------------
146 # - The message is too large. Send the message again without any attachments, or confi-
147 # gure a larger message size limit for the recipient. For more information, see Re-
148 # cipient limits.
149 ['5.2.3', 0, 0, 'resolver.rst.recipsizelimit; message too large for this recipient'],
150  
151 # - The message is too large. This error can be generated by the source or destination
152 # messaging system. Send the message again without any attachments, or configure a
153 # larger message size limit. For more information, see Message size and recipient
154 # limits in Exchange Server.
155 ['5.3.4', 0, 0, 'message size exceeds fixed maximum message size'],
156  
157 # Previous versions of Exchange Server ------------------------------------------------
158 ['5.3.4', 0, 0, 'message too big for system'],
159 ],
160 $Sisimai::Eb::ReTIME => [
161 # Exchange Server 2019 ----------------------------------------------------------------
162 # - Transient network issues that might eventually correct themselves. The Exchange
163 # server periodically tries to connect to the destination server to deliver the mes-
164 # sage. After multiple failures, the message is returned to the sender in an NDR with
165 # a permanent failure code.
166 # For more information about configuring the queue retry and failure intervals, see
167 # Configure message retry, resubmit, and expiration intervals. To manually retry a
168 # queue, see Retry queues. Firewall or Internet service provider (ISP) restrictions
169 # on TCP port 25.
170 ['4.4.1', 0, 0, 'connection timed out'],
171  
172 # - Send connector configuration issues. For example:
173 # - The Send connector is configured to use DNS routing when it should be using smart
174 # host routing, or vice-versa. Use nslookup to verify that the destination domain
175 # is reachable from the Exchange server.
176 # - The FQDN that the Send connector provides to HELO or EHLO requests doesn't match
177 # the host name in your MX record (for example, mail.contoso.com). Some messaging
178 # systems are configured to compare these values in an effort to reduce spam. The
179 # default value on a Send connector is blank, which means the FQDN of the Exchange
180 # server is used (for example, exchange01.contoso.com).
181 # - The Mailbox Transport Delivery service isn't started on the destination server
182 # (which prevents the delivery of the message to the mailbox).
183 # - The destination messaging system has issues with Transport Neutral Encryption For-
184 # mat (TNEF) messages (also known as rich text format or RTF in Outlook). For exam-
185 # ple, meeting requests or messages with images embedded in the message body.
186 # - If the destination domain uses the Sender Policy Framework (SPF) to check message
187 # sources, there may be SPF issues with your domain (for example, your SPF record
188 # doesn't include all email sources for your domain).
189 ['4.4.7', 0, 0, 'message delayed'],
190 ['4.4.7', 0, 0, 'queue expired; message expired'],
191  
192 # Exchange Online ---------------------------------------------------------------------
193 # - The message in the queue has expired. The sending server tried to relay or deliver
194 # the message, but the action wasn't completed before the message expiration time oc-
195 # curred. This message can also indicate that a message header limit has been reached
196 # on a remote server, or some other protocol time-out occurred while communicating
197 # with the remote server.
198 # - This message usually indicates an issue on the receiving server. Check the validity
199 # of the recipient address, and determine if the receiving server is configured cor-
200 # rectly to receive messages. You might have to reduce the number of recipients in
201 # the message header for the host about which you're receiving this error. If you
202 # send the message again, it's placed in the queue again. If the receiving server is
203 # available, the message is delivered.
204 ['4.4.7', 0, 0, 'message expired'],
205  
206 # - The email took too long to be successfully delivered, either because the destina-
207 # tion server never responded or the sent message generated an NDR error and that NDR
208 # couldn't be delivered to the original sender.
209 ['5.4.300', 0, 0, 'message expired'],
210 ],
211 $Sisimai::Eb::ReTTLS => [
212 # Exchange Online ---------------------------------------------------------------------
213 # - MX hosts of <domain> failed MTA-STS validation The destination MX host is not the
214 # expected host per the domain's STS policy
215 ["4.4.8", 0, 0, " failed mta-sts validation"],
216 ["5.4.8", 0, 0, " failed mta-sts validation"],
217  
218 # - DNSSEC checks have passed, yet upon connection, destination mail server doesn't re-
219 # spond to the STARTTLS command. The destination server responds to the STARTTLS com-
220 # mand, but the TLS handshake fails.
221 # - This message usually indicates an issue on the destination email server. Check the
222 # validity of the recipient address. Determine if the destination server is configur-
223 # ed correctly to receive the messages.
224 ['4.4.317', 0, 0, 'starttls is required to send mail'],
225 ['5.4.317', 0, 0, 'starttls is required to send mail'],
226  
227 # - Remote certificate failed MTA-STS validation. Reason: <validityStatus> The destina-
228 # tion mail server's certificate must chain to a trusted root Certificate Authority
229 # and the Common Name or Subject Alternative Name must contain an entry for the host
230 # name in the STS policy.
231 ["4.7.5", 0, 0, "remote certificate failed mta-sts validation"],
232 ["5.7.5", 0, 0, "remote certificate failed mta-sts validation"],
233  
234 # - DNSSEC checks have passed, yet upon establishing the connection the destination
235 # mail server provides a certificate that is expired.
236 # - A valid X.509 certificate that isn't expired must be presented. X.509 certificates
237 # must be renewed after their expiration, commonly annually.
238 ['5.7.51', 0, 0, 'restrictdomainstoipaddresses or restrictdomainstocertificate'],
239 ['4.7.321', 0, 0, 'starttls-not-supported:'],
240 ['5.7.321', 0, 0, 'starttls-not-supported:'],
241 ['5.7.322', 0, 0, "certificate-expired:"],
242  
243 # - Records are DNSSEC authentic, but one or multiple of these scenarios occurred:
244 # - The destination mail server's certificate doesn't match with what is expected per
245 # the authentic TLSA record.
246 # - Authentic TLSA record is misconfigured.
247 # - Destination domain is being attacked.
248 # - Any other DANE failure.
249 # - This message usually indicates an issue on the destination email server. Check the
250 # validity of recipient address and determine if the destination server is configured
251 # correctly to receive messages.
252 # - For more information about DANE, see: https://datatracker.ietf.org/doc/html/rfc7671
253 ['4.7.323', 0, 0, 'tlsa-invalid:'],
254 ['5.7.323', 0, 0, 'tlsa-invalid:'],
255  
256 # - The destination domain indicated it was DNSSEC-authentic, but Exchange Online was
257 # not able to verify it as DNSSEC-authentic.
258 ['4.7.324', 0, 0, 'dnssec-invalid:'],
259 ['5.7.324', 0, 0, 'dnssec-invalid:'],
260  
261 # - This happens when the presented certificate identities (CN and SAN) of a destina-
262 # tion SMTP target host don't match any of the domains or MX host.
263 # - This message usually indicates an issue on the destination email server. Check the
264 # validity of recipient address and determine if the destination server is configured
265 # correctly to receive messages. For more information, see How SMTP DNS-based Authen-
266 # tication of Named Entities (DANE) works to secure email communications.
267 ['4.7.325', 0, 0, 'certificate-host-mismatch:'],
268 ['5.7.325', 0, 0, 'certificate-host-mismatch:'],
269 ],
270 $Sisimai::Eb::ReFULL => [
271 # Exchange Server 2019 ----------------------------------------------------------------
272 # - The recipient's mailbox has exceeded its storage quota and is no longer able to ac-
273 # cept new messages. For more information about configuring mailbox quotas, see Con-
274 # figure storage quotas for a mailbox.
275 ['5.2.2', 0, 0, 'mailbox full'],
276 ],
277 $Sisimai::Eb::ReINET => [
278 # Exchange Server 2019 ----------------------------------------------------------------
279 # - There's a DNS or network adapter configuration issue on the Exchange server. Verify
280 # the internal and external DNS lookup settings for the Exchange by running this com-
281 # mand in the Exchange Management Shell:
282 # - Get-TransportService | Format-List Name,ExternalDNS*,InternalDNS*;
283 # - Get-FrontEndTransportService | Format-List Name,ExternalDNS*,InternalDNS*`
284 # You can configure these settings by using the InternalDNS* and ExternalDNS* parame-
285 # ters on the Set-TransportService and Set-FrontEndTransportService cmdlets.
286 # By default, these settings are used by Send connectors (the default value of the
287 # UseExternalDNSServersEnabled parameter value is $false). Check the priority (order)
288 # of the network adapters in the operating system of the Exchange server.
289 ['5.4.4', 0, 0, 'smtpsend.dns.nonexistentdomain; nonexistent domain'],
290  
291 # - A configuration error has caused an email loop. By default, after 20 iterations of
292 # an email loop, Exchange interrupts the loop and generates an NDR. Verify that Inbox
293 # rules for the recipient and sender, or forwarding rules on the recipient's mailbox
294 # aren't causing this (the message generates a message, which generates another mes-
295 # sage, and the process continues indefinitely).
296 # Verify the mailbox doesn't have a targetAddress property value in Active Directory
297 # (this property corresponds to the ExternalEmailAddress parameter for mail users in
298 # Exchange). If you remove Exchange servers, or modify settings related to mail rout-
299 # ing an mail flow, be sure to restart the Microsoft Exchange Transport and Exchange
300 # Frontend Transport services.
301 ['5.4.6', 0, 0, 'hop count exceeded - possible mail loop'],
302  
303 # Exchange Online ---------------------------------------------------------------------
304 # - Microsoft 365 or Office 365 is trying to send a message to an email server outside
305 # of Microsoft 365 or Office 365, but attempts to connect to it are failing due to a
306 # network connection issue at the external server's location.
307 # - This error almost always indicates an issue with the receiving server or network
308 # outside of Microsoft 365 or Office 365. The error should also include the IP ad-
309 # dress of the server or service that's generating the error, which you can use to
310 # identify the party responsible for fixing this.
311 ['4.4.316', 0, 0, 'connection refused'], # [Message=Socket error code 10061]
312 ['5.4.316', 0, 0, 'connection refused'], # [Message=Socket error code 10061]
313  
314 # - A configuration error has caused an email loop. 5.4.6 is generated by on-premises
315 # Exchange server (you'll see this code in hybrid environments). 5.4.14 is generated
316 # by Exchange Online. By default, after 20 iterations of an email loop, Exchange in-
317 # terrupts the loop and generates an NDR to the sender of the message.
318 # - This error occurs when the delivery of a message generates another message in re-
319 # sponse. That message then generates a third message, and the process is repeated,
320 # creating a loop. To help protect against exhausting system resources, Exchange in-
321 # terrupts the mail loop after 20 iterations. Mail loops are typically created be-
322 # cause of a configuration error on the sending mail server, the receiving mail serv-
323 # er, or both. Check the sender's and the recipient's mailbox rules configuration to
324 # determine whether automatic message forwarding is enabled.
325 ['5.4.4', 0, 0, 'invalid arguments'],
326 ['5.4.6', 0, 0, 'routing loop detected'],
327 ['5.4.14', 0, 0, 'routing loop detected'],
328  
329 # Imported from Sisimai::Lhost::Office365
330 ['4.4.312', 0, 0, 'dns query failed'], # [Message=InfoNoRecords]
331 ['5.4.312', 0, 0, 'dns query failed'], # [Message=InfoNoRecords]
332 ],
333 $Sisimai::Eb::RePASS => [
334 # Exchange Server 2019 ----------------------------------------------------------------
335 # - You have an application server or device that's trying to relay messages through
336 # Exchange. For more information, see Allow anonymous relay on Exchange servers. The
337 # recipient is configured to only accept messages from authenticated (typically, in-
338 # ternal) senders. For more information, see Configure message delivery restrictions
339 # for a mailbox.
340 ['5.7.1', 0, 0, 'unable to relay'],
341 ['5.7.1', 0, 0, 'client was not authenticated'],
342  
343 # Exchange Online ---------------------------------------------------------------------
344 # - The mail server that's generating the error doesn't accept mail for the recipient's
345 # domain. This error is caused by mail server or DNS misconfiguration.
346 ['5.4.1', 0, 0, 'relay access denied'],
347  
348 # - The sending email system isn't allowed to send a message to an email system where
349 # that email system isn't the final destination of the message.
350 # - This error occurs when the sending email system tries to send an anonymous message
351 # to a receiving email system, and the receiving email system doesn't accept messages
352 # for the domain or domains specified in one or more of the recipients. The following
353 # are the most common reasons for this error:
354 # - A third party tries to use a receiving email system to send spam, and the receiv-
355 # ing email system rejects the attempt. By the nature of spam, the sender's email
356 # address might have been forged, and the resulting NDR could have been sent to the
357 # unsuspecting sender's email address. It's difficult to avoid this situation.
358 # - An MX record for a domain points to a receiving email system where that domain is
359 # not accepted. The administrator responsible for the specific domain name must
360 # correct the MX record or configure the receiving email system to accept messages
361 # sent to that domain, or both.
362 # - A sending email system or client that should use the receiving email system to
363 # relay messages doesn't have the correct permissions to do this.
364 ['5.7.1', 0, 0, 'unable to relay'],
365  
366 # - You use an inbound connector to receive messages from your on-premises email envi-
367 # ronment, and something has changed in your on-premises environment that makes the
368 # inbound connector's configuration incorrect.
369 ['5.7.64', 0, 0, 'tenantattribution; relay access denied'],
370  
371 # Previous versions of Exchange Server ------------------------------------------------
372 ['5.4.310', 0, 0, 'does not exist'], # DNS domain * does not exist
373 ],
374 $Sisimai::Eb::Re00MX => [
375 ['4.3.2', 0, 0, 'system not accepting network messages'],
376 ['4.4.4', 0, 0, 'hosted tenant which has no mail-enabled subscriptions'],
377  
378 # Exchange Server 2019 ----------------------------------------------------------------
379 # - You're using the ABP Routing agent, and the recipient isn't a member of the global
380 # address list that's specified in their address book policy (ABP). For more infor-
381 # mation, see Use the Exchange Management Shell to install and configure the Address
382 # Book Policy Routing Agent and Address book policies in Exchange Server.
383 ['5.3.2', 0, 0, 'storedrv.deliver: missing or bad storedriver mdb properties'],
384 ],
385 $Sisimai::Eb::ReWONT => [
386 # - 5.0.350 is a generic catch-all error code for a wide variety of non-specific errors
387 # lfrom the recipient's email organization. The specific x-dg-ref header is too long
388 # message is related to Rich Text formatted messages. The specific Requested action
389 # not taken: policy violation detected (AS345) message is related to nested attach-
390 # ments.
391 ['5.0.350', 0, 0, 'x-dg-ref header is too long'],
392 ['5.0.350', 0, 0, 'requested action not taken: policy violation detected (as345)'],
393  
394 # - The message was rejected by a mail flow rule (also known as a transport rule). This
395 # enhanced status code range is available when the rule is configured to reject mes-
396 # sages (otherwise, the default code that's used is 5.7.1). For more information, see
397 # Mail flow rule actions in Exchange Server.
398 ['5.7.', 900, 999, 'delivery not authorized, message refused'],
399 ],
400 $Sisimai::Eb::ReRATE => [
401 # Exchange Server 2019 ----------------------------------------------------------------
402 # - The combined total of recipients on the To, Cc, and Bcc lines of the message ex-
403 # ceeds the total number of recipients allowed in a single message for the organiza-
404 # tion, Receive connector, or sender. For more information, see Message size and re-
405 # cipient limits in Exchange Server.
406 ['5.5.3', 0, 0, 'too many recipients'],
407
408 # Exchange Online ---------------------------------------------------------------------
409 # - The recipient mailbox's ability to accept messages is being throttled because it's
410 # receiving too many messages too quickly. This is done so a single recipient's mail
411 # processing doesn't unfairly impact other recipients sharing the same mailbox data-
412 # base.
413 ['4.3.2', 0, 0, 'storedrv.deliver; recipient thread limit exceeded'],
414  
415 # - The message has more than 200 SMTP envelope recipients from the same domain.
416 # - An envelope recipient is the original, unexpanded recipient that's used in the RCPT
417 # TO command to transmit the message between SMTP servers. When this error is return-
418 # ed by Microsoft 365 or Office 365, the sending server must break up the number of
419 # envelope recipients into smaller chunks (chunking) and resend the message.
420 ['4.5.3', 0, 0, 'too many recipients'],
421  
422 # - The sender has exceeded the recipient rate limit as described in Sending limits.
423 # - This could indicate the account has been compromised and is being used to send
424 # spam.
425 ['5.1.90', 0, 0, "reached your daily limit for message recipients"],
426  
427 # - The sender has exceeded the recipient rate limit or the message rate limit as de-
428 # scribed in Sending limits.
429 # - This could indicate the account has been compromised and is being used to send
430 # spam.
431 ['5.2.2', 0, 0, 'submission quota exceeded'],
432  
433 # - The sender has exceeded the maximum number of messages they're allowed to send per
434 # hour to a specific recipient in Exchange Online.
435 # - The automated mailer or sender should try again later, and reduce the number of
436 # messages they send per hour to a specific recipient. This limit helps protect
437 # Microsoft 365 or Office 365 users from rapidly filling their inboxes with a large
438 # number of messages from errant automated notification systems or other single-send-
439 # er mail storms.
440 ['5.2.121', 0, 0, "recipient's per hour message receive limit"],
441  
442 # - The Microsoft 365 or Office 365 recipient has exceeded the number of messages they
443 # can receive per hour from all senders.
444 # - The automated mailer or sender should try again later, and reduce the number of
445 # messages they send per hour to a specific recipient. This limit helps protect
446 # Microsoft 365 and Office 365 users from rapidly filling their inboxes with a large
447 # number of messages from errant automated notification systems or other mail storms.
448 ['5.2.122', 0, 0, "recipient's per hour message receive limit"],
449  
450 # - Access denied, [$SenderIPAddress] has exceeded permitted limits within $range range
451 # - The sender's IPv6 range has attempted to send too many messages in too short a time
452 # period.
453 ['5.7.508', 0, 0, 'has exceeded permitted limits within'],
454  
455 # - The majority of traffic from this tenant has been detected as suspicious and has
456 # resulted in a ban on sending ability for the tenant.
457 # - Ensure that any compromises or open relays have been resolved, and then contact
458 # support through your regular channel. For more information, see Fix email delivery
459 # issues for error codes 5.7.700 through 5.7.750 in Exchange Online.
460 ['5.7.', 700, 749, 'tenant has exceeded threshold'],
461 ['5.7.', 700, 749, 'traffic not accepted from this ip'],
462  
463 # - 451 4.7.652 The mail server [192.0.2.251] has exceeded the maximum number of
464 # connections. (S3115) [Name=Protocol Filter Agent][AGT=PFA][MxId=11BA9B3FA168ABBF]
465 # [BN3PEPF0000B370.namprd21.prod.outlook.com 2025-02-20T14:30:32.425Z 08DD4D9FD5AFF45C]
466 # (in reply to MAIL FROM command))
467 ["4.7.652", 0, 0, "has exceeded the maximum number of connections"],
468  
469 # Previous versions of Exchange Server ------------------------------------------------
470 ['5.2.122', 0, 0, 'the recipient has exceeded their limit for'],
471 ],
472 $Sisimai::Eb::ReFROM => [
473 # Exchange Server 2019 ----------------------------------------------------------------
474 # - There's a problem with the sender's email address. Verify the sender's email ad-
475 # dress.
476 ['5.1.7', 0, 0, 'invalid address'],
477 ['5.1.7', 0, 0, 'unknown sender address'],
478  
479 # - A common cause of this NDR is when you use Microsoft Outlook to save an email mes-
480 # sage as a file, and then someone opened the message offline and replied to it. The
481 # message property only preserves the legacyExchangeDN attribute when Outlook deliv-
482 # ers the message, and therefore the lookup could fail.
483 # - Either the recipient address is incorrectly formatted, or the recipient couldn't be
484 # correctly resolved. The first step in resolving this error is to check the recipi-
485 # ent address, and send the message again.
486 ['5.1.0', 0, 0, 'sender denied'],
487  
488 # - The account has been blocked for sending too much spam. Typically, this problem oc-
489 # curs because the account has been compromised (hacked) by phishing or malware.
490 ['5.1.8', 0, 0, 'access denied, bad outbound sender'],
491  
492 # Exchange Online ---------------------------------------------------------------------
493 # - The sender of the message isn't allowed to send messages to the recipient.
494 # - This error occurs when the sender tries to send a message to a recipient but the
495 # sender isn't authorized to do this. This frequently occurs when a sender tries to
496 # send messages to a distribution group that has been configured to accept messages
497 # only from members of that distribution group or other authorized senders. The send-
498 # er must request permission to send messages to the recipient. This error can also
499 # occur if an Exchange transport rule rejects a message because the message matched
500 # conditions that are configured on the transport rule.
501 ['5.7.1', 0, 0, 'delivery not authorized'],
502  
503 # - The sender's message is rejected because the recipient address is set up to reject
504 # messages sent from outside of its organization. Only an email admin for the recipi-
505 # ent's organization can change this.
506 ['5.7.12', 0, 0, 'sender was not authenticated by organization'],
507  
508 # - The sender doesn't have permission to send to the distribution group because the
509 # sender isn't in the group's allowed-senders list. Depending how the group is set
510 # up, even the group's owner might need to be added to the allowed sender list in or-
511 # der to send messages to the group.
512 ['5.7.124', 0, 0, 'sender not in allowed-senders list'],
513  
514 # - The recipient address is a group distribution list that is set up to reject mes-
515 # sages sent from outside of its organization. Only an email admin for the recipi-
516 # ent's organization or the group owner can change this.
517 ['5.7.133', 0, 0, 'sender not authenticated for group'],
518  
519 # - The recipient address is a mailbox that is set up to reject messages sent from out-
520 # side of its organization. Only an email admin for the recipient's organization can
521 # change this.
522 ['5.7.134', 0, 0, 'sender was not authenticated for mailbox'],
523  
524 # - The recipient address is a public folder that is set up to reject messages sent
525 # from outside of its organization. Only an email admin for the recipient's organiza-
526 # tion can change this.
527 ['5.7.13', 0, 0, 'sender was not authenticated for public folder'],
528 ['5.7.135', 0, 0, 'sender was not authenticated for public folder'],
529  
530 # - The recipient address is a mail user that is set up to reject messages sent from
531 # outside of its organization. Only an email admin for the recipient's organization
532 # can change this.
533 ['5.7.136', 0, 0, 'sender was not authenticated'],
534  
535 # - 550 5.7.193 UnifiedGroupAgent; Delivery failed because the sender isn't a group
536 # member or external senders aren't permitted to send to this group.
537 ["5.7.193", 0, 0, "sender isn't a group member or external senders aren't permitted"],
538  
539 # - The sending account has been banned due to detected spam activity.
540 # - For details, see Fix email delivery issues for error code 451 5.7.500-699 (ASxxx)
541 # in Exchange Online.
542 # - Verify that any account issues have been resolved, and reset its credentials. To
543 # restore this account's ability to send mail, contact support through your regular
544 # channel.
545 ['5.7.', 501, 503, 'access denied, spam abuse detected'],
546  
547 # - Message was sent without a valid "From" email address.
548 # - Office 365 only. Each message must contain a valid email address in the "From"
549 # header field. Proper formatting of this address includes angle brackets around the
550 # email address, for example, <security@contoso.com>. Without this address Microsoft
551 # 365 or Office 365 will reject the message.
552 ['5.7.512', 0, 0, 'access denied, message must be rfc 5322 section 3.6.2 compliant'],
553  
554 # - A suspicious number of messages from unprovisioned domains is coming from this ten-
555 # ant.
556 # - Add and validate any and all domains that you use to send email from Microsoft 365
557 # or Office 365. For more information, see Fix email delivery issues for error codes
558 # 5.7.700 through 5.7.750 in Exchange Online.
559 ['5.7.750', 0, 0, 'service unavailable. client blocked from sending from unregistered domains'],
560  
561 # Previous versions of Exchange Server ------------------------------------------------
562 ['5.7.', 501, 503, 'access denied, banned sender'],
563 ],
564 $Sisimai::Eb::ReSAFE => [
565 # Exchange Server 2019 ----------------------------------------------------------------
566 # - A firewall or other device is blocking the Extended SMTP command that's required
567 # for Exchange Server authentication (X-EXPS). Internal email traffic is flowing
568 # through connectors that aren't configured to use the Exchange Server authentication
569 # method . Verify the remote IP address ranges on any custom Receive connectors.
570 ['5.7.3', 0, 0, 'cannot achieve exchange server authentication'],
571 ['5.7.3', 0, 0, 'not authorized'],
572  
573 # - The sending email system didn't authenticate with the receiving email system. The
574 # receiving email system requires authentication before message submission.
575 # - This error occurs when the receiving server must be authenticated before message
576 # submission, and the sending email system hasn't authenticated with the receiving e-
577 # mail system. The sending email system administrator must configure the sending e-
578 # mail system to authenticate with the receiving email system for delivery to be suc-
579 # cessful.
580 ['5.7.1', 0, 0, 'client was not authenticated'],
581  
582 # - You configured an application or device to send (relay) email messages in Microsoft
583 # 365 or Office 365 using the smtp.office365.com endpoint, and there's a problem with
584 # the configuration of the application or device.
585 ['5.7.57', 0, 0, 'client was not authenticated to send anonymous mail during mail from'],
586 ],
587 $Sisimai::Eb::ReSPAM => [
588 # Exchange Server 2019 ----------------------------------------------------------------
589 # - The message was quarantined by content filtering. To configure exceptions to con-
590 # tent filtering, see Use the Exchange Management Shell to configure recipient and
591 # sender exceptions for content filtering.
592 ['5.2.1', 0, 0, 'content filter agent quarantined this message'],
593 ],
594 $Sisimai::Eb::ReQUIT => [
595 # Exchange Online ---------------------------------------------------------------------
596 # - The recipient address that you're attempting to contact isn't valid.
597 # - Verify the recipient's email address, and try again.
598 # - If you feel this is in error, contact support.
599 ['5.7.504', 0, 0, 'recipient address rejected: access denied'],
600 ['5.7.505', 0, 0, 'access denied, banned recipient'],
601  
602 # Previous versions of Exchange Server ------------------------------------------------
603 ['5.2.1', 0, 0, 'mailbox cannot be accessed'],
604 ],
605 $Sisimai::Eb::ReCOMM => [
606 # Exchange Server 2019 ----------------------------------------------------------------
607 # - Receive connectors that are used for internal mail flow are missing the required
608 # Exchange Server authentication mechanism. For more information about authentication
609 # on Receive connectors, see Receive connector authentication mechanisms.
610 ['5.3.3', 0, 0, 'unrecognized command'],
611  
612 # - SMTP commands are sent out of sequence (for example, a server sends an SMTP command
613 # like AUTH or MAIL FROM before identifying itself with the EHLO command). After es-
614 # tablishing a connection to a messaging server, the first SMTP command must always
615 # be EHLO or HELO.
616 ['5.5.2', 0, 0, 'send hello first'],
617 ],
618 $Sisimai::Eb::RePROC => [
619 # Exchange Server 2019 ----------------------------------------------------------------
620 # - You've configured a custom Receive connector in the Transport (Hub) service on a
621 # Mailbox server that listens on port 25. Typically, custom Receive connectors that
622 # listen on port 25 belong in the Front End Transport service on the Mailbox server.
623 # Important Exchange server components are inactive. You can confirm this by running
624 # the following command in the Exchange Management Shell:
625 # Get-ServerComponent -Identity <ServerName>.
626 # To restart all inactive components, run the following command:
627 # Set-ServerComponentState -Identity <ServerName> -Component ServerWideOffline
628 # -State Active -Requester Maintenance.
629 # Incompatible transport agents (in particular, after an Exchange update). After you
630 # identify the transport agent, disable it or uninstall it. For more information, see
631 # Troubleshoot transport agents.
632 ['4.3.2', 0, 0, 'service not available'],
633 ['4.3.2', 0, 0, 'service not active'],
634  
635 # - A mail loop was detected. Verify that the FQDN property on the Receive connector
636 # doesn't match the FQDN of another server, service, or device that's used in mail
637 # flow in your organization (by default, the Receive connector uses the FQDN of the
638 # Exchange server).
639 ['5.3.5', 0, 0, 'system incorrectly configured'],
640  
641 # Exchange Online ---------------------------------------------------------------------
642 # - Journaling on-premises messages to Microsoft 365 or Office 365 isn't supported for
643 # this organization because they haven't turned on Journaling Archive in their set-
644 # tings.
645 # - A journaling rule is configured in the organization's on-premises environment to
646 # journal on-premises messages to Microsoft 365 or Office 365, but Journaling Archive
647 # is disabled. For this scenario to work, the organization's Office 365 administrator
648 # should either enable Journaling Archive or change the journaling rule to journal
649 # messages to a different location.
650 ['5.3.190', 0, 0, 'when journaling archive is disabled'],
651  
652 # Previous versions of Exchange Server ------------------------------------------------
653 ['5.0.0', 0, 0, 'helo / ehlo requires domain address'],
654 ['5.1.4', 0, 0, 'destination mailbox address ambiguous'],
655 ['5.2.4', 0, 0, 'mailing list expansion problem'],
656 ['5.2.14', 0, 0, 'misconfigured forwarding address'],
657  
658 # Undocumented error messages ---------------------------------------------------------
659 # - 451 4.4.22 Message failed to be replicated: no healthy peers found ... (in reply to end of DATA command)
660 # - 451 4.4.23 Message failed to be replicated: No healthy secondary server available
661 # to accept replica at this time. ... (in reply to end of DATA command)
662 # - 451 4.4.28 Message failed to be replicated:
663 # Microsoft.Exchange.Transport.Net.Http.TransportHttpException(session Id: -1) ...(in reply to end of DATA command)
664 # - 451 4.4.28 Message failed to be replicated:
665 # System.Net.Http.HttpRequestException(session Id: ****) ... (in reply to end of DATA command)
666 ["4.4.", 22, 28, "message failed to be replicated:"],
667 ["4.4.3", 0, 0, "temporary server error. please try again later attr18"],
668 ["4.7.0", 0, 0, "temporary server error. please try again later. prx4 nexthop:"],
669  
670 # 550 5.4.318 Message expired, connection reset (SuspiciousRemoteServerError)
671 # 450 4.4.318 Connection was closed abruptly (SuspiciousRemoteServerError)
672 ['4.4.318', 0, 0, '(suspiciousremoteservererror)'],
673 ['5.4.318', 0, 0, '(suspiciousremoteservererror)'],
674  
675 # - status=deferred (host hotmail-com.olc.protection.outlook.com[192.0.2.1] said:
676 # 451 4.7.500 Server busy. Please try again later from [192.0.2.2]. (AS761) (in reply
677 # to RCPT TO command))
678 ['4.7.500', 0, 0, 'server busy. please try again later from '],
679  
680 # - status=deferred (host apc.olc.protection.outlook.com[192.0.2.1] said:
681 # 451 4.7.700 PFA agent busy, please try again. [***.***.prod.protection.outlook.com]
682 # (in reply to MAIL FROM command))
683 ['4.7.700', 0, 0, 'pfa agent busy, please try again.'],
684 ],
685 $Sisimai::Eb::ReDISK => [
686 # Exchange Server 2019 ----------------------------------------------------------------
687 # - Free disk space is low (for example, the disk that holds the queue database doesn't
688 # have the required amount of free space). For more information, see Understanding
689 # back pressure. To move the queue database to a different disk, see Change the loca-
690 # tion of the queue database.
691 # - Available memory is low (for example, Exchange installed on a virtual machine that
692 # is configured to use dynamic memory). Always use static memory on Exchange virtual
693 # machines.
694 ['4.3.1', 0, 0, 'insufficient system resources'],
695 ],
696 $Sisimai::Eb::ReUSER => [
697 # Exchange Server 2019 ----------------------------------------------------------------
698 # - The recipient's email address is incorrect (the recipient doesn't exist in the des-
699 # tination messaging system). Verify the recipient's email address. You recreated a
700 # deleted mailbox, and internal users are addressing email messages in Outlook or
701 # Outlook on the web using old entries in their autocomplete cache (the X.500 values
702 # or LegacyExchangeDN values for the recipient are now different). Tell users to de-
703 # lete the entry from their autocomplete cache and select the recipient again.
704 ['5.1.1', 0, 0, 'resolver.adr.exrecipnotfound; not found'],
705 ['5.1.1', 0, 0, 'user unknown'],
706  
707 # - The recipient's email address is incorrect (for example, it contains unsupported
708 # characters or invalid formatting).
709 ['5.1.3', 0, 0, 'storedrv.submit; invalid recipient address'],
710  
711 # - Receive connectors reject SMTP connections that contain the top level domains de-
712 # fined in RFC 2606 (.test, .example, .invalid, or .localhost), This behavior is con-
713 # trolled by the RejectReservedTopLevelRecipientDomains parameter on the New-Receive-
714 # Connector and Set-ReceiveConnector cmdlets.
715 ['5.1.', 4, 5, 'recipient address reserved by rfc 2606'],
716  
717 # - Receive connectors reject SMTP connections that contain single label domains (for
718 # example, chris@contoso instead of chris@contoso.com) This behavior is controlled by
719 # the RejectSingleLabelRecipientDomains parameter on the New-ReceiveConnector and
720 # Set-ReceiveConnector cmdlets.
721 ['5.1.6', 0, 0, 'recipient addresses in single label domains not accepted'],
722  
723 # Exchange Online ---------------------------------------------------------------------
724 # - This failure might be caused by the following conditions:
725 # - The recipient's email address was entered incorrectly by the sender.
726 # - No recipient's exists in the destination email system.
727 # - The recipient's mailbox has been moved and the Outlook recipient cache on the
728 # sender's computer hasn't updated.
729 # - An invalid legacy domain name (DN) exists for the recipient's mailbox Active Di-
730 # rectory Domain Service.
731 # - This error typically occurs when the sender of the message incorrectly enters the
732 # email address of the recipient. The sender should check the recipient's email ad-
733 # dress and send again. This error can also occur if the recipient email address was
734 # correct in the past but has changed or has been removed from the destination email
735 # system. If the sender of the message is in the same organization as the recipient,
736 # and the recipient's mailbox still exists, determine whether the recipient's mailbox
737 # has been relocated to a new email server. If this is the case, Outlook might not
738 # have updated the recipient cache correctly. Instruct the sender to remove the re-
739 # cipient's address from sender's Outlook recipient cache and then create a new mes-
740 # sage. Resending the original message will result in the same failure.
741 ['5.1.1', 0, 0, 'bad destination mailbox address'],
742  
743 # - The recipient's <SMTP Address> wasn't found by SMTP address lookup.
744 ['5.1.10', 0, 0, 'recipient not found'],
745  
746 # - The recipient's address doesn't exist.
747 ['5.4.1', 0, 0, 'recipient address rejected: access denied'],
748  
749 # - The recipient's <SMTP Address> domain is @hotmail.com or @outlook.com and it wasn't
750 # found by SMTP address lookup.
751 # - Similar to 550 5.1.10.
752 ['5.5.0', 0, 0, 'requested action not taken: mailbox unavailable'],
753  
754 # Previous versions of Exchange Server ------------------------------------------------
755 ['5.1.2', 0, 0, 'invalid x.400 address'],
756  
757 # Imported from Sisimai::/Lhost::Office365
758 ['5.1.351', 0, 0, 'remote server returned unknown recipient or mailbox unavailable'],
759 ],
760 };
761 118 state $errorcodes = {
762 # The mail server IP connecting to Outlook.com server has exceeded the rate limit allowed.
763 # Reason for rate limitation is related to IP/domain reputation.
764 "RP-001" => ["421", $Sisimai::Eb::ReFAMA],
765  
766 # The mail server IP connecting to Outlook.com server has exceeded the rate limit allowed
767 # on this connection. Reason for rate limitation is related to IP/domain reputation.
768 "RP-002" => ["421", $Sisimai::Eb::ReFAMA],
769  
770 # The mail server IP connecting to Outlook.com server has exceeded the connection limit
771 # allowed. Reason for limitation is related to IP/domain reputation.
772 "RP-003" => ["421", $Sisimai::Eb::ReFAMA],
773  
774 # Mail rejected by Outlook.com for policy reasons. Reasons for rejection may be related
775 # to content with spam-like characteristics or IP/domain reputation.
776 "SC-001" => ["550", $Sisimai::Eb::ReFAMA],
777  
778 # Mail rejected by Outlook.com for policy reasons. The mail server IP connecting to
779 # Outlook.com has exhibited namespace mining behavior.
780 "SC-002" => ["550", $Sisimai::Eb::ReWONT],
781  
782 # Mail rejected by Outlook.com for policy reasons. Your IP address appears to be an
783 # open proxy/relay.
784 "SC-003" => ["550", $Sisimai::Eb::ReBLOC],
785  
786 # Mail rejected by Outlook.com for policy reasons. A block has been placed against your
787 # IP address because we have received complaints concerning mail coming from that IP
788 # address. We recommend enrolling in our Junk Email Reporting Program (JMRP), a free
789 # program intended to help senders remove unwanted recipients from their email list
790 "SC-004" => ["550", $Sisimai::Eb::ReBLOC],
791  
792 # Mail rejected by Outlook.com for policy reasons. We generally do not accept email
793 # from dynamic IP's as they are not typically used to deliver unauthenticated SMTP email
794 # to an Internet mail server. (Spamhaus)
795 "DY-001" => ["550", $Sisimai::Eb::ReBLOC],
796  
797 # Mail rejected by Outlook.com for policy reasons. The likely cause is a compromised or
798 # virus infected server/personal computer.
799 "DY-002" => ["550", $Sisimai::Eb::ReEXEC],
800  
801 # Mail rejected by Outlook.com for policy reasons. If you are not an email/network admin
802 # please contact your Email/Internet Service Provider for help. For more information
803 # about this block and to request removal please go to: Spamhaus.
804 "OU-001" => ["550", $Sisimai::Eb::ReBLOC],
805  
806 # Mail rejected by Outlook.com for policy reasons. Reasons for rejection may be related
807 # to content with spam-like characteristics or IP/domain reputation.
808 "OU-002" => ["550", $Sisimai::Eb::ReFAMA],
809 };
810  
811 118 my $statuscode = $argvs->{'deliverystatus'};
812 118 my $thirddigit = int [split /[.]/, $statuscode]->[-1];
813 118 my $issuedcode = lc $argvs->{'diagnosticcode'};
814  
815 118 for my $e ( keys %$messagesof ) {
816 # Each key is a reason name
817 1698 for my $f ( $messagesof->{ $e }->@* ) {
818 # ["status-code", min, max, "error message"]
819 9870 ▶ if( $f->[1] == $f->[2] ) {
Branch: 1 branch
BranchTrueFalseTotal
if ($f->[1] == $f->[2]) { } 9154 716 9870
820 # This error code have no range
821 9154 ▶ next unless $statuscode eq $f->[0];
Branch: 1 branch
BranchTrueFalseTotal
unless $statuscode eq $f->[0] 9008 146 9154
822  
823 } else {
824 # This error code has a range
825 716 ▶ next if index($statuscode, $f->[0]) < 0;
Branch: 1 branch
BranchTrueFalseTotal
if index($statuscode, $f->[0]) == -1 591 125 716
826 125 ▶ next if $thirddigit < $f->[1];
Branch: 1 branch
BranchTrueFalseTotal
if $thirddigit < $f->[1] 71 54 125
827 54 ▶ next if $thirddigit > $f->[2];
Branch: 1 branch
BranchTrueFalseTotal
if $thirddigit > $f->[2] 46 8 54
828 }
829 154 ▶ return $e if index($issuedcode, $f->[3]) > -1;
Branch: 1 branch
BranchTrueFalseTotal
if index($issuedcode, $f->[3]) != -1 103 51 154
830 }
831 }
832 15 for my $e ( keys %$errorcodes ) {
833 # The key name is an error code described at Outlook.com Postmaster/Troubleshooting
834 # https://substrate.office.com/ip-domain-management-snds/postmaster/troubleshooting
835 165 ▶ next if index($argvs->{'diagnosticcode'}, $e) < 0;
Branch: 1 branch
BranchTrueFalseTotal
if index($argvs->{"diagnosticcode"}, $e) == -1 165 0 165
836 0 ▶ return $errorcodes->{ $e }->[1] if $argvs->{'replycode'} eq $errorcodes->{ $e }->[0];
Branch: 1 branch
BranchTrueFalseTotal
if $argvs->{"replycode"} eq $errorcodes->{$e}[0] 0 0 0
837 }
838 15 return "";
839 }
840  
841 10 1;
842 __END__
« Sisimai/Lhost/OpenSMTPD.pm ↑ Summary Sisimai/Reason/Rejected.pm »