Email Bounces Troubleshooting

It is not uncommon for your FeedsyList to generate soft and hard bounces over time.

Soft bounces 

These can occur when the recipient's mailbox is full; the receiving server is down or swamped with messages; the message size is too large; the recipient's settings do not allow for email from the sender; suspicious or spammy content has been detected, and many more reasons.

It does not necessarily mean the email address is invalid or no longer active.

So these subscribers remain in your Active folder and whilst we may have stopped trying to deliver your last email, we will try to send the next one to these addresses.

Hard bounces

These can be found in the Bounced folder and the most common cause is the email address being no longer in use.

However, sometimes the bounced receivers email server may have blocked bulk emails from this email address because it deems the email as spam or suspicious.

This is more likely to happen when generic sending office email addresses (eg beginning with admin@ or office@, etc) are used.

There are 3 ways to improve the chances of avoiding soft or hard bounces

  1. Add the email address to contacts
  2. Verifying the domain name
  3. Whitelisting the sending servers

1. Ask them to add your email address to their address book

  1. This is best for individual subscribers experiencing difficulties receiving your emails.
  2. Ask these subscribers to add your sending email address to the contacts list (or address book) linked to their email browser software.
  3. Ask these subscribers to look for your emails in their JUNK, SPAM or PROMO folders and to change their status to NOT JUNK.
  4. We suggest sending your Bounced subscribers an email (sent from the same email address you send your newsletter from)

SUBJECT: Can you please help me [1 minute]

MESSAGE: Hi there.

We have been trying to send you some important information in our monthly newsletters but have noticed your email address is showing as bounced.

(a) If your email address has changed recently can you please reply with your new updated email address so we can update our records.
(b) If your email address is still OK then our newsletter is likely to be going to your SPAM or JUNK folder.

Can you please try two things:

(1) have a quick look for it and mark it as NOT JUNK/SPAM and
(2) add my email address to your computer's Contacts (or Address Book) so it better trusts it when receiving our newsletter (and then reply to let us know you have done so).

Thank you so much for your time.

2. Verifying the domain name

  1. Verifying your domain name for the email address you send your Feedsy emails and is entirely optional but it can increase the chances of your emails landing in people's inboxes (and not being filtered as SPAM). For more info.
  2. If you wish to do this then please email support@feedsy.infoand request us to be send some info to give to your IT person:
    1. It will be simple instructions to add a TXT record into the DNS (it's easy and will take a few minutes).

3. Whitelisting the sending servers

  1. OK, this is pretty full-on and is only very rarely needed when receivers from the same location/server cannot receive emails.
  2. This is the job for a system administrator.
  3. Below are the addresses you can whitelist if you're having trouble delivering email from Feedsy software to your own network. Depending on your situation, you can whitelist sending domains or IP addresses.
  4. Return-path sending domains
    1. Instead of whitelisting all of our sending IP addresses, you can whitelist our domains. They currently include through to
  5. Authenticated domains
    1. If you have set up authentication, you will also want to whitelist the domain you have authenticated. Subdomains can be authenticated, if your mail administrator would like to limit access further.
  6. Sending IP addresses
    1. Below are the IP ranges we use for sending email:
  7. In cases where you need to whitelist IPs to receive email from our servers, we recommend mail administrators set up custom rules within their email filtering software. To work, the rule must match both of these conditions:
    1. The email is coming from one of our IPs or sending domains ( through
    2. The email contains your domain in the "From" address.
    3. Any email that doesn't match one of these conditions can be rejected. A custom rule like this is generally an acceptable solution for security teams and mail administrators.

Did you find it helpful? Yes No

Can you please tell us how we can improve this article?