Skip to content

Cookie settings

Choose which kinds of cookies you allow. You can change your choice at any time via Cookie settings at the bottom of every page. Privacy statement

Necessary

Always on

Needed to log in, keep your cart and remember your choices. These are always on.

Which cookies?
  • weboke_sessie, weboke_klant, weboke_remember: your session and staying logged in
  • weboke_basket: your cart
  • wkBtwIncl: showing prices with or without VAT
  • wok_cookies: your cookie choice, 12 months

Measures which ad leads to a visit or order, so we do not pay for ads that do nothing.

Which cookies?
  • Google Ads via Google Tag Manager (_gcl_au, _gcl_aw), up to 90 days
  • OpenAI Ads, ads in ChatGPT
  • wok_aff: which partner referred you to us (affiliate programme), 60 days

4.6

Country and language

Each country has its own site, with prices and VAT for that country.

View

Mail delivery failed: how to read the error message and what the codes mean

Did you get an email back with the subject Mail delivery failed: returning message to sender, Undelivered Mail Returned to Sender or Delivery Status Notification (Failure)? Then your email didn't arrive. An error message like this is called a bounce. It comes from Mailer-Daemon or Mail Delivery System and almost always tells you what went wrong. Here's how to read it.

How to read a bounce

peter@example.net
  host mx1.example.net [198.51.100.20]
  SMTP error from remote mail server after RCPT TO:<peter@example.net>:
  550 5.1.1 <peter@example.net>: Recipient address rejected: User unknown
  • Which address did it fail for? If there are multiple recipients, the error only applies to this address.
  • Who is reporting it? If it says SMTP error from remote mail server, the recipient's server (after host) refused the email. If it doesn't say that, our own server gave up, for example because of a limit.
  • The code and the text after it: that's where you'll find the reason.

In the technical part below it, look at Remote-MTA (the server that refused) and Diagnostic-Code (its literal response). At the very bottom you'll find the headers of your original email: there you can see which sender address and which server were used.

Temporary or permanent: the 4/5 rule

  • If the code starts with a 5 (550, 5.7.1), the email has been permanently refused. Sending it again only helps once the cause has been fixed.
  • If the code starts with a 4 (451, 4.7.500), it's temporary and our server will retry on its own. If you get a delay notice with Action: delayed, don't send the email again, otherwise it may arrive twice.

The second number tells you where the problem is: x.1 the address, x.2 the mailbox, x.3 the mail system, x.4 the connection, x.7 security and policy.

The most common codes

Code or messageMeaningWho needs to act?
550 5.1.1 User unknown, Recipient address rejectedThe address doesn't exist.You: check the spelling.
452 4.2.2 or 552 5.2.2 Mailbox full, Quota exceededThe recipient's mailbox is full.The recipient.
552 5.3.4 Message too bigThe message is too large. With us, a message can be up to 50 MB, including attachments. That's about 36 MB of attachments.You: share large files via a link, see Email rejected: message too big.
550 5.7.1 Relaying deniedYour email program isn't logging in to the outgoing server.You: turn on authentication, see I can't send email (receiving works fine).
451 Daily send limit of 300 emails for account '...' is reached, message limit reachedOur daily limit has been reached: by default 300 emails per package per day, lower for some packages.You: wait until tomorrow. If you hardly send any email yourself, your mailbox may have been misused. See Limit for sending email.
550 5.7.1 with a different textThe recipient refuses the email based on their own policy, such as spam. The text says why.Depends on the text.
550 5.7.26 (Gmail), 550 5.7.509 (Microsoft), SPF check failed, DMARC check failedSPF, DKIM or DMARC isn't set up correctly for your domain.You: set them up correctly, also for services that send email on your behalf. See What is DMARC? Explained in plain language.
550 5.7.25 (Gmail)The sending server doesn't have a valid reverse DNS (PTR).The server administrator: us for a hosting package, you for a VPS (Sending email from your VPS and setting up reverse DNS).
421 4.7.28 or 550 5.7.28 (Gmail), unusual rateAn unusually large amount of (unwanted) email from this IP address.The server administrator. If you send a lot of email at once yourself, use a newsletter service.
451 4.7.500 (Microsoft), Server busyMicrosoft is temporarily throttling the IP address of the sending server.Nobody right away: the server will try again.
550 5.7.606 (Microsoft), banned sending IPMicrosoft has blocked the IP address of the sending server.The server administrator. For our servers: send us the bounce.
550 5.7.708 (Microsoft)You send via Microsoft 365 and Microsoft no longer accepts traffic from that environment.The administrator of your Microsoft 365, via Microsoft support.
550 5.7.515 (Microsoft)You send a lot of email to Outlook.com without passing SPF and DKIM, or without DMARC.You: set up SPF, DKIM and DMARC correctly.
554 IP=... - None/bad reputation (NOWL) (T-Online)T-Online doesn't accept email from this IP address.The server administrator. Send us the bounce.
421 Service not available, Too many connectionsThe receiving server isn't accepting email right now.Nobody: our server will try again later.
blocked using, listed at, SpamhausAn IP address is on a blacklist.See Sending refused: blacklists and limits.

You can read more about Microsoft and T-Online in Email to Outlook, Hotmail or T-Online delayed or refused. If your code isn't listed, look it up with the party that returned it, such as Gmail or Microsoft.

Getting exactly the message 550 5.5.0 Requested action not taken: mailbox unavailable? Read what it means and what to do about it in Error message: 550 5.5.0 Requested action not taken: mailbox unavailable.

Bounces for email you didn't send

Suddenly getting bounces for email you never sent? Then look at the original email at the bottom. If your address is listed as the sender, but with a text and server you don't recognize, a spammer has forged your address and the bounces are coming back to you. This is called backscatter. That doesn't necessarily mean your mailbox has been hacked. A DMARC record helps recipients refuse forged email like this, see What is DMARC? Explained in plain language. To be safe, check your Sent folder and Email Tracking to make sure nothing was sent from your own mailbox. If in doubt, read What to do if your email address has been misused.

No bounce, but your email still isn't arriving? Look it up with Email Tracking in DirectAdmin, see Checking whether an email has arrived with Email Tracking and My email isn't arriving or ends up in spam: how to figure it out.

Still stuck? Create a ticket via the Support Center with the full bounce, the recipient's address and the time. Then we can look up the email right away.

See also in the DirectAdmin manual: Sending refused: blacklists and limits.

Detailed explanation with screenshots: I can't send email in the DirectAdmin manual.

Want to learn more? Take the free course Email in order, lesson 6.1 Reading a bounce and lesson 6.2 Common error codes explained.

Was this article helpful?

← Back to Email

One moment…

Set up your domains

For each domain, arrange the nameservers, the link to your hosting and who becomes the owner.

Loading your domains…