Description

This article will cover the list of reason codes and descriptions that can appear in MPmail live tracking.



Definitions


ham  : opposite of spam

RBL   : Real time Black List


Solution

Reason
 
Definition
 
Activity
 
450 4.1.1
 
Rejection when relay check is enabled
 
Blocked
 
450 4.1.8
 
Sender address rejected: Domain not found
 
Blocked
 
450 4.5.5
 
E-Mail deferred because of detected spam sending

The email has been temporarily rejected because spam had been sent from the email address of the sender. You can unlock the email address by clicking on the displayed URL.
Blocked
 
450 4.5.5
too many false recipients rate-limited

The email has been temporarily rejected because it contains too many false recipients.
Blocked
450 4.5.5

unblock {URL}

The email has been temporarily rejected due to contents in its header. You can unlock the email address by clicking on the displayed URL.
Blocked
450 4.5.6
 
The email has been temporarily rejected due to server overload.
Blocked
450 4.5.7
loop detected, by {relay}

The email has been temporarily rejected because a loop has been detected. The hostname of our relay is displayed.
Blocked
450 4.5.7
 
The email has been temporarily rejected due to server overload. The hostname of our gateway is displayed. Blocked
 
450 4.5.8
no mail data, by {relay}

The email has been temporarily rejected because it does not have any content. The hostname of our relay may be displayed.
Blocked
450 4.5.8
too much load try next hop

The email has been temporarily rejected because due to server overload. The delivery should be tried through a different hop.
Blocked
450 4.5.9
Connection PID broken $CLEANUPID by $(hostname)

The email has been temporarily rejected because of a system error.
Blocked
450 4.5.9
Greylisted, please try again later

The email has been temporarily rejected because of greylisting.
Blocked
450 4.5.9
no resources please take next hop. by {relay}

The email has been temporarily rejected because no resources were available for the reception. The delivery should be tried through a different hop. The hostname of our relay is displayed.
Blocked
450 4.5.9
no smtp resources, please take next hop. by {relay}

The email has been temporarily rejected because no SMTP resources were available for the reception. The hostname of our relay is displayed.
Blocked
450 5.5.6
loop detected

The email has been temporarily rejected because a loop has been detected.
Blocked
504 5.5.2
 
Sender address rejected: need fully-qualified address

The email has been rejected because the recipient’s email address was incomplete.
Blocked
523 5.2.3
E-Mail rejected, e-mail is too large by company rule {rule ID}

The email has been rejected because it exceeded a size limit defined by the customer. The rule ID is displayed.
Blocked
550 5.1.1
 
Recipient address rejected: undeliverable address

The email has been rejected because the recipient’s email address does not exist. 
Blocked
550 5.5.3
Recipient address rejected: Multi-recipient bounce
Blocked
552 5.2.2
Mailbox not available. For more information visit {URL}

The email has been rejected due to the recipient’s or the sender’s email address. The hostname of our gateway is displayed.
Blocked
552 5.5.2
Message size exceeds fixed maximum message size. Size: {email size}, Max size: {maximum size} by {gateway}

The email has been rejected because it exceeds the size limit at the gate. The hostname of our gateway is displayed.
Blocked
552 5.5.2
Size: {email size}

The email has been rejected according to the Content Control policies because it does not comply with the applicable size limits. The email size is specified.
Blocked
552 5.5.8
utilize smarthost instead of MX by {gateway}

The email has been rejected because it should be sent via a smarthost and not directly to the gate. The hostname of our gateway is displayed.
Blocked
554 5.5.3
 
e-mail Rejected Content Filter Size
 
Blocked
 
554 5.5.4
 
Your IP {IP address} address has a bad reputation. To unblock visit {URL}

The email has been rejected because your IP address has a negative reputation. You can unlock your email address by following the given URL. 
Blocked
554 5.5.5
 
e-mail Rejected Spam

The email has been rejected because it contains spam. To send a request to support, click on the given URL. 
Blocked
554 5.5.6
 
Loop detection > 10 times X-everycloud-disclaimer
 
Blocked
 
554 5.5.7
 
e-mail Rejected Content Attachment
 
Blocked
 
554 5.6.0
unblock {URL}

The email has been rejected because its header is too big. To send a request to support, click on the given URL.
Blocked
554 5.6.1
 
E-Mail rejected because of Spam-Header to unlock goto {URL}

Your email has been rejected because it has been identified as spam based on its header. You can unlock the email address by clicking on the displayed URL.
Blocked
 
554 5.6.1
Your mailheader contains SPAM. To unblock visit {URL}

Your email has been rejected because it has been identified as spam based on its header. You can unlock the email address by clicking on the displayed URL.
Blocked
554.5.6.2
 
E-Mail rejected because of Spam-http-Link to unlock goto {URL}

Your email has been rejected because it has been identified as spam based on a link. You can unlock the email address by clicking on the displayed URL.
Blocked
 
554 5.6.2
Your mail contains a SPAM-LINK. To unblock visit {URL}

Your email has been rejected because it has been identified as spam based on a link. You can unlock the email address by clicking on the displayed URL.
Blocked
554 5.6.3
 
E-Mail rejected because of Spam-Body to unlock goto {URL}

Your email has been rejected because it has been identified as spam based on its text. You can unlock the email address by clicking on the displayed URL.
Blocked
554 5.6.3
Your mail contains SPAM. To unblock visit {URL}

The email has been rejected because it contains spam. You can unlock the email address by clicking on the displayed URL.
Blocked
554 5.6.4
E-Mail rejected, forbidden attachment by company rule Attachments {rule ID}

