We’re pleased to provide an overview of new product updates that will go live on Monday, March 5. The main highlights are related to the global journal address and the automatic email scout reports features.
What’s new this week:
Global Journal Address
One of the features that the archiving product offers is the ability to ingest messages in Microsoft Exchange’s “journaling” format; this is used to ensure that messages that are sent within a domain are also added to the domain’s archive. A limitation of this functionality is that it requires that the domain’s MX records are set to the cluster – this would be the case if using the incoming filter but is less appealing for anyone wishing to use the archiving product without the incoming filter.
In this release, a new “global” journal address functionality has been added, that considerably simplifies using Exchange journaling with the archiving product. Each archived domain is assigned a unique mailbox in the cluster, specifically for ingesting journaled messages. An added advantage is that you no longer need to connect to the submission port (587) to add journaled outgoing messages and the delivery port (25) to add journaled incoming messages – the system will figure it out for you.
For example, the example.org domain might have the unique mailbox email@example.com. You can simply use this address when configuring journaling in Exchange, and the system will ensure that it’s journaled under the correct archiving domain.
To see the mailbox for a domain, simply go to the “Archive Status” page at the domain level. The system attempts to show a branded domain name if one is being used, and will otherwise default to the hostname of the cluster.
Automatic Email Scout Reports
The “Domain Settings” page includes a new option with this release: “Automatically Enable Daily Email Scout Reports”. When you enable this option, an Email Scout Report, which shows the messages that are quarantined, will be automatically added for each mailbox (when a message is successfully delivered to it).
You’re able to have one, two, or three reports sent each day, at times of your choice – the report will automatically cover the period since the previous report. For example, you might have an 8 am report covering all mail quarantined overnight, a 12 pm report for mail quarantined since 8 am, and then a 4 pm report for mail quarantined since midday.
More flexibility around the automatic reports, and how the reports look, will be available later in the year. More information about the current automatic report functionality is available in our article here.
Front-end / GUI:
Resolved: Issue with unbinding from ‘/api/admin/remove/’ wrongly assigning domain to super-admin instead of removing admin (#34573)
Resolved: Issue with email alias page being visible when features preview is enabled, on some clusters (#34566)
Resolved: Issue where in some situations the “use default” radio button would incorrectly show as unselected in the LDAP Mailbox Sync mapping tab (#34596)
Resolved: Issue with adding a new domain not setting the parent’s Protection Report template if no custom brand is set (#34595)
Resolved: Issue where the LDAP Mailbox Sync default settings could clash with one specific admin (#34585)
Resolved: Issue with inability to delete wildcard email address aliases (#34616)
Resolved: Issue with error being returned when editing entry on Sender Whitelist / Blacklist pages at super admin level (#34620)
Improved: The quarantine and queue pages now have ‘(preview)’ in their label only when the user is in preview mode ()
Added: A new global journal address system (#34067)
Added: The ability to set daily automatic Email Scout Reports (#34395)
In case there are items you would like to discuss in more detail, please contact support at support.solarwindsmsp.com