The message security service detects spam by applying hundreds of rules to each message that passes through. It blocks obvious spam outright, and diverts what is possibly spam to the Quarantine. If you discover that some quarantined messages are actually good mail that just look like spam, add the senders of those messages to an appropriate approved-senders list. If a number of quarantined senders are from the same domain, such as the same company, add the domain to an appropriate approved-senders list. Messages from those senders are then delivered to user’s in your organization, regardless of the spam-like content.
To avoid the risk of increasing spam traffic, approve only specific senders whose messages might look like spam, rather than approving all of your known senders. Also, avoid approving too many domains, as that can increase the risk of spoofing. For more information see
Deciding Which Approved Senders to Add“.
Messages from individual senders or entire domains are delivered to user inboxes, regardless of spam-like content. Approved senders always circumvent junk email filters. However, if virus blocking is enabled for the recipient, the message security service does not deliver a message containing a virus, even if the sender is approved.
Messages sent to approved recipients or entire domains are delivered to user inboxes, regardless of spam-like content. Messages to approved recipients always circumvent junk-email filters. However, if virus blocking is enabled for the recipient, the message security service does not deliver a message containing a virus, even if the sender is approved.
Many mailing/email-list and newsgroup emails contain characteristics in common with spam. In fact, one person's opt-in mailing/email list can be perceived by another person as spam.
If you find mailing/email-list or newsgroup postings quarantined in the Message Center, add the mailing/email-list address to the approved-recipients list to prevent those messages from being quarantined.
The approved-recipients list evaluates the “To” and “Cc” fields on each message since mailing/email-list addresses are usually in these fields rather than the “From” field.
Never add a user to his or her own approved-recipients list. Since the list is based on the recipient of the email, this causes all mail to bypass filtering.
Messages from an approved domain are delivered to user inboxes, regardless of spam-like content. Messages from approved domains always circumvent junk email filters. However, if virus blocking is enabled for the recipient, the message security service does not deliver a message containing a virus, even if the domain is approved.
Messages sent to an approved mailing/email list are delivered to user inboxes, regardless of spam-like content. Messages from approved mailing lists always circumvent junk email filters. However, if virus blocking is enabled for the recipient, the email security service does not deliver a message containing a virus, even if the mailing/email list is approved.
Many mailing/email-list and newsgroup emails contain characteristics in common with spam. In fact, one person's opt-in mailing/email list can be perceived by another person as spam.
If you find mailing/email-list or newsgroup postings quarantined in the Message Center, add that list to the approved mailing/mail list to prevent the messages from being quarantined
The Approved Mailing list evaluates the “To” and “Cc” fields on each message — a mailing/email list most often place its address in those fields rather than the “From” field.
Never add yourself to your own Approved Mailing list. Since the Approved Mailing list is based on the recipient of the email, this causes all mail to bypass filtering.
If an organization has Industry Heuristics turned on, a message containing industry content coming from a Blocked Sender is still quarantined. The industry-specific content disposition is set after the Approved/Blocked Senders disposition is set and processed.
You may consider adding an address from user’s list to the appropriate organization-level list to improve filtering for all users, while freeing up space for that particular user.
An organization-level list applies to all users in that organization; entries in that list are not visible to users in the organization. A user-level list applies only to that user.
The user’s list takes precedence over the organization-level list. For example, if a sender is blocked at the org level but approved at the user level, then that sender’s messages bypass spam filters and are delivered to the user’s inbox.
Administrators access organization-level and user-level lists through the Administration Console. Users access their own lists through the Message Center.
The service identifies an approved or blocked sender by looking at the address in the message’s From field. First, it looks at the From address shown in the message header. If that is empty, it looks at the From address in the message’s Envelope (which is typically hidden from view in email clients).
When you include a domain in a sender list, any mail from that domain is approved or blocked according to the list in which it is included. Approving or blocking a domain affects all its subdomains, too. For example, if you approve jumboinc.com, then you also approve sales.jumboinc.com and marketing.jumboinc.com.
You cannot block a Top Level Domain (TLD) using the Blocked Senders list. A TLD is the right-most part of the address, after the last period. Examples of some common TLDs include
.com,
.edu,
.gov,
.net, and
.org (types of domains) and locales, such as
.uk,
.mx,
.jp,
.ie,
.ca. Instead, configure an IP range block on the TLD. For details, see
Manual IP Block Configuration.