Spam email is tagged with the spam Internet header and allowed to pass through to end-user mailboxes. We recommend that you set up a filtering rule on individual user desktops so that spam is automatically moved to a separate folder. The filtering reduces the amount of spam in user inboxes and allows the users to review the spam email. The filtering works as a junk mail folder.

 

You may want to choose this option because:

·         Individual users want to control what is designated as spam.

·         Your organization's IT and end users want to work cooperatively to ensure that the antispam service fits the needs of the organization.

·         No loss guarantee for false positives at the enterprise IT level or the cloud infrastructure level; the responsibility lies with end users.

 

Spam email is tagged with the spam Internet header in the subject line with a word of your choice. The tagged spam email is then allowed to pass through to end-user mailboxes. We recommend that you set up a filtering rule on individual user desktops so that spam is automatically moved to a separate folder. This filtering reduces the amount of spam in user inboxes and allows the users to review the spam email. This filtering works as a junk mail folder.

 

You may want to choose this option because:

·         Individual users want to control what is designated as spam.

·         Your organization's IT and end users want to work cooperatively to ensure that the antispam service fits the needs of the organization.

·         No loss guarantee for false positives at the enterprise IT level or the cloud infrastructure level; the responsibility lies with end users.

 

Spam email is tagged with the spam Internet header and is redirected to a bulk mail address. (Your organization's IT administrator chooses the bulk email address.)

Some common alternatives for this option are as follows:

·         Set up the bulk email address as a public folder and grant all users access to the folder.

·         Set up a separate mailbox to which a maximum of three people have access (depending on the size of your organization).

 

You may want to choose this option because:

·         It reduces the junk email that end users would need to process on a daily basis.

·         It allows users to determine whether an email that is "missing" from an inbox is a true business necessity (newsletters, mailing lists, business correspondence, etc.).

·         Places the responsibility of spam control with the end user and spam filtering success at the enterprise level.

·         Ensures that allow-listing and block-listing become cooperative processes of communication among all levels of the organization.

·         Allows any valid emails or "false positives" to be recovered, given enough information from an end user.

 

Email that is identified as spam is discarded and does not reach your end users or network.

 

 

This option makes allow-listing marginally difficult because you cannot review the Internet header to verify that the "From:" address matches the "X-Env-Sender:"

 

You may want to choose this option because:

·         Your organization's usage policy declares a "no tolerance" stance for spam email. Legitimate senders have to resend failed email in another fashion.

·         Your organization's drive to reduce time and resources is dedicated to reviewing and releasing diverted email.

·         The costs that are associated with storage, processing, and the bandwidth that is related to storing diverted emails are eliminated.

·         Increased end-user productivity, which results from less spam email reaching end users.

 

Spam mail is held in the SpamManager quarantine. From there the mail can be viewed, released to the original recipient's inbox, or deleted. Depending on the deployment policy that you choose, individual users or other nominated individuals can handle the messages in Spam Manager. The emails in Spam Manager can be reviewed regularly or checked only occasionally for specific messages.

 

You may want to choose this option because:

·         Individual users want to control what is designated as spam.

·         Your organization's IT and end users want to work cooperatively to ensure that the antispam service fits the needs of the organization.

·         No loss guarantee for false positives at the enterprise IT level or the cloud infrastructure level; the responsibility lies with end users.

·         Suspected spam emails are all held in a single location to make it easy for users to manage.