|
View
Buyers
guide & |
|
Buyers Guide |
|
|
|
|
Compliance
Attender Delivers:
Journaling: a
robust journal of every message that has been sent or
received, replaces the inefficient Domino journal
mechanism Filtering: provides
administrators with a variety of message management
options to control: · Data
leakage of sensitive information outside the enterprise · Internal
SPAM (for example, restrict messages based on group
membership, recipient count, or total message size (the
space required to store all copies of the message) ·
The
enforcement of acceptable use policies Classification:
automatic classification (tagging) of messages based on a
user-defined dictionary of terms Disclaiming:
offers the ability to automatically attach sophisticated,
rule-based disclaimers to outgoing mail messages Analytics: statistics collection and reporting
|
|
FREE
White Papers |
|
|
Cross-Platform End-to-End Messaging
Transaction Analysis with OmniAnalyser
|
|
Instant Messaging Service Level Reporting using OmniAnalyser
|
|
Best Practices for Proactively Monitoring the
BlackBerry network.
|
|
IT Services Monitoring with OmniAnalyser
|
|
Advanced Reporting techniques to Optimize Exchange, &
Blackberry Performance & Availability
|
|
Robotic Testing to measure Messaging Services Quality from an End-User Perspective
|
|
You can't manage your email until you measure
it.
|
|
|
Compliance Attender provides the
ability to either prevent messages from being routed (filtering) or save a copy
of the messages (journaling), as they arrive within the mail.box on any Domino
server within your environment. You can configure Compliance Restrictions
(rules) to be generic for all mail accounts (any user/mail-in database) or you
can get very specific to only manage messages that have a specified value in the
sender or recipient, which allows you to focus your attention to a subset of
users.
There are currently two distinct, mutually exclusive functions that you can perform (more modules will be released in the near future) Filtering This prevents messages from being
released to the router if they are non-compliant with any Compliance
Restriction. For instance, you could configure a Compliance Restriction to
prevent the emails from being released to the router, if an invalid domain is
specified for the sender or any recipient. Another example is if a user is
sending a 10mb message to 1,000 recipients (internal), the overall delivery size
would be 10gb, which might use more space that you would desire one message to
consume. Methods such as a pattern matching
that of a Social Security Number or Credit Card provides you with the ability to
prevent an email from being routed if private information is included.
This restriction will prevent the routing of any message that has a sender or recipient to/from the ‘acme.com’ domain. However, if the email is sent internally and there are other recipients besides those with an ‘acme.com’ domain, all other recipients will receive the email, since the ‘Apply filter only to indicated recipients’. In addition to preventing messages
from being released to the router, you have the option to save a copy of each
non-compliant message within a Compliance Attender Graveyard database. This
information can be very useful when you need to determine the most common reason
for the filtering of messages. You can configure Compliance Attender to add all
messages into a single Compliance Attender Graveyard database or you can define
multiple Compliance Attender Graveyard databases, with each to hold a subset of
the messages. Journaling This will keep a copy of every
message, regardless if the message is inbound or outbound. This is vital when
you need to comply with a legal need that has been defined. For instance, you
could specify to journal a message if it either is sent from or sent to a
specific domain and/or recipient. You can also get content-specific, such as
journaling any message that contains specified words/phrases.
This restriction will journal all messages, regardless of
the message direction (inbound or outbound), into a single Compliance Attender
Journal database. Just like the Compliance Attender
Graveyard databases, you can specify where you want to store the journaled
messages. This could be one Compliance Attender Journal database for all
messages, or you could specify to add the journaled messages to different
journals, depending on your specified criteria. Legal implications are very prominent in today’s business world regarding the content of messages. Compliance Attender was created to allow you to ensure that the messages routing within your Domino infrastructure are compliant to your needs.
Sherpa Software LLP |
|
