Once an e-mail is rejected by a subscriber's email server, it's referred to as a bounce. There are distinct kinds of bounces that depend upon the cause the e-mail bounced. These info may be found in your marketing campaign report. It is an excellent idea to keep a close eye on your bounce numbers to make sure your campaigns are attaining your subscribers, and that you're abiding through spam legal guidelines.
A hard bounce shows a permanent cause an e-mail can't be delivered. In other words, a hard bounce is an email message that has been returned to the sender due to the fact the recipient's e-mail address is invalid. A hard bounce may occur because the domain name does not exist or due to the fact the recipient is unknown. In most instances, bounced e mail addresses are eliminated automatically and without delay from the active subscribers and placed in the cleaned portion of your list. Cleaned subscribers will be excluded from next marketing campaign sends to this list. Whilst there are numerous causes an e-mail address may hard bounce, below are a few commonplace reasons this may take place.
- Recipient e-mail address doesn't exist.
- Domain name doesn't exist.
- Recipient e-mail server has completely blocked delivery.
There are occasionally instances in which valid e-mail addresses can hard bounce or a subscriber may mistakenly unsubscribe and will need to opt back in in your list.
Soft bounces generally indicate a temporary delivery problem to an e-mail address and are treated in a different way than hard bounces. When an e-mail address soft bounces, it will immediately show as a soft bounce inside the campaign report.
If an e-mail address maintains to soft bounce in more campaigns, the e-mail address will finally be taken into consideration a hard bounce and cleaned from your email list. Whilst there are numerous reasons an e-mail address may soft bounce, below are some commonplace reasons this may occur.
- Mailbox is full (over quota).
- Recipient e-mail server is down or offline.
- E-mail message is just too large.
Here is a brief summary of this article: