D
Discover mailboxes
Scan the local mail environment and present mailbox candidates for confirmation before activation.
For corporate and government rollouts, SIP Shield provides a Linux-first server package path that runs on the client’s own infrastructure. The reference flow already works on Ubuntu 24.04 with Webuzo, Exim, and Dovecot: discover local mailboxes, confirm the protected set, then keep spoofing, phishing, scams, impersonation attempts, and uncertain messages outside the trusted inbox path until they are reviewed.
The server deployment is designed to stay practical for IT while acting as a trust-control layer for end users.
Scan the local mail environment and present mailbox candidates for confirmation before activation.
Check inbound mail upstream for phishing, spoofing, fraud indicators, and unsafe attachments before people treat it as routine mail.
When the system is not confident enough to deliver or reject, keep the message out of the inbox and quarantine it instead.
Notify the intended user and offer a one-time-use review page that explains why the message was held instead of forcing that user into a full admin dashboard.
Enterprise and government customers can now keep a monthly report trail of flagged messages tied to the Customer ID email only, so the organization has one central audit copy with CSV export instead of sending summaries to every mailbox user.
See how many messages were flagged, how many mailboxes were affected, and what sender or category patterns repeated during the month.
When the Linux agent posts message-level events, the portal can show the actual flagged rows for the month instead of only aggregate counters.
The monthly report page can export the same data as CSV for internal filing, procurement, compliance, or audit handoff.
The scheduled report goes only to the customer account email on file, keeping reporting centralized at the organization level.
The current server release is no longer just a concept page. The reference Linux flow has already been exercised end to end on a live Ubuntu VPS.
The Linux agent can discover local mailboxes from the active mail environment and report them back to the customer portal for confirmation.
Inbound mail is routed through SIP Shield before normal mailbox delivery, so suspicious messages can be held upstream.
If a message is held, the intended recipient receives a separate notice instead of the risky message itself.
The recipient can open a one-time review link, inspect the held message summary, and choose release or delete.
The rollout should not force the customer to hand over mailbox passwords to us or maintain a complicated control plane.
The organization can still use a normal SIP Shield portal login instead of learning a separate admin system.
If more mailboxes are discovered than licensed, the IT team can remove extras and proceed with the approved set.
Licensing is based on protected mailbox count, not on how many administrators or devices happen to view the portal.
Mailbox credentials and mail content remain on the organization’s server wherever possible.
SIP Shield keeps one main Linux package and adapts deployment using compatibility profiles, so the product stays simple while still recognizing different Linux families and mail environments.
Ubuntu and Debian are the strongest starting point and the clearest documented rollout path.
AlmaLinux, Rocky, and other RHEL-family systems can use the same package with light environment adjustments.
The installer writes an install profile showing distro family, package manager, service manager, control panel markers, and mail stack markers.
There is no need to maintain separate customer products for Ubuntu, Debian, AlmaLinux, or Rocky if the compatibility profile is clear.
The rollout starts with Linux because that is the cleanest first environment for self-hosted mail protection.
First target for self-hosted mail environments and the current tested reference path on Ubuntu 24.04 with Exim + Dovecot.
Planned option for organizations standardized on Microsoft server infrastructure.
Future path for private cloud deployments where SIP Shield can still run before staff inbox delivery, using the same licensing and mailbox-confirmation model.
Use server-side protection for the organization while preserving desktop tools where they still make sense.