Bounced Emails

Different mail servers classify bounces in very different ways. Some bounce reasons (such as "invalid domain" and "ambiguous address") represent problems that are unlikely to be resolved. These are called hard bounces. When a hard bounce for email occurs, Oracle Responsys updates all matching profile records (matching is based on email address) and sets the EMAIL_DELIVERABILITY_STATUS_ to U across all profile tables in the account. When EMAIL_DELIVERABILITY_STATUS_ has a U value in a recipient’s RIID_ records, then the recipient will not be targeted in email campaigns. Learn more about Profile List standard fields (system-defined).

If an email address has resulted in a hard bounce in the past, you can still use it create to new records or update existing records. However, if Oracle Responsys sends a message to the email address, it will still result in a hard bounce if the address is in the same state. Oracle Responsys does not parse old bounce records during the import of email address values.

Other bounce reasons (such as "mailbox full") represent problems that may be resolved in a relatively short time. These are called soft bounces.

Some mail servers react badly when they receive messages from senders who have already been notified of soft bounces for the same address. They may even refuse to accept all future messages from that sender.

To avoid being shut out by such mail servers, you should consider suppressing addresses for which several soft bounces have been recorded.

For example, if you contact a typical recipient three times a month, then you might consider suppressing an address that bounces 3 times in 30 days (or perhaps 4 times in 40 days), so the mail server at that address won't classify you as a "spammer."