Protect the organization before risky email becomes a human mistake.
SIP Shield provides a Linux-first server package path for corporate and government rollouts that runs on the client’s own infrastructure. It can discover local mailboxes, confirm the protected set, and keep spoofing, phishing, scams, impersonation, and uncertain mail outside the trusted inbox path until users review it safely.
One controlled layer instead of one app per workstation.
The server path is designed for organizations that want trust control upstream, mailbox-based licensing, and safer user review without turning everything into a full administrator workflow.
SIP Shield server deployment is built for environments where email protection should happen before messages reach the normal inbox flow. That means suspicious or uncertain messages can be quarantined upstream instead of looking routine to staff.
It also keeps rollout practical for IT teams: licensing is based on protected mailbox count, review links can go directly to the affected user, and the client can still use a normal SIP Shield portal login instead of learning a separate control plane.
Built to stay practical for IT while protecting end-user trust decisions.
The server app is designed to discover the environment, intercept risky mail upstream, and offer safer review paths for the intended recipient.
Discover mailboxes
Scan the local mail environment and present mailbox candidates for confirmation before activation.
Control trust before inbox
Check inbound mail upstream for phishing, spoofing, fraud indicators, and unsafe attachments before people treat it as routine.
Quarantine uncertainty
When the system is not confident enough to deliver or reject, keep the message out of the inbox and quarantine it instead.
Explainable review links
Notify the intended user with a one-time-use review page that explains why the message was held.
Centralized monthly visibility without broadcasting summaries to every user.
Enterprise and government customers can keep a monthly report trail tied to the Customer ID email only, with CSV export available for filing, compliance, and audit handoff.
Monthly totals
See how many messages were flagged, how many mailboxes were affected, and what sender or category patterns repeated during the month.
Detailed rows
When the Linux agent posts message-level events, the portal can show the actual flagged rows instead of only aggregate counters.
CSV download
Export the same monthly data as CSV for procurement, compliance, internal filing, or audit review.
Customer-ID delivery
The scheduled report goes only to the customer account email on file, keeping reporting centralized at organization level.
The reference Linux path is already exercised end to end.
The current server release is presented as a working reference flow rather than only a concept page.
Mailbox discovery
The Linux agent discovers local mailboxes from the active environment and reports them back for confirmation.
Pre-inbox interception
Inbound mail is routed through SIP Shield before normal mailbox delivery so suspicious messages can be held upstream.
Quarantine notice
If a message is held, the intended recipient receives a separate notice instead of the risky message itself.
One-time review
The recipient opens a one-time review link, sees the held message summary, and chooses release or delete.
Practical rollout without a complicated control plane.
The rollout model is built to stay manageable for the organization while keeping privacy local and licensing clear.
Client ID and password
The organization can still use a normal SIP Shield portal login instead of learning a separate admin system.
Confirm the mailbox list
If more mailboxes are discovered than licensed, the IT team can remove extras and proceed with the approved set.
Roll out by count
Licensing is based on protected mailbox count, not on how many administrators or devices view the portal.
Keep privacy local
Mailbox credentials and mail content remain on the organization’s own server wherever possible.
One Linux package, adapted by profile instead of separate distro products.
SIP Shield keeps one main Linux package and uses compatibility profiles so deployment stays simpler across different Linux families and mail environments.
Supported
Ubuntu and Debian are the strongest starting point and the clearest documented rollout path.
Compatible
AlmaLinux, Rocky, and other RHEL-family systems can use the same package with light environment adjustments.
Profile written locally
The installer writes an install profile showing distro family, package manager, service manager, control panel markers, and mail stack markers.
One bundle
There is no need to maintain separate customer products for Ubuntu, Debian, AlmaLinux, or Rocky if the compatibility profile is clear.
Start with Linux, then expand to other private infrastructure paths.
The roadmap shown on the current page starts with Linux, then extends to Windows Server, AWS/Azure-style private cloud VMs, and hybrid models.
Self-hosted first target
Current tested reference path on Ubuntu 24.04 with Exim + Dovecot for self-hosted mail environments.
Planned Microsoft path
Planned option for organizations standardized on Microsoft server infrastructure.
Private cloud VMs
Future path for private cloud deployment while preserving the same licensing and mailbox-confirmation model.
Mixed rollout
Use server-side protection for the organization while preserving desktop tools where they still make sense.