Feature Request – Comprehensive Mailbox Audit Log with Search, Table View and Self-Service Capabilities
Idea shared by Roger - 10/9/2025 at 12:04 PM
Under Consideration

Hello everyone,

Some years ago, I already wrote a detailed post about this topic, but unfortunately I couldn’t find it again right away — so here is a revised version of the request.

Our customers increasingly require an audit log for each mailbox that allows users to independently track sent and received messages directly in webmail.

Key information should include at least:

  • Sender and recipient address

  • Subject line

  • Date and time

  • Attachment information

  • Total mail size

To ensure maximum clarity and usability, the data should be displayed in a clean, tabular view. This allows mailbox owners and administrators to get a complete overview at a glance without having to open individual log entries. Columns should be sortable and filterable.

In addition, a powerful search and filtering function (by recipient, sender, subject, date range, attachment, etc.) would be extremely valuable.

For domain administrators, a centralized overview of all mailboxes with the same table-based search and filtering functions would be ideal, combined with role-based access control to ensure that only authorized persons can view the logs.

From an operational perspective, we run a multi-tenancy environment with many customers. Each time a customer asks when an email was sent, received, or possibly blocked, our team currently has to manually dig through server logs.
This is:

  • Very time-consuming,

  • Adds no real value for us as service providers, and

  • Can easily be delegated to the customer if appropriate tools are available.

A self-service, tabular audit log would:

  • Increase transparency for the end customer,

  • Reduce workload on our support team,

  • Accelerate troubleshooting,

  • Help companies comply with legal requirements (e.g., traceability, archiving, compliance), and

  • Significantly improve the overall customer experience.

Additional helpful enhancements could include:

  • Export function (CSV/Excel) for further analysis or compliance reporting

  • API access for integration into existing monitoring or ticketing systems

  • Role-based access control (e.g., mailbox owner vs. domain admin)

  • Optional logging of message delivery events (delivered, deferred, bounced, quarantined)

  • Retention policies configurable per tenant

I kindly ask you to review this request and consider implementing it in one of the upcoming releases.
I am convinced that many administrators and customers would highly appreciate this functionality.

Thank you very much for your time and support.

Hello everyone,

It seems to me that this suggestion is also being sanded down elsewhere in the community, and I would be very interested to hear what SmarterTools has to say about it. Is there a statement on this, or perhaps any plans that take this into account, or other views?

Thank you and best regards,
This would be a great feature. 
any updates or inputs from SmarterTools Team?
+1
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
we want this features as a part of MSP and muti tenancy  every customer ask to log  and audit search features by their own.
Please have this one 
It's a sad that the SmarterMail team hasn't reported it yet. May we hear your assessment?
+1
Zach Sylvester Replied
Employee Post

Hey everyone,

Thank you for the detailed feature request, I’ll get this added to our backlog.

I do have a question so we can better understand what’s needed:
The domain-level Message Archive already allows searching, sorting, and reviewing all sent/received messages for a domain. The main piece it does not include today is delivery status.

If we were to add delivery status information to Message Archive, would that fully satisfy the requirement?

Kind regards,

Zach Sylvester Software Developer SmarterTools Inc. www.smartertools.com

Hi Zach

Thank you for your quick reply and for adding the request to your backlog.

Regarding your question:
No — extending Message Archive would not fully satisfy the requirement.

Here’s why:

  • The solution must be independent of the Message Archive.
    In our environment (and in many others), the built-in archiving feature is not used because it does not meet certain compliance and operational requirements. In addition, it requires significant storage capacity, which makes it unsuitable and too costly for our setup.

  • We are looking for a lightweight, audit-focused logging view, completely separate from any archiving functionality.
    The goal is simply to track all inbound and outbound messages with their essential metadata (sender, recipient, subject, size, attachments, timestamps, etc.) — without actually storing or archiving the message contents.

This should be a self-service audit log, not tied to retention or storage requirements of the Archive module.

A standalone audit log would therefore:

  • Work for all customers, even those who do not use (or cannot use) the Message Archive

  • Avoid additional storage consumption

  • Provide an operationally efficient way to review mail flow activity

  • Support transparency, troubleshooting, and compliance without the overhead of full archiving

For these reasons, an enhancement to Message Archive alone would not meet the need — a separate audit log module is required.

Thank you again for considering this, and please let me know if you need any additional clarification.

Kind regards,
Roger

Zach Sylvester Replied
Employee Post

Hey Roger,

Thanks for the clarification. I’ve created the feature request and will update the status of this thread to Under Consideration.

Kind regards,

Zach Sylvester Software Developer SmarterTools Inc. www.smartertools.com
Hey zach,
This feature should be available for individuals domains 

Reply to Thread

Enter the verification text