A 554 email error is sometimes thought of as a catch-all of email errors. It is generally used when there is a generic delivery failure that another email error code doesn't directly define a problem for.

Some mail servers also use a 554 error even if there is a specific error code that defines what went wrong all ready.

You should receive a bounce-back message from the server with a variation of email error 554 in the subject, and the body should contain your original message that you attempted to deliver.

Example bounce-back message

Return-path: <>
Envelope-to: sender@YourDomain.com
Delivery-date: Sat, 13 Oct 2012 04:40:30 -0700
Received: from mailnull by biz32.inmotionhosting.com with local (Exim 4.77)
id 1TN050-0007it-Dw
for sender@YourDomain.com; Sat, 13 Oct 2012 04:40:30 -0700
X-Failed-Recipients: recipient@RemoteDomain.com
Auto-Submitted: auto-replied
From: Mail Delivery System <mailer-daemon@biz32.inmotionhosting.com>
To: sender@YourDomain.com
Subject: Mail delivery failed: returning message to sender
Message-Id: <e1tn050-0007it-dw@biz32.inmotionhosting.com>
Date: Sat, 13 Oct 2012 04:40:30 -0700

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
 
recipient@RemoteDomain.com
SMTP error from remote mail server after RCPT TO:<recipient@remotedomain.com>:
host mail.RemoteDomain.com [123.123.123.123]: 554 Invalid recipient
 
------ This is a copy of the message, including all the headers. ------
Return-path: <sender@yourdomain.com>
Received: from Admin by biz32.inmotionhosting.com with local (Exim 4.77)
(envelope-from <sender@yourdomain.com>)
id 1TN04y-0007iG-6d
for recipient@RemoteDomain.com; Sat, 13 Oct 2012 04:40:28 -0700
To: Recipient <recipient@remotedomain.com>
X-Autorespond: Comments
MIME-Version: 1.0
X-Loop: Recipient group <recipient@remotedomain.com>
Precedence: auto_reply
X-Precedence: auto_reply
From: "sender" <sender@yourdomain.com>
Subject: Auto Reply: Out of Office
Date: Sat, 13 Oct 2012 04:40:28 -0700

