Bounce Reason List

Sisimai can detect the following 27 bounce reasons from the parsed bounce message. Detected error reason is set in the value of "reason" accessor of Sisimai::Data object in lower case like "userunknown", "expired".

By Address

The message you sent has rejected due to a sender's email address or a recipient's email address.

Read

By Content

The message you sent has rejected due to a message content: a part of a message header and a message body.

Read

By Server

The message you sent rejected due to status on a local MTA or a remote MTA.

Read

Others

Rejected due to other reason or Sisimai could not detect the reason

Read

Table of Bounce Reasons

Sisimai can detect 27 bounce reasons and set the reason into the value of "reason" in the parsed results. The value of "reason" is written in lower case like "userunknown", "expired".

reason() method of Sisimai class is useful to get all the bounce reasons Sisimai can detect.

Reason Name Hard Bounce Description
Host Unknown Yes Destination host name does not exist
User Unknown Yes Recipient's address does not exist
Filtered No Rejected after DATA command
Has Moved Yes Destination mail addrees has moved
Rejected No Rejected due to envelope from address
Mailbox Full No Recipient's mailbox is full
Suspend No Recipient's account is suspended
Vacation No Auto replied message (recipient is away)
Content Error No Email body or header is invalid format
Exceed Limit No Message size exceeded the limit(5.2.3)
Feedback No Bounced for a complaint of the message(FBL)
Mesg Too Big No Message size is too big(5.3.4)
Security Error No Virus detected or authentication error
Spam Detected No Detected a message as spam
Blocked No Blocked due to client IP address or hostname
Expired No Delivery time expired
Mailer Error No Mailer program error on remote host
Network Error No Network error: DNS or routing
No Relaying No Relay access denied
Not Accept No Destinaion does not accept any message
System Error No Some error on the destination host
System Full No Disk full on the destination host
Too Many Conn No Connection rate limit exceeded
Delivered No Successfully delivered
Syntax Error No syntax error in SMTP
On Hold No Deciding the bounce reason is on hold
Undefined No Could not decide an error reason

Rejected By Address

The following shows the list of reasons that the message you sent has rejected due to an envelope sender's email address, an envelope recipient's email address, or a recipient's mailbox status.

Host Unknown (Hard bounce)

This is the error that a domain part (Right hand side of @ sign) of a recipient's email address does not exist. In many cases, the domain part is misspelled, or the domain name has been expired. Sisimai will set "hostunknown" to the reason of email bounce if the value of Status: field in a bounce mail is "5.1.2".

Your message to the following recipients cannot be delivered:

<kijitora@example.cat>:
<<< No such domain.
                
  • No such domain.
  • all host address lookups failed permanently
  • all relevant MX records point to non-existent hosts
  • Unrouteable address
  • 554 5.4.4 SMTPSEND.DNS.NonExistentDomain
  • Illegal host/domain name found
  • Sorry, I couldn't find any host by that name. (#4.1.2)
  • Host or domain name not found
  • The mail could not be delivered to the recipient because the domain is not reachable

User Unknown (Hard bounce)

This is the error that a local part (Left hand side of @ sign) of a recipient's email address does not exist. In many cases, a user has changed internet service provider, or has quit the company, or the local part is misspelled. Sisimai will set "userunknown" to the reason of email bounce if the value of Status: field in a bounce email is "5.1.1", or connection was refused at SMTP RCPT command, or the contents of Diagnostic-Code: field represents that it is unknown user.

