Email Bouncebacks

Bouncebacks

Overview

The following guide will provide you information about bounceback messages. You or a person sending to you may have received a bounceback email. The bounceback message will give you clues on why the message bounced back and what you should do to rectify it.

Bounceback Error Messages

Error Message

Possible Reason

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:

 

The listed email addresses are either misspelled or no longer exists.

alias@domain.com.au

mailbox is full: retry timeout exceeded

 

The email you are sending to cannot accept any more data.

<alias@domain.com.au>:

Sorry. Although I’m listed as a best-preference MX or A for that host,

it isn’t in my control/locals file, so I don’t treat it as local. (#5.4.6)

 

There may be an issue with either the DNS setup or the port for the mail on that server is not working.

alias@domain.com.au

Technical details of permanent failure:

PERM_FAILURE: DNS Error: Domain name not found

 

This message is saying that the domain name “domain.com.au” does not exist. Make sure it is not misspelled.

alias@domain.com.au

Technical details of permanent failure:

PERM_FAILURE: SMTP Error (state 13): 553 sorry, mailbox unavailable (#4.7.1)

 

This mailbox may not exist — double check spelling. Or, this mailbox may exist but the pathway on the server needs to be re-established. It could also mean that the DNS is not set up properly.

<alias@domain.com.au>:

Connected to 168.144.68.96 but sender was rejected.

Remote host said: 553 sorry, your mailserver [131.103.218.112] is

rejected by See http://spamcop.net/

 

Your email is being rejected because it is being seen as spam. This message specifically shows spamcop is the spam company that blocked the IP address. The IP address could be the one provided to you by either the company that hosts the email, or your internet service provider.  You can tell who is being blocked by copying the IP address and doing an IP whois lookup:

In this example it is: 131.103.218.112

 

<alias@domain.com.au>:

209.18.68.11 does not like recipient.

Remote host said: 550-Rejected message because 131.103.218.80 is in a black list at 550 bl.spamcop.net Giving up on 209.18.68.11.

 

Your email is being rejected because it is being seen as spam.

This message specifically shows spamcop is the spam company that blocked the IP address

The IP address could be the one provided to you by either the company that hosts the email

Or your internet service provider providing the line you used to send the mail

You can tell who is being blocked by copying the IP address

In this example it is: 131.103.218.80 and doing an IP whois lookup

 

alias@domain.com.au

SMTP error from remote mail server after RCPT TO:<alias@domain.com.au>:

host 72.22.71.86 [72.22.71.86]: 553 sorry, that domain isn’t in my list of allowed rcpthosts (#5.7.1)

 

There could be 2 reasons for this.

  • The sender is not allowed to email this account. (spam filters, blacklisted IP address, recipient has wrong permissions for email files)
  • The command was aborted because the email address is invalid.

 

<alias@domain.com.au>:

The e-mail address could not be found. Perhaps the recipient moved to a different e-mail organization, or there was a mistake in the address. Check the address and try again.

<”host451″.”howtointernet.net” #5.1.0>

 

The email address is either misspelled, or does not exist.

alias@domain.com.au

Technical details of permanent failure:

PERM_FAILURE: SMTP Error (state 13): 553 sorry, that domain isn’t in my list of allowed rcpthosts (#5.7.1)

 

The sender is not allowed to email this account. The receiving email box may have the wrong permissions for email files, or sender is being blocked by a spam filter

alias@domain.com.au

SMTP error from remote mail server after RCPT TO:<alias@domain.com.au>:

host 74.220.202.27 [74.220.202.27]: 550-4.184.96.66.static.eigbox.net

(bosmailout04.yourhostingaccount.com)

550-[66.96.184.4] is currently not permitted to relay through this server.

550-Perhaps you have not logged into the pop/imap server in the last 30 minutes

550 or do not have SMTP Authentication turned on in your email client.

 

Relay not permitted through this server means that either SMTP relay has been disabled or requires authentication such as a password

Email may be suspended or permissions are set incorrectly. The sender’s system may have a blocked port.

If the email requires authentication, this can be corrected through your email client

 

alias@domain.com.au

Technical details of permanent failure:

PERM_FAILURE: SMTP Error (state 12): 550 bosauthsmtp11: Host

209.85.146.182: No unauthenticated relaying permitted

 

Relay not permitted through this server means that either SMTP relay has been disabled or requires authentication such as a password

The password is not authenticating or being recognized. The sender’s system may have a blocked port.

If the email requires authentication, this can be corrected through your email client

 

alias@domain.com.au

SMTP error from remote mail server after initial connection:

host gateway-f2.isp.att.net [207.115.11.16]: 550-66.96.185.8 blocked by

ldap:ou=rblmx,dc=bellsouth,dc=net

550 Blocked for abuse. See http://www.att.net/bls_rbl/ for information.

 

Your email is being rejected because it is being seen as spam.

This message specifically shows at&t is the company that blocked the IP address

The IP address could be the one provided to you by either the company that hosts the email or your internet service provider providing the line you used to send the mail

You can tell who is being blocked by copying the IP address

In this example it is: 66.96.185.8 and doing an IP whois

 

<alias@domain.com.au>:

Sorry, I wasn’t able to establish an SMTP connection. (#4.4.1)

I’m not going to try again; this message has been in the queue too long.

This usually means there is some delay on the server

It could be the sender’s server has a backed up mail system

Or the receiver’s server is taking too long to respond

 

alias@domain.com.au:

See /home/howtointernet/.maildata/users/help/TMDA_DELIVERY_FAILURE for traceback

I’m not going to try again; this message has been in the queue too long.

 

The message was waiting too long because of a delay on the server

The path shows that there is a log kept of failed messages and it shows the route it went through

 

alias@domain.com.au

Technical details of permanent failure:

PERM_FAILURE: SMTP Error (state 13): 550 5.1.1 <alias@domain.com.au> recipient rejected

 

The email was rejected by the recieving email system. Usually indicates a problem with the recipent’s email address

alias@domain.com.au

SMTP error from remote mail server after end of data:

host mx.tnbnazarene.org [66.96.140.51]: 552 5.7.0 Number of ‘Received:’ DATA

headers exceeds maximum permitted

 

The email went through too many different channels and is being rejected by the server it is being sent to.

Too many headers could indicate a spammer or an email spoofer trying to route through someone else’s mail system.

This can be caused if you are forwarding mail from one address to another or the person you sent mail to is forwarding their email to another address.

 

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Backing up a Website

So often we hear that people and business don’t have a recent copy of their website that they can...

Account Suspension

Account Suspension An account suspension will generally occur: When invoice payments have not...

Email Client Settings

Here is a simple way to find out your Email Client settings for Secure SSL/TLS and Non-SSL...

Disk Usage Warning critical

If you have your website and emails hosted with Insane Technologies and you have...

Email Client Setup - Outlook 2010

Overview This article will provide you with the steps to setup your email accounts within your...