For msgattr commands only.
<msgvar> represents the message attribute that you want to test. The following operators are supported:
Protected content values
Use these values to detect emails with protected content. Unlike most <msgvar> values, these take no comparison operator (such as > or <). They can be incorporated into complex commands to precisely target specific examples of emails with protected content.
This value returns True if an email is DRM-protected. or example:
msgattr WHERE isDRMProtected
Using this lookup value, CA DataMinder can detect DRM-protected emails that have been encrypted using Microsoft Windows Rights Management Services (RMS). RMS technology can be used to restrict the ways in which employees can use corporate emails, Word documents, and Web pages.
Note: DRM-protected emails cannot be detected by the CA DataMinder Notes endpoint agent or Domino server agent.
This value returns True if an email is digitally signed.
This allows you, for example, to block or warn against sending emails if they do not have a digital signature, but exempt them if they are digitally signed.
This value returns True if an email is encrypted.
This allows you, for example, to block or warn against sending emails if they are not encrypted, but exempt emails that are encrypted.
Message class values
This value returns the message class. This allows you to exclude specific categories of email such as meeting requests or read receipts. Common message classes that you can test for include:
This is the standard message class for Outlook emails. Nearly all Outlook emails have this messageclass. To avoid burdening the CMS database with unnecessary data, the message class is not stored when it is simply ‘IPM.Note’.
This is the message class for meeting requests. The corresponding classes for 'Accept', 'Decline' and 'Tentative' invitee responses are:
IPM.Schedule.Meeting.Resp.Pos
IPM.Schedule.Meeting.Resp.Neg
IPM.Schedule.Meeting.Resp.Tent
Task request.
Delivery receipt.
Read receipt.
Numeric values: size (KB), recipients, domains
Use these values in conjunction with <numericoperator> to detect emails with specific numeric attributes. For example, these values can count the number of recipients or calculate the total network impact (in terms of KBs of data sent).
Message size, including attachments (in kilobytes).
Note: This attribute is useful for blocking large emails. For example, preventing someone from sending a 5 MB email. The calculation methods used may not be accurate enough for blocking emails with a smaller impact.
For example, to detect all outgoing emails bigger than 5 MB:
msgattr WHERE msgsizekb > 5000
Total message impact (in kilobytes sent), calculated as:
Message size * No. of recipients
Note: This attribute is useful for blocking large emails. For example, preventing someone from sending a 5 MB email to 100 recipients. The calculation methods used may not be accurate enough for blocking emails with a smaller impact.
Number of recipients
Number of internal recipients.
Number of external recipients.
Number of 'To' recipients. For example:
msgattr WHERE tonum >= 10
Number of 'CC' recipients
Number of 'BCC' recipients
Number of 'To' and 'CC' recipients
Number of unique domains in recipient list.
Number of unique external domains in recipient list. This domain count is based only on external recipients; see the following section for details about external recipients.
Numeric values: for blank emails or missing attachments
These attributes can detect poorly written emails. For example, an email with a blank Subject field, no body text, or without a mandatory attachment.
Number of characters in the Subject line, excluding any leading or trailing spaces. . For example:
msgattr WHERE subjectlen = 0
Number of characters in the ‘normalized’ Subject line, excluding any leading or trailing spaces.
A ‘normalized’ Subject line is one where prefixes such as RE: and FW: have been removed.
Number of characters in the mail body text, excluding any leading or trailing spaces.
Number of attachments.
Numeric values: email importance, sensitivity and priority
Email applications such as Microsoft Outlook allow senders to assign importance and sensitivity to emails. Some applications, such as Lotus Notes, also allow senders to assign a delivery priority. These <msgvar> values allow you to test emails for these attributes.
These are numeric attributes, with zero representing the lowest level of significance. You can test for individual levels of significance or a range of significance.
Tests email importance levels, where:
0=Low
1=Normal (This is the default level.)
2=High
Tests email sensitivity, where:
0=None or not set. (This is the default level.)
1=Personal
2=Private
3=Confidential or Company-confidential
Tests email delivery priority, where:
0=Low or Non-urgent
1=Normal (This is the default level.)
2=High or Urgent
<who> variables: %sender% and %recipient%
In addition to the <msgvar> values listed above, you can also use <who> variables such as %sender% and %recipient% in msgattr lookup commands.
These allow you to combine standard message attribute test (for example, recipient counts or checking for protected-content) with tests for specific senders or recipients. for example:
msgattr WHERE isEncrypted AND %sender% IS "srimmel@unipraxis.com"
Note: Results from these string values depend on the expansion of the email, which in turn is determined by the machine policy setting Perform LDAP directory lookups? and the user policy setting Retrieve Full Recipient/Sender details.
|
Copyright © 2014 CA.
All rights reserved.
|
|