Here is a list of issues that were fixed in this release - build 2.6.33.

Issue Key Description

AVSUPPORT-45531, AVSUPPORT-45462

Issue with periodic reports loading caused the page to be loaded endlessly and never display.

AVSUPPORT-45359

Full scan did not finish for some customers, was stuck on "starting" dashboard status. No emails scanned, but rules and connectors seemed to be generated correctly.

AVSUPPORT-45243, AVSUPPORT-45231

For some customers inbound emails directed to an M365 email alias address were not delivered.

AVSUPPORT-44826

Clicking on Lastline events resulted in endlessly loading events page in the new portal.

AVSUPPORT-44297, AVSUPPORT-44952, AVSUPPORT-45359, AVSUPPORT-44828

Customers got an error saying that the mailbox does not exist when trying to set dedicated quarantine mailbox verification in M365 mail. This caused due to a change in M365, additional permissions are now required to perform the operation.

AVSUPPORT-43882, AVSUPPORT-44069

In numerous cases, not all M365 email copies were quarantined manually. This was caused due to internal system load that caused delay in quarantine actions.

AVSUPPORT-44447

"Show body from raw email" did not show the email body for Gmail.

AVSUPPORT-43073

A customer experienced that the Exchange client only sees one active user. 

AVSUPPORT-42748

 

A customer did not see any Gmail policy groups. This was caused to a rapid engine stop + start, which resulted in a partial cleanup.

AVSUPPORT-42227

A customer failed to manually move an email to the spam folder. The spam actions and workflow were fixed accordingly.

AVSUPPORT-40875, AVSUPPORT-42529, AVSUPPORT-41794, AVSUPPORT-41895, AVSUPPORT-42375, AVSUPPORT-42701,
AVSUPPORT-38895

A few customers reported missing emails on their portal. The issue happened in emails where the first recipient in the envelope recipients list was not a valid recipient (i.e. user does not exist).

AVSUPPORT-31934

Multiple DLP alerts were generated for the same email, one for each attachment.

AVSUPPORT-30441

The security tool exception action was missing for DLP events in the events page.