A little bit of background: Every time you see a bounce*@ email address is the last time you will see that address. These disposable, script generated addresses are only valid for a short period of time and are used by the mailing list companies to track bouncebacks and replies to their campaigns. On is generated for every single email sent out and if you look closely at them they usually have a random string or your email encoded in the user part of the email address. Whitelisting them, as so many people often try, is to put it simply: pointless. Naturally when the next email comes in from \u201cthe same sender\u201d<\/em> it\u2019s going to have a completely different from address and the old whitelist entry will not fire. This tends to get really annoying really fast for clients that don\u2019t understand what is going on behind the scenes.<\/p>\n<\/blockquote>\n To make things easier and assure delivery in the future, ExchangeDefender will now detect when you\u2019re attempting to whitelist a bounce\/disposable address and offer to whitelist the entire domain for you. We\u2019ve stripped out the product branding so you can forward this to your clients or include in your own documentation\/newsletter. When they click on a Trust link in an email report they will see this prompt:<\/p>\n And if they go through our online portal and attempt to whitelist a temporary bounce email, they will see this:<\/p>\n Is that all? Well, not quite. You see, most of these bounce lists are coming from legitimate sources such as Constant Contact, MailChimp, SalesForce, etc. Later this fall we will be releasing a new \u201cNewsletter\u201d feature but in the meantime our new managed whitelist (enterprise-wide) will make sure these bounce messages getting caught in SPAM folders due to their contents (but from legitimate sources) are no longer something your clients have to worry about fishing out. So yay, less work for everyone involved!<\/p>\n One more thing<\/strong><\/p>\n While we\u2019re on the \u201cless work\u201d<\/em> train, infections and filename\/filetype policy violations will no longer involve going through our team to release messages. You can now release infected or policy violating attachments\/messages on your own through the Domain login at https:\/\/admin.exchangedefender.com<\/a>. (psst. You can even let your clients \/ CIO types access this since it\u2019s a domain-level feature, not an MSP-level feature<\/em>)<\/p>\n![\"TrustedSender\"](\"http:\/\/www.exchangedefender.com\/blog\/wp-content\/uploads\/2017\/10\/TrustedSender.jpg\" "\\"TrustedSender\\"")
<\/a><\/p>\n<\/a><\/p>\n