Common variations of the 554 email error

  • 554 5.7.0 Message Size Violation
  • 554 5.7.1 Message blocked due to spam content in the message
  • 554 5.7.1 [P4] Message blocked due to spam content in the message.
  • 554 5.7.1 <sender@yourdomain.com>: Relay access denied
  • 554 5.7.9 Message not accepted for policy reasons. See http://postmaster.yahoo.com/errors/postmaster-28.html

  • 554 RLY:B1
  • 554 delivery error: dd This user doesn't have a ymail.com account
  • 554 Denied (Mode: normal)
  • 554 Invalid recipient
  • 554 Malformed mail denied!
  • 554 Message is not RFC compliant; missing "Date" header
  • 554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit http://postmaster.yahoo.com/errors/postmaster-27.html [120]
  • 554 Message permanently rejected
  • 554 Message refused
  • 554 no valid recipients, bye
  • 554 rejected due to spam content
  • 554 rejected due to virus
  • 554 <sender@yourdomain.com>: Relay access denied
  • 554 Sorry, no mailbox here by that name.
  • 554 Spam detected
  • 554 Spam violation, the content of your e-mail contains illegal characters, re-sent after examination
  • 554 Transaction Failed Spam Message not queued.554 Virus found, message permanently rejected (#5.3.0)

Resolving a 554 email error bounceback

Because errors in the 554 series don't always bounceback for a common reason, they could be either a hard or soft bounce. To better understand soft and hard bounces, and general email bounceback errors you can read why does email bounce, bounceback, or error?

In our example bounce-back error above the reason the message has failed is because an auto-reply was trying to be sent to an account that didn't exist. So the RemoteDomain.com mail server responded back with a 554 Invalid recipient error.

Support Center Login


Social Media Login

Related Questions

Here are a few questions related to this article that our customers have asked:
Ooops! It looks like there are no questions about this page.
Would you like to ask a question about this page? If so, click the button below!
Ask a Question
n/a Points
2014-12-04 1:42 am

This message was created automatically by mail delivery software.A message that you sent could not be delivered to one or more of itsrecipients. This is a permanent error. The following address(es) failed:  rajeshwari@kmohan.com    SMTP error from remote mail server after initial connection:    host mx01.cloudzimail.com [115.112.214.41]: 554-secure.logix.in    554 IP blacklisted in http://www.senderbase.org------ This is a copy of the message, including all the headers. ------Return-path: <vivek@girirajpackaging.com>Received: from [122.166.231.165] (port=2124 helo=ashok)by usa1.my-linuxserver.com with smtp (Exim 4.82)(envelope-from <vivek@girirajpackaging.com>)id 1Xw9ZS-00021C-KA; Wed, 03 Dec 2014 18:31:57 +0530Message-ID: <000b01d00ef9$5e80f6a0$3501a8c0@ashok>From: "Vivek" <vivek@girirajpackaging.com>To: "Rajeshwari" <rajeshwari@kmohan.com>,"'GP'" <info@girirajpackaging.com>References: <00ff01d00ef8$fc7b4640$f571d2c0$@kmohan.com>Subject: Re: test mailDate: Wed, 3 Dec 2014 18:32:16 +0530MIME-Version: 1.0Content-Type: multipart/mixed;boundary="----=_NextPart_000_0007_01D00F27.770F3190"X-Priority: 3X-MSMail-Priority: NormalX-Mailer: Microsoft Outlook Express 6.00.2900.2180X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180This is a multi-part message in MIME format.------=_NextPart_000_0007_01D00F27.770F3190Content-Type: multipart/alternative;boundary="----=_NextPart_001_0008_01D00F27.770F3190"------=_NextPart_001_0008_01D00F27.770F3190Content-Type: text/plain;charset="iso-8859-1"Content-Transfer-Encoding: quoted-printableThanx & RegardsVivek R BiradarGiriraj Packaging98862 91023  ----- Original Message -----=20  From: Rajeshwari=20  To: 'GP' ; 'Vivek'=20  Sent: Wednesday, December 03, 2014 6:29 PM  Subject: test mail  =20  =20  =20  Best Regards  Rajeshwari.V  Ext#137  =20

Staff
25,329 Points
2014-12-04 11:31 am
Hello Vivek,

The message you provided indicates that the IP address of the server you are sending from is in a blacklist checked by the recipient. You will want to alert your mail provider to let them know their IP is in a blacklist so they can work to get it removed. You may want to provide them with the full bounceback message you provided here.

Kindest Regards,
Scott M
n/a Points
2014-12-12 11:22 am

Could you possibly find the issue here? We've been trying all morning and other emails that are not Yahoo can get through via respondin . But the bounce back isn't stating blocked that I can see. 

 

Sorry, we were unable to deliver your message to the following address.

 

<jbartolotta@artisandesigntampa.com>:

Remote host said:

554 Denied [4830b845.0.508071.00-2318.907745.p01c12m117.mxlogic.net] (Mode: normal)

[BODY]

 

--- Below this line is a copy of the message.

 

Received: from [127.0.0.1] by nm50.bullet.mail.gq1.yahoo.com with NNFMP; 12 Dec 2014 15:02:27 -0000

Received: from [98.137.12.59] by nm50.bullet.mail.gq1.yahoo.com with NNFMP; 12 Dec 2014 14:59:27 -0000

Received: from [98.139.215.142] by tm4.bullet.mail.gq1.yahoo.com with NNFMP; 12 Dec 2014 14:59:27 -0000

Received: from [98.139.212.243] by tm13.bullet.mail.bf1.yahoo.com with NNFMP; 12 Dec 2014 14:59:27 -0000

Received: from [127.0.0.1] by omp1052.mail.bf1.yahoo.com with NNFMP; 12 Dec 2014 14:59:27 -0000

X-Yahoo-Newman-Property: ymail-4

X-Yahoo-Newman-Id: 755260.88702.bm@omp1052.mail.bf1.yahoo.com

Received: (qmail 77117 invoked by uid 60001); 12 Dec 2014 14:59:27 -0000

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1418396367; bh=e4ZWpsgtCvRgSPnORIBtMaqHqrZy+IsoHVfyA1ZSKuA=; h=Message-ID:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=vD0bf86u/jGHBkxgtRlEFScNFY79DYXxFRCyeSndK6FLB4GzfSYt5UcYru6YVGuE0GVf55S9JCsE/ah0mgu/g81QGG1EUUnaAKNs9AyfnyJ0mnojFwXjsBZbwbJ03fk2te6+JU2IPiqXPpPwtAupqiA+LEgvLYyn4NTraxGlbEw=

X-YMail-OSG: 3FPByqQVM1n4I8ba6I0pGk4DSnaLcn.fGVG6eWGaAl7e4.R

JiQTPKTtx6YelLpC5gM78ZqziyZWzkECSX6GEW9uzgMxtnLCxZ1ulbMnt8Y6

RPUgL5XAfoHwiiuZrqsVrc1UoEY.rgHvdq94CNJUlUlQyHazLj1d15.oJcZ4

9tLUxNhH4UaGRYvnGsTxrUA6ad6_FDHGUtwh.b4m8Gq917Ywd5J3pepJfrMd

q3M.Bu4R0.UaX_ax0aW4dEZK6xNu6bmMe0LWBx2JQWpnUIzlzd3Hxpot9ynR

QiGYuz3FyfahHpakE9jh6c4m1aHVK1l8V7lv8q5sAI.vosEFi23sF20FCizE

Q9rLQMhpvo6.m9jzCsMdf.Z8RZ7nwD4WaUPcjp3pxWbnsawUA7Hak2tmd9tq

MUmtgELiZ5jbzfTYisFqE9Zx4h3CmCnG9qdrxChzXWZAbk1SFZV3jKFzHQbs

ccISp55XSewQfr98yQV7NSEIY5XT17hJ3T__YMAUIe8Rrh._QEmPp0L_tV8f

LRvt9cCJLDCii8enmjgSORDLfexeSBt_SUAJYpZYeIl6YG8xC2C5y4GykdcS

zFeng0REDqhWCTdR3mrC3wQq6rMS1xFZbP3WKcw1q9wYs6F1pMZxmopKG1xq

FeDgxreUHCsZtw7gCYWrQdqPlt7hR8JCzKLUljziBrwl07nbmGkUk.24JweJ

bJniLkuUACAzz_z8N5UbNzvs9x0KyF4UvUzGNPbro6Gj8Clsp3WSY

Received: from [172.56.1.177] by web141603.mail.bf1.yahoo.com via HTTP; Fri, 12 Dec 2014 06:59:27 PST

X-Rocket-MIMEInfo: 002.001,VHJ5aW5nIGFnYWluCgpTZW50IGZyb20gWWFob28gTWFpbCBvbiBBbmRyb2lkCgoBMAEBAQE-

X-Mailer: YahooMailAndroidMobile/4.7.2 YahooMailWebService/0.8.203.740

Message-ID: <1418396367.67956.YahooMailAndroidMobile@web141603.mail.bf1.yahoo.com>

Date: Fri, 12 Dec 2014 06:59:27 -0800

From: Jennifer Nicol <nicoljennifer3@yahoo.com>

Subject: Re: test 

To: Joseph Bartolotta <jbartolotta@artisandesigntampa.com>

In-Reply-To: <53268544A0AEAB4A9DB53DA2F54B44ADAB829A93@AIF-W2K11.artisan.local>

MIME-Version: 1.0

Content-Type: multipart/alternative; boundary="-221842591-1898802818-1418396367=:67956"

 

---221842591-1898802818-1418396367=:67956

Content-Type: text/plain; charset=us-ascii

 

Trying again

 

Sent from Yahoo Mail on Android

 

---221842591-1898802818-1418396367=:67956

Content-Type: text/html; charset=us-ascii

 

<table cellspacing="0" cellpadding="0" border="0"><tr><td valign="top"><p dir="ltr"><font size ="2"><font size ="2">Trying</font></font><font size ="2"><font size ="2"> </font></font><u><font size ="2"><font size ="2">again</font></font></u></p>

<p dir="ltr"><font size ="2"><font size ="2"><a href="https://overview.mail.yahoo.com/mobile/?.src=Android">Sent from Yahoo Mail on Android</a></font></font></p>

<table cellspacing="0" cellpadding="0" border="0"> <tbody> <tr> <td valign="top"> <div style="font-family:Roboto, sans-serif;color:#7e7d80;">From:"Joseph Bartolotta" <jbartolotta@artisandesigntampa.com><br/>Date:Fri, Dec 12, 2014 at 9:57 AM<br/>Subject:test <br/><br/></div> 

<div class="WordSection1">

<p class="MsoNormal">Try again</p> 

<p class="MsoNormal">  </p> 

<p class="MsoNormal">Thank You,</p> 

<p class="MsoNormal">Joe Bartolotta</p> 

<p class="MsoNormal">Artisan Design</p> 

<p class="MsoNormal">813-933-9245</p> 

<p class="MsoNormal">813-728-3020</p> 

<p class="MsoNormal"><a rel="nofollow" ymailto="mailto:joeb@artisandesigntampa.com" target="_blank" href="javascript:return">joeb@artisandesigntampa.com</a>

</p> 

<p class="MsoNormal">  </p> 

</div>

</td>  </tr>  </tbody>  </table></td></tr></table>

---221842591-1898802818-1418396367=:67956--

Staff
11,156 Points
2014-12-12 11:27 am
While Yahoo has not provided a specific reasoning as to why the email is blocked, it could potentially be due to a blacklist. If sent from an InMotion Hosting server, I recommend sending the bounceback within a ticket to technical support for further investigation.

Post a Comment

Name:
Email Address:
Phone Number:
Comment:
Submit

Please note: Your name and comment will be displayed, but we will not show your email address.

5 Questions & Comments

Post a comment

Back to first comment | top

Need more Help?

Search

Ask the Community!

Get help with your questions from our community of like-minded hosting users and InMotion Hosting Staff.

Current Customers

Chat: Click to Chat Now E-mail: support@InMotionHosting.com
Call: 888-321-HOST (4678) Ticket: Submit a Support Ticket

Not a Customer?

Get web hosting from a company that is here to help. Sign up today!