When issues do occur, our engineers work as quickly as possible to resolve them, and as release information become available, it will be added to this document.
Following the known issues in the current release. Each issue includes a tracking number, brief description, and workaround (if applicable).
|
When you delete a user via the Administration Console, that user is considered deactivated for a period of time equal to its quarantine period (for example, 14 days). While the user is considered deactivated, you can add the user back to the service. If you have Message Discovery, then all messages for that user (before and after deactivation, and including quarantined messages) are available in the same Personal Archive.
|
If you add back a user during the deactivation period, specify the org to which you are adding the user. Specifying the org lets you avoid errors associated with the user’s original org no longer existing or with the user’s original domain having been moved to another org.
|
|
If you delete a user via a batch command and do not use the purge argument, you cannot subsequently purge that same user. To purge a user under these circumstances, you need to add back that user, and then delete it with the purge argument.
|
Notifications: Quarantined outbound messages with multiple recipients are sometimes delivered to only one recipient [1087256]
Issue: When an outbound message sent to multiple recipients is redirected to an administrator’s quarantine and then later delivered by that administrator, the message is sometimes delivered to the wrong user. Some users will not receive their quarantined message, while other users receive multiple copies.
Attachment Manager: Scanning of compressed files must be set for all recipients [2193576]
Issue: If the first recipient in a multiple-recipient message has the Attachment Manager org setting “Scan inside compressed file types” turned off, then Attachment Manager does not scan inside compressed file attachments for the rest of the recipients, regardless of whether their org is set to “Scan inside compressed file types.”
Workaround: For all user orgs, turn on Attachment Manager and turn on the "Scan inside compressed file types" setting. You do not need to enable Attachment Manager filters for all orgs.
Attachment Manager: Microsoft Office 2007 Word (.docx) and PowerPoint (.pptx) files are incorrectly identified as ZIP files [1542203]
|
2.
|
Click Filters.
|
|
3.
|
Issue: Attachment Manager may incorrectly identify some .csv files which are saved as .zip files, as .exe files.
Issue: In some cases, messages continue to spool when a mail server comes back online, and messages are not unspooled.
|
2.
|
Set Spooling Mechanism to Suspend, set Unspooling Control to Automatic, and click Submit.
|
This action stops the spooling process for the online server and initiates the unspooling process.
Delivery Manager: Inaccurate data displayed when a system is running in continuation mode [1465268]
Issue: When a system is running in continuation mode, the Administration Console cannot access mail traffic data from the secondary data center, but can access connection limit data. In this case, the Status value for the mail server can indicate that the mail server is busy, while the Delivery Manager graph incorrectly indicates that no mail is flowing.
Content Manager: Filter Name reports list extra data when multiple Content Manager dispositions are triggered for a single message [1408150]
Issue: When a single message triggers multiple Content Manager dispositions, each disposition is counted as a separate message, which in turn inflates the data in the report.
Issue: It is possible to create an org whose parent is an account org rather than an email config, and to then add a domain and users to that org. Because that org does not have an email config above it in the hierarchy, users in that org do not receive mail.
Workaround: Make sure any org you create for a domain and users has an email config above it in the hierarchy.
Issue: The number of archived messages indicated in the "Inbound Archiving by Domain" report is lower than the actual number of archived messages. Depending on the number of dispositions applied to a message, the archiving disposition can appear earlier or later in the sequence of dispositions listed for that message. Depending on its location in that sequence, the archiving disposition is sometimes not counted by the report.
Message Archiving: Cannot use IP address for host name when exporting via Secure FTP [1863340]
Issue: When you use Secure FTP to export search results that are contained in an MBOX or PST file, you cannot enter the IP address of the FTP server to which you want to transfer your file.
Issue: If you try to display the contents of a very large message (for example, in excess of 100 MB) from your search results, the message fails to open on the first few attempts, and you see a “Connection Interrupted” error.
Workaround: Continue to click the subject link to open the message until the message opens (usually after three or four attempts).
Issue: If you save search results and specify a hold-until date, that date is not displayed on the search results page until you refresh the page.
Message Archiving: If you attempt to purge messages to which a user hold has been applied, you see a “No records found” message [1385224]
Issue: If you attempt to purge messages to which a user hold has been applied, you see a “No records found” message, which can be misleading. If you refresh your browser, you see the correct count and size for messages on hold for that month.
Message Archiving: The Purge Messages page on the Retention tab indicates that messages on hold are available to purge [1348082]
Issue: The Purge Messages page on the Retention tab indicates that messages on hold are available to purge. Messages on hold are included in the Total Count and Total Size columns for each related month, implying that these messages may be purged. Despite the implication, if you click Purge, the messages on hold are not deleted from the archive.
Message Archiving: The “Graph data not available” message is displayed on pages that never contain graph data [1324020]
Issue: The “Graph data not available” message is sometimes displayed on pages that never contain graph data.
Message Archiving: If you use Internet Explorer 6.0.2900, you can specify a hold-until date that has already passed [1320796]
Issue: If you use Internet Explorer 6.0.2900 to view the Message Archiving interface, you can save search results with a past value for the “Hold until specific date” option.
Message Archiving: Entering special characters as search criteria returns odd error message [1087930]
Issue: When you enter special characters (e.g., $, %, or @), as search criteria, an odd error message is returned.
Message Archiving: Searching for user names that include special characters returns no results [1087793]
Issue: If you enter special characters to search for registered users in the system whose names include special characters, no results are returned. For example, if you enter @ in the Find field to search for a user whose name includes the @ character, no results are returned.
Issue: If you enter a name that contains too many characters for a new investigation, saved search criteria, or saved search results, UI elements become misaligned.
Message Archiving: The Find Related Subjects search fails under some circumstances [1087579]
Issue: When you are viewing the contents of a message and run the Find Related Subjects search, the search can fail if the subject line contains special characters.
Message Archiving: Audit reports for purge events contain wrong date for rearchived data [1087572]
Issue: If you run an audit report that includes Purge Events, any of those events that occurred for rearchived data are listed with the wrong month. The month listed is one month after the event (for example, if the purge event happened in January, then the event is listed in the report as having happened in February). All other data for the event is correct.
Message Archiving: In archived journal reports from Exchange 2007 there is an extra From field [1087568]
Issue: When you use Message Archiving to view the message contents of an archived journal report from Exchange 2007, you see an extra From field.
Message Archiving: On the Investigation Summary page, wrong error messages are displayed for View Messages and Delete buttons [1087553]
Issue: On the Investigation Summary page, if you click View Messages or Delete without selecting a set of search results, you see the same error message that is displayed for the Edit button under those circumstances: Please select the search results to edit.
Message Archiving: If you are displaying the Administration Console in Internet Explorer 6, you may not be able to activate Message Archiving [1087552]
Issue: The interface elements necessary to configure Message Archiving from the Management Console may not be properly displayed when you use Internet Explorer 6.0.2900 SP2. When this occurs, you cannot use those elements to configure archiving.
Workaround: You can use IE 7 or Firefox.
|
|
|
|
|