The email has been rejected because it contains a forbidden attachment according to rules defined by the customer. The rule ID is displayed.
Blocked
554 5.6.4
 
E-Mail rejected Virus found, for support contact {URL}

The email has been rejected because it contains viruses. To send a request to support, click on the given URL. 
Blocked
554 5.6.5
TLS encryption required by customer rule;

The email has been rejected because it was not encrypted with TLS and TLS encryption is required by a rule defined by the customer.
Blocked
554 5.6.5
TLS encryption required by customer rule by {gateway};

The email has been rejected because it was not encrypted with TLS and TLS encryption is required by a rule for the specified host defined by the customer. The hostname of our gateway is displayed.
Blocked
554 5.6.9
Customer rule based reject by antispameurope Compliancfilter ID={rule ID}


The email has been rejected by the specified Compliance Filter rule. The rule ID is displayed.
Blocked
554 5.6.9
Compliance rule based reject by antispameurope Compliancefilter ID={rule ID} by {gateway}

The email has been rejected by the specified Compliance Filter rule of the specified host. The rule ID and the hostname of our gateway are displayed.
Blocked
554 5.6.9
Compliance rule based reject by Compliancefilter ID={rule ID} by {gateway}

The email has been rejected by the specified Compliance Filter rule of the specified host. The rule ID and the hostname of our gateway are displayed.
Blocked
554 5.7.0
Sender address rejected: {sender address} sending out spam

The email has been rejected because the sender distributed spam.
Blocked
554 5.7.1
domain / User unknown

The email has been rejected because the specified domain is not available in the Control Panel.
Blocked
554 5.7.2
Sender address rejected: Access denied

The email has been rejected because the sender’s IP address is not registered in our system.

554 5.7.10
encryption rule based rejected DANE required. {Gateway}

The email has been rejected because it was not encrypted with the required encryption method DANE. The hostname of our gateway is displayed.
Blocked
554 5.7.12
SPF fail by customer policy. {Gateway}

The email has been rejected because of an SPF fail according to a setting made by the customer. The hostname of our gateway is displayed.
Blocked
virus
 
Virus found (based on signature)
 
Virus
 
virus
 
Malware link, phishing or virus outbreak detected
 
Virus
 
admin-bl
 
Blacklist controlled by admin
 
Quarantined
 
ase-bl
 
Individual blacklist controlled by Support dep.
 
Quarantined
 
ase-recap1
 
Diffuse spam fingerprint
 
Quarantined
 
ase-rep1
 
IP reputation list1
 
Quarantined
 
ase-rep2
 
IP reputation list2
 
Quarantined
 
ase-rep4
 
URL / IP reputation list 4
 
Quarantined
 
bodytag
 
Spam signature in mail text
 
Quarantined
 
dirtyip
 
Reputation filter on IP basis
 
Quarantined
 
fingerprint
 
Re-captured spam mail by hash
 
Quarantined
 
header
 
Spam signature in mail header
 
Quarantined
 
link
 
Ads link
 
Quarantined
 
rbl50
 
pre-stage to 554 5.5.4 but not blocking yet
 
Quarantined
 
sameip
 
Signature recognition of spam engines
 
Quarantined
 
score
 
Dynamic contents evaluation
 
Quarantined
 
ScoreTag
 
Dynamic contents evaluation
 
Quarantined
 
spam
 
Reputation filter based on sender server
 
Quarantined
 
spamip-net
 
IP range of servers with poor reputation
 
Quarantined
 
spam-sum
 
Spam fingerprint
 
Quarantined
 
subjecttag
 
Spam signature in subject line
 
Quarantined
 
user-bl
 
Blacklist controlled by the user
 
Quarantined
 
wc
 
Spam pattern recognition
 
Quarantined
 
xarg
 
Bounce attack or individual customer rule
 
Quarantined
 
zombie
 
Botnet computer
 
Quarantined
 
content
 
Inadmissible attachment (content filter)
 
Content
 
admin-wl
 
Whitelist controlled by admin
 
Valid
 
asespf1
 
Known sender, type 1
 
Valid
 
asespf2
 
Known sender, type 2
 
Valid
 
ase-wl
 
Individual whitelist controlled by the support dep.
 
Valid
 
big2
 
Maximum mail size valid for spam check exceeded
 
Valid
 
bigmessage
 
Maximum mail size valid for spam check exceeded
 
Valid
 
body-wl
 
Whitelist signature in mail text, type 1
 
Valid
 
body-wl2
 
Whitelist signature in mail text, type 2
 
Valid
 
header-wl
 
Whitelist signature in header, type 1
 
Valid
 
header-wl2
 
Whitelist signature in header, type 2
 
Valid
 
knownsender
 
Sender address with positive reputation, type 1
 
Valid
 
noreason
 
Unevaluated mail
 
Valid
 
qsender2
 
Sender address with positive reputation, type 2
 
Valid
 
realbounce
 
Sent via bounce management
 
Valid
 
score
 
Dynamic contents evaluation
 
Valid
 
sender-ip
 
IP sender address has a positive reputation
 
Valid
 
subject-wl
 
Whitelist signature in subject line, type 1
 
Valid
 
subject-wl2
 
Whitelist signature in subject line, type 2
 
Valid
 
user-wl
 
Whitelist controlled by user
 
Valid
 
xarg-wl
 
Bounce mail or individual customer rule
 
Valid
cleanip-net
 
IP has not been flagged previously by system. IP has never been reported as sending spam
 
Valid
noreason
 
No positive characteristics within the email relating to any heuristics in the filters
 
Valid
asespf7-2
 
This reason code denotes that this customer has Advanced SPF Checking enabled and that this email failed the SPF Check
 
Valid