<kijitora@example.co.jp>: host mx01.example.co.jp[192.0.2.8] said:
550 5.1.1 Address rejected kijitora@example.co.jp (in reply to
RCPT TO command)
                
  • not listed in Domino Directory / Public Name & Address Book
  • 550 5.1.1 RESOLVER.ADR.RecipNotFound
  • 550 5.1.1 RESOLVER.ADR.ExRecipNotFound
  • Invalid final delivery userid
  • Sorry, no mailbox here by that name. (#5.1.1)
  • <neko@example.jp>: 192.0.2.153 does not like recipient. Remote host said: 550 5.2.1 ...
  • Requested action not taken: mailbox unavailable

Filtered

This is the error that an email has been rejected by a header content after the SMTP DATA command. In Japanese cellular phones, the error will incur that a sender's email address or a domain is rejected by recipient's email configuration. Sisimai will set "filtered" to the reason of email bounce if the value of Status: field in a bounce email is "5.2.0" or "5.2.1".

This error reason is almost the same as UserUnknown.

... while talking to mfsmax.ntt.example.ne.jp.:
>>> DATA
<<< 550 Unknown user kijitora@ntt.example.ne.jp
554 5.0.0 Service unavailable
                
  • Cannot route mail to user
  • 550 5.7.1 RESOLVER.RST.AuthRequired
  • 550 5.2.1 <kijitora@example.jp>... User Unknown
  • 550 Unknown user kijitora@example.net (in reply to end of DATA command)
  • 554 delivery error: dd This user doesn't have a yahoo.com account (this-local-part-does-not-exist@yahoo.com) [0] - mta1061.mail.ne1.yahoo.com
  • 550 5.1.1 RCP-P2 http://postmaster.facebook.com/response_codes?ip=192.0.2.135#rcp Refused due to recipient preferences

Has Moved (Hard bounce)

This is the error that a user's mailbox has moved (and is not forwarded automatically). Sisimai will set "hasmoved" to the reason of email bounce if the value of Status: field in a bounce email is "5.1.6".

<kijitora@example.go.jp>: host mx1.example.go.jp[192.0.2.127] said: 550 5.1.6 recipient
no longer on server: kijitora@example.go.jp (in reply to RCPT TO command)
                
  • <kijitora@example.go.jp>: host mx1.example.go.jp[192.0.2.127] said: 550 5.1.6 recipient no longer on server: kijitora@example.go.jp (in reply to RCPT TO command)
  • 551 not our user
  • 551 not our customer
  • The e-mail address neko@example.jp has been replaced by nyaan@example.jp

Rejected

This is the error that a connection to destination server was rejected by a sender's email address (envelope from). Sisimai set "rejected" to the reason of email bounce if the value of Status: field in a bounce email is "5.1.8" or the connection has been rejected due to the argument of the SMTP MAIL command.

<kijitora@example.org>:
Connected to 192.0.2.225 but sender was rejected.
Remote host said: 550 5.7.1 <root@nijo.example.jp>... Access denied
                
  • 550 5.7.1 RESOLVER.RST.NotAuthorized
  • 553 5.1.8 <neko@neko.example.jp>... Domain of sender address root@neko.example.jp does not exist (in reply to MAIL FROM command)
  • Connected to 192.0.2.225 but sender was rejected. Remote host said: 550 5.7.1 <neko@nijo.example.jp>... Access denied
  • 553 5.1.8 <neko@nyaan.example.jp>... Domain of sender address neko@nyaan.example.jp does not exist
  • SMTP error from remote mail server after MAIL FROM:<neko@nyaan.example.jp> SIZE=1420: host mx.libsisimai.org [192.0.2.135]: 550 5.1.8 <neko@nyaan.example.jp>... Error

Mailbox Full

This is the error that a recipient's mailbox is full. Sisimai will set "mailboxfull" to the reason of email bounce if the value of Status: field in a bounce email is "4.2.2" or "5.2.2".

Action: failed
Status: 5.2.2
Diagnostic-Code: smtp;550 5.2.2 <kijitora@example.jp>... Mailbox Full
  • mailbox is full
  • User mailbox exceeds allowed size
  • 552 Error: disk quota exceeded
  • Could not be delivered to: <kijitora@**.**.ne.jp> As their mailbox is full.
  • The number of messages in recipient's mailbox exceeded the local limit.
  • The user(s) account is temporarily over quota
  • The recipient's mailbox is full and can't accept messages now.
  • #550 5.2.2 STOREDRV.Deliver: mailbox full.
  • The e-mail message could not be delivered because the user's mailfolder is full.
  • This person's account is exceeding their quota.

Suspend

This is the error that a recipient account is being suspended due to unpaid or other reasons.

SMTP error from remote mail server after end of data: host mx2.mail.yahoo.com [192.0.2.222]:
554 delivery error: dd Sorry your message to **@yahoo.com.ar cannot be delivered.
This account has been disabled or discontinued [#102]. - mta497.mail.mud.yahoo.com"
                
  • Mailaddress is administratively disabled
  • The user(s) account is disabled.
  • The user(s) account is temporarily limited.
  • dd Sorry your message to ****@yahoo.com.ar cannot be delivered. This account has been disabled or discontinued [#102].
  • 525 5.7.13 Disabled recipient address
  • 550 [SUSPEND] Mailbox currently suspended - Please contact correspondent directly

Vacation

This is the reason that the recipient is out of office. The bounce message is generated and returned from the auto reponder program. This reason has added in Sisimai 4.1.28 and does not exist in any version of bounceHammer.

I am out of the office until 05/01/2010.

I am of the office returning 5th Jan
                

Rejected By Content

The following shows the list of reasons that the message you sent has rejected due to the contents of the message by a spam filter or an MTA program on a remote host.


Content Error

This is the error that a destination mail server has rejected email due to header format of the email like the following. Sisimai will set "contenterror" to the reason of email bounce if the value of Status: field in a bounce email is "5.6.*".

  • 8 bit data in message header
  • Too many "Received" headers
  • Invalid MIME headers
... while talking to g5.example.net.:
>>> DATA
<<< 550 5.6.9 improper use of 8-bit data in message header
554 5.0.0 Service unavailable
                
  • Too many "Received" headers - suspected mail loop
  • 550 5.6.9 improper use of 8-bit data in message header
  • 500 5.6.1 Message content rejected

Exceed Limit

This is the error that a message was rejected due to an email exceeded the limit. The value of D.S.N. is "5.2.3". This reason is almost the same as "MesgTooBig", we think. Because when a message is delivered to the local host, the status code will be set as "5.2.3" in Sendmail's source code: deliver.c.

1586: if (bitnset(M_LOCALMAILER, to->q_mailer->m_flags))
1587:     to->q_status = "5.2.3";
1588: else
1589:     to->q_status = "5.3.4";
                
... while talking to mx.example.org.:
>>> MAIL From:<kijitora@example.co.jp> SIZE=16600348
<<< 552 5.2.3 Message size exceeds fixed maximum message size (10485760)
554 5.0.0 Service unavailable
                
  • The message exeeded the maximum size the user accepts
  • 552 5.2.3 Message size exceeds fixed maximum message size (10485760)
  • maildir delivery failed: Sorry, the user's maildir has overdrawn his diskspace quota, please try again later.
  • 552-5.2.3 Your message exceeded Google's message size limits. Please visit http://mail.google.com/support/bin/answer.py?answer=8770 to review our size guidelines.
  • 552 5.2.3 Message exceeds local size limit.
  • 550 5.2.3 RESOLVER.RST.SendSizeLimit.Org; message too large for this organization

Feedback

The message you sent was forwarded to the sender as a complaint message from your mailbox provider. When Sismai has set "feedback" to the reason, the value of "feedbacktype" is also set like the following parsed data.

[
    {
        "token": "491f2fd0f90ee3017f2ab2eb67a1239b78a84321",
        "deliverystatus": "",
        "destination": "yahoo.com",
        "timezoneoffset": "-0800",
        "smtpcommand": "",
        "listid": "",
        "replycode": "",
        "subject": "Nyaaaaaaaan",
        "diagnostictype": "SMTP",
        "diagnosticcode": "This is an email abuse report for an email message received from mx8.example.com  on Thu, 29 Apr 2013 23:45:00 PST",
        "senderdomain": "example.com",
        "feedbacktype": "abuse",
        "alias": "",
        "reason": "feedback",
        "addresser": "shironeko@example.com",
        "lhost": "smtp-gw83.example.com",
        "smtpagent": "Yahoo!-Mail-Feedback/1.0",
        "rhost": "uid",
        "messageid": "000000000000000000000000.smtp@example.com",
        "action": "failed",
        "recipient": "this-local-part-does-not-exist-on-yahoo@yahoo.com",
        "timestamp": 1367307950
    }
]
                
  • If you would like to cancel or change the configuration for your FBL please use the tool located at: http://postmaster.example.net/waters/fbl_change_form.html
  • This is an email abuse report for an email message received from IP 192.0.2.45 on Wed, 12 Nov 2014 12:40:48 +0000. The message below did not meet the sending domain's dmarc policy. For more information about this format please see http://tools.ietf.org/html/rfc6591 .
  • This is an opt-out report for an email message received from IP 192.0.2.89 on Thu, 9 Apr 2006 23:34:45 JST. For more information about this format please see http://www.example.org/arf/.

Message Too Big (mesgtoobig)

This is the error that a sent email size is too big for a destination mail server. In many cases, There are many attachment files by email, or the file size is too large. Sisimai will set "mesgtoobig" to the reason of email bounce if the value of Status: field in a bounce email is "5.3.4".

Action: failure
Status: 553 Exceeded maximum inbound message size
                
  • 550 5.2.3 RESOLVER.RST.RecipSizeLimit
  • sorry, that message size exceeds my databytes limit (#5.3.4)
  • 552 sorry, that message size exceeds my databytes limit (#5.3.4)
  • 553 Exceeded maximum inbound message size
  • Mail size limit exceeded.
  • 552 5.3.4 Message too large
  • message size 18876259 exceeds size limit 10485760 of server neko.example.jp[192.0.2.2]
  • 534 SIZE=Message too big. (in reply to MAIL FROM command)
  • 554 5.7.1 Message Rejected Class=size limit=15728640 Subclass=reject size=18571048 (in reply to end of DATA command)
  • Remote host said: 552 Message size exceeds fixed maximum message size: 1048576 bytes
  • 552 Message size exceeds maximum value

Security Error

This is the error that a security violation was detected on a destination mail server. Depends on the security policy on the server, there is any virus in the email, a sender's email address is assumed. Sisimai will set "securityerror" to the reason of email bounce if the value of Status: field in a bounce email is "5.7.*".

Status: 5.7.0
Remote-MTA: DNS; gmail-smtp-in.l.google.com
Diagnostic-Code: SMTP; 552-5.7.0 Our system detected an illegal attachment on your message. Please
                
  • Requested action not taken: virus detected
  • Could not retrieve credentials
  • 552-5.7.0 This message was blocked because its content presents a potential security issue.
  • 552-5.7.0 Our system detected an illegal attachment on your message. Please visit http://mail.google.com/support/bin/answer.py?answer=6590 to review our attachment guidelines.
  • 554 email rejected due to security policies
  • SMTP Server <mta.neko.exampe.jp> rejected recipient <nyaan@neko.example.jp> (Error following RCPT command). It responded as follows: [550 Previous (cached) callout verification failure]
  • Technical details of permanent failure: You have exceeded the the allowable number of posts without solving a captcha.
  • 553 From <>, message blocked, you are not authorized to send mail, authentication is required.

Spam Detected

This is the error that the message you sent was rejected by the spam filter running on the remote host. This reason has added in Sisimai 4.1.25 and does not exist in any version of bounceHammer.

Action: failed
Status: 5.7.1
Diagnostic-Code: smtp; 550 5.7.1 Message content rejected, UBE, id=00000-00-000
Last-Attempt-Date: Thu, 9 Apr 2008 23:34:45 +0900 (JST)
                
  • Our system has detected that this message is likely unsolicited mail.
  • 550 5.7.1 message content rejected
  • 550 Spam refused.
  • 554 imta14.emeryville.ca.mail.comcast.net comcast 192.0.2.4 Comcast block for spam. Please see http://postmaster.comcast.net/smtp-error-codes.php#BL000000
  • User profile spam level exceeded
  • 550-Blacklisted URL in message. (example.com) in [black]. See http://lookup.uribl.com.
  • 550-5.7.1 [192.0.2.6] Our system has detected that this message is likely unsolicited mail. To reduce the amount of spam sent to Gmail, this message has been blocked. Please visit http://support.google.com/mail/bin/answer.py?hl=en&answer=188131 for more information.
  • 550 5.7.1 Your email breaches local URIBL policy. (in reply to end of DATA command)
  • 554 5.7.1 Message cannot be accepted, spam rejection (in reply to end of DATA command)
  • 550 Error: SPAM-ID: e00000000-000000 Your email had spam-like header contents. Please contact your email service provider. (in reply to end of DATA command)
  • 550 ****(0000): Your email was detected as spam. (RCPTs: neko@example.org) (in reply to end of DATA command)
  • 550 Denied due to spam list (in reply to RCPT TO command)
  • 554 5.7.1 Mail (22222-22222) appears to be unsolicited - Score (222) over MessageScoringUpperLimit (22) - send error reports to postmaster@example.org
  • 554 5.7.1 Your message failed several antispam checks (SCORING) and it was rejected or collected on example.net spambox. Please be sure your mailserver is configured correctly (spf , HELO, PTR) or try using an alternative email or smtp.
  • 550 Probable Spam (in reply to end of DATA command)
  • 550 5.7.1 Message content rejected, UBE, id=00000-00-000

Rejected By Server

The following shows the list of reasons that the message you sent has rejected due to things about a local MTA such as a hostname, IP address, and internal status of a remote MTA such as the number of concurrent connections, resolver, and other backend systems.

Blocked

This is the error that SMTP connection was rejected due to a client's IP address or a hostname, or the parameter of the HELO/EHLO command. This reason has added in Sisimai 4.0.0 and does not exist in any version of bounceHammer.

<kijitora@example.net>: 
Connected to 192.0.2.112 but my name was rejected. 
Remote host said: 501 5.0.0 Invalid domain name
                
  • 550 5.7.1 can't determine Purported Responsible Address
  • SMTP error from remote mail server after MAIL FROM:<shironeko@example.jp> SIZE=1543: host mx.example.jp [192.0.2.20]: 550 5.7.0 <shironeko@example.jp>... Please use the smtp server of your ISP.
  • host mxs.mail.ru[194.67.23.20] said: 550 Access from ip address 192.0.2.4 blocked. Visit http://win.mail.ru/cgi-bin/support_bl?ip=192.0.2.4 (in reply to RCPT TO command)
  • Connected to 192.0.2.112 but my name was rejected. Remote host said: 501 5.0.0 Invalid domain name
  • 450 4.7.1 Access denied. IP name lookup failed [192.0.2.222]
  • 5.1.0 - Unknown address error 550-'5.7.1 <000001321defbd2a-788e31c8-2be1-422f-a8d4-cf7765cc9ed7-000000@email-bounces.amazonses.com>... Access denied' (delivery attempts: 0)
  • The error that the other server returned was: 554 554 5.7.1 Service unavailable; Client host [192.0.2.49] blocked using cbl.abuseat.org (state 13).

Expired

This is the error that delivery time has expired due to connection failure or network error and the message you sent has been in the queue for a long time.

kijitora@example.org
(ultimately generated from nekochan@example.org)
all hosts have been failing for a long time and were last
tried after this message arrived
                
  • 550 4.4.7 QUEUE.Expired
  • Delivery failed 22 attempts
  • Envelope expired
  • retry timeout exceeded
  • Your message was not delivered within 0 days and 1 hours.
  • Host not reachable
  • 4.4.7 (unable to deliver this message after 1 day)
  • <neko@nyan.example.org>: connect to nyaan.example.org[192.0.2.1]:25: Connection timed out
  • Deferred: 421 Message could not be delivered for 8 hours Message will be deleted from queue
  • 421 example.com (smtp)... Deferred: Connection timed out during user open with example.com
  • Routing: Could not find a gateway for kijitora@example.co.jp
  • Delevery to the following recipients was aborted after 5.0 hour(s):
  • The following message, addressed to 'neko@nyaan.example.jp', failed because it has not been collected after 30 days
  • 5.4.7 - Delivery expired (message too old) 'timeout' (delivery attempts: 0)
  • 554 4.4.7 Message expired: unable to deliver in 840 minutes. <421 4.4.2 Connection timed out> Status: 4.4.7
  • Unable to deliver message to the following recipients, due to being unable to connect successfully to the destination mail server.
  • kijitora:00000:<kijitora@example.org> : Connection timed out in connect
  • kijitora@7jo.example.jp Error, ERROR_CODE :421, ERROR_CODE :, Host not reachable.

Mailer Error

This is the error that a mailer program has not exited successfully or exited unexpectedly on a destination mail server.

X-Actual-Recipient: X-Unix; |/home/kijitora/mail/catch.php
Diagnostic-Code: X-Unix; 255
                
  • 554 5.3.0 unknown mailer error 255
  • <r@p351355.pool.example.ne.jp> (expanded from <kijitora@example.org>): user unknown. Command output: procmail: Couldn't create "/var/spool/mail/neko" id: r.example.org: No such user
  • |IFS=' ' && exec /usr/local/bin/procmail -f- || exit 75 #kijitora@mailx-53.neko.example.edu
  • temporary failure. Command output: avpcheck: unable to connect to avp daemon: Connection refused
  • Command died with status 17: "/usr/sbin/amavis". Command output: Can't use an undefined value as a symbol reference at /usr/sbin/amavis line 1178.

Network Error

This is the error that SMTP connection failed due to DNS lookup failure or other network problems. This reason has added in Sisimai 4.1.12 and does not exist in any version of bounceHammer.

A message is delayed for more than 10 minutes for the following
list of recipients:

kijitora@neko.example.jp: Network error on destination MXs
  • DNS lookup failed.
  • 554 5.4.4 SMTPSEND.DNS.MxLoopback
  • Message has exceeded maximum hop count
  • Temporary failure in MX lookup
  • Address family mismatch on destination MXs
  • unrouteable mail domain "non-local.example" (:fail:)
  • Name service error for name=example.org type=MX: Malformed or unexpected name server reply
  • Name service error for domain digicool.com: Host not found, try again
  • Sorry, I wasn't able to establish an SMTP connection. (#4.4.1)
  • 554 5.4.6 Too many hops 26 (25 max): from <shironeko@example.jp> via localhost, to <kijitora@example.com>
  • Unable to deliver message to the following recipients, because the message was forwarded more than the maximum allowed times. This could indicate a mail loop.

No Relaying

This is the error that SMTP connection rejected with error message "Relaying Denied". This reason does not exist in any version of bounceHammer.

... while talking to mailin-01.mx.example.com.:
>>> RCPT To:<kijitora@example.org>
<<< 554 5.7.1 <kijitora@example.org>: Relay access denied
554 5.0.0 Service unavailable
                
  • Due to the following SMTP relay error
  • host neko.example.com[192.0.2.22] said: 550 5.7.1 Unable to relay for nyaan@neko.example.com (in reply to RCPT TO command)
  • 192.0.2.1 does not like recipient. Remote host said: 554 5.7.1 <neko@example.com>: Relay access denied
  • 554 5.7.1 <kijitora@example.org>: Relay access denied
  • 550 Insecure Mail Relay

Not Accept

This is the error that a destination mail server does (can) not accept any email. In many cases, the server is high load or under the maintenance. Sisimai will set "notaccept" to the reason of email bounce if the value of Status: field in a bounce email is "5.3.2" or the value of SMTP reply code is "556".

  • an MX or SRV record indicated no SMTP service
  • no host found for existing SMTP connection
  • Destination seem to reject all mails

System Error

This is the error that an email has bounced due to system error on the remote host such as LDAP connection failure or other internal system error.

<kijitora@example.net>: 
Unable to contact LDAP server. (#4.4.3)I'm not going to try again; this
message has been in the queue too long.
                
  • This domain's DNS violates RFC 1035.
  • Several matches found in Domino Directory
  • delivery to file forbidden
  • delivery to pipe forbidden
  • 550 5.2.0 RESOLVER.ADR.BadPrimary
  • 550 5.1.0 RESOLVER.ADR.InvalidInSmtp
  • 550 5.1.4 RESOLVER.ADR.Ambiguous
  • 451 Temporary local problem - please try later (in reply to end of DATA command)
  • Unable to contact LDAP server. (#4.4.3) I'm not going to try again;
  • 550 5.3.5 <kuroneko@example.org>... Internal System Error
  • 500 Remote server does not support TLS (state 6).

System Full

This is the error that a destination mail server's disk (or spool) is full. Sisimai will set "systemfull" to the reason of email bounce if the value of Status: field in a bounce email is "4.3.1" or "5.3.1".

  • Requested action not taken: mailbox unavailable (not enough free space)
  • 452 4.4.5 Insufficient disk space; try again later

Too Many Connections (toomanyconn)

This is the error that SMTP connection was rejected temporarily due to too many concurrency connections to the remote server. This reason has added in Sisimai 4.1.26 and does not exist in any version of bounceHammer.

<kijitora@example.ne.jp>: host mx02.example.ne.jp[192.0.1.20] said:
452 4.3.2 Connection rate limit exceeded. (in reply to MAIL FROM command)
  • 550 5.5.3 RESOLVER.ADR.RecipLimit
  • 452 4.3.2 Connection rate limit exceeded. (in reply to MAIL FROM command)

Others

Rejected due to other reason or Sisimai could not detect the reason

Delivered (beginning with v4.16.0)

This reason is NOT AN ERROR and means that an email you sent is successfully delivered to the recipient. Sisimai will set "delivered" to the reason of email bounce if the value of Status: field in a bounce mail begins with "2".

This reason is not included in the parsed results by default. To get the parsed results which are including this reason, specify "delivered" option at the argument of make(), dump() method of Sisimai like following sample codes.

Final-Recipient: rfc822; kijitora@neko.nyaan.jp
Action: deliverable
Status: 2.1.5
Diagnostic-Code: SMTP; 250 2.1.5 OK
                
Perl
#! /usr/bin/env perl
my $v = Sisimai->make('/path/to/mbox', 'delivered' => 1);
my $r = Sisimai->dump('/path/to/mbox', 'delivered' => 1);
my $d = Sisimai::Data->make('data' => $q, 'delivered' => 1);
                
Ruby
#! /usr/bin/env ruby
v = Sisimai.make('/path/to/mbox', delivered: true)
r = Sisimai.dump('/path/to/mbox', delivered: true)
d = Sisimai::Data.make(data: q, delivered: true)
                

Syntax Error (Beginning with v4.17.0)

This is the error that a destination mail server could not recognize SMTP command which is sent from a sender's MTA.
This reason has been added at Sisimai v4.17.0.

  • 503 Improper sequence of commands
  • 504 Command parameter not implemented

On Hold

Sisimai will set "onhold" to the reason of email bounce if there is no (or less) detailed information about email bounce for judging the reason.


Undefined

Sisimai could not detect the error reason. In many cases, the error message is written in non English or there is no enough error message in a bounce email to decide the reason.