BashEmailFOR PLESK OBSIDIAN
A Plesk spam filter for safer inboxes and healthier sending.
Protect every subscription from incoming spam, phishing and infected mail, then contain outgoing abuse before one compromised sender affects the server. BashEmail runs on the Plesk server you already manage, with no MX change, no DNS change and no external mail relay.
One native Plesk extension
Private subscription quarantine
Mail stays on your server
Email security for Plesk hosting
One mail server carries two very different kinds of risk.
The first risk is visible to customers: junk, phishing attempts and harmful attachments reaching their mailboxes. The second can be quieter and more expensive. A stolen password or compromised website can start sending unwanted mail through your server, putting unrelated subscriptions and your sending reputation under pressure.
A practical Plesk spam filter needs to protect both directions without taking over the mail route or forcing every subscription into the same policy. BashEmail gives administrators server-wide control while letting each customer review only the held mail that belongs to their own domains.
Incoming Plesk spam filtering
Make the decision clear before delivery.
BashEmail follows the policy selected for each domain or mailbox. Wanted messages continue through the existing Plesk mail path. Questionable mail is handled in the way the administrator has chosen, with the result visible to the people responsible for it.
INCOMING EMAIL
Wanted mail and unwanted mail
Existing mail route
BASHEMAILFilter · scan · apply policy Runs on the Plesk server
PLESK MAIL DELIVERY
Inbox, Junk or quarantine
Subscription policy applied
Tune individual mailboxes
Give a sensitive mailbox stronger filtering without making every other customer accept the same level of strictness.
Keep infected mail reviewable
Malware and virus detections are held instead of being silently discarded, so operators can see what happened.
Respect known exceptions
Allow and deny lists support trusted relationships, unwanted sources and requirements that belong to a particular domain.
Quarantine inside the Plesk Mail tab
Keep self-service properly scoped.Each customer can only view and act on mail for domains, subdomains and mailboxes assigned to their subscription.
Make recovery simple.Deliver a wanted message, delete one item, remove a selection or empty the quarantine from one familiar place.
Show what retention will do.The view explains how much is held, how recent it is and when older messages will be removed automatically.
Give customers a private answer to “where did my message go?”
Customers open BashEmail from the Mail tab of their own subscription, beside the tools they already use. They can inspect held messages for their domains without waiting for a hosting administrator and without seeing any other subscription.
HELD MAILPrivate quarantine
Scoped to this subscriptionSearch held messagesSearch
MESSAGE TYPERESULTACTION
Account notificationExpected business message
ReviewReleaseUrgent password noticeIdentity warning detected
PhishingDeleteUnrequested promotionUnwanted bulk mail
SpamDelete
Outgoing spam protection for Plesk
Contain the smallest useful scope.A sending restriction does not take the website, FTP, incoming mail or the rest of the subscription offline.
Let temporary actions end.Automatic watch, hold and suspension states expire on their own, avoiding an old restriction that nobody remembers to remove.
Protect the addresses used for delivery.BashEmail watches the server addresses that actually send mail and warns your team when reputation needs attention.
Stop the sending problem without disabling the customer.
When a mailbox credential or website is abused, BashEmail responds to the sending risk in stages. Activity can be watched, held and then suspended through Plesk's own Outgoing Mail Control. The action appears in the Plesk screens your administrators already understand and respects the limits they have configured.
One Plesk extension, two appropriate views
Keep the hosting team in control and customers out of the support queue.
The server administrator sees the complete mail picture. A subscription customer sees only the decisions they can safely resolve. Both views live inside Plesk, so there is no separate control panel account to create or another portal to explain.
- Server-wide administration inside Plesk
- Customer quarantine beside existing Mail tools
- Outgoing enforcement visible in Outgoing Mail Control
See the full mail operation
Review traffic, delivery outcomes, active senders, incoming sources, sign-in attack sources, quarantine and message events across the server.
- Server and subscription policies
- Per-sender and per-domain limits
- Searchable mail history
- Sending reputation warnings
Resolve their own held mail
Preview, deliver or delete messages from the Mail tab while every other customer's data remains private.
- Own domains only
- Single and bulk actions
- Clear retention summary
- No additional login
Plesk Obsidian on Ubuntu and Debian RHEL and CloudLinux support Built through supported Plesk extension points
On-server Plesk email security
Protect mail without handing the route to another provider.
External filtering gateways usually ask you to point customer MX records at their infrastructure. BashEmail stays on the Plesk server, so domains keep their existing DNS, messages keep their normal route and held mail remains under the hosting company's control.
There is no migration project for existing mailboxes and no outside service becomes responsible for storing the quarantine. Customers continue using the Plesk mail experience they already know.
Explore the BashEmail platformQUESTIONBASHEMAILEXTERNAL GATEWAY
Where is mail inspected?On the Plesk serverOn provider infrastructure
Do MX records change?NoUsually required
Where is quarantine kept?On your serverOutside your server
Where do customers work?Inside PleskOften another portal
A cautious route into production
See how your own mail would be handled before anything is held.
BashEmail is installed in observe-only mode. Administrators can review likely outcomes on real server traffic, adjust the policy and enable enforcement only when they are comfortable with the result.
Fail open by design
If filtering is unavailable, mail continues instead of being deferred or bounced because of BashEmail.
Observe before enforcing
The initial installation does not hold messages. Your team decides when the reviewed policy is ready.
Work with Plesk
Supported extension points avoid taking ownership of files and settings that the panel itself manages.
Uninstall cleanly
Removing BashEmail restores the panel's filtering, releases held mail and retains what was learned for a later reinstall.
BashEmail pricing
Straightforward pricing for the whole mail server.
Choose a plan by the number of hosting accounts on the server. Incoming filtering, outgoing abuse controls, malware scanning and quarantine are included in both.
Lite
Up to 10 hosting accounts
$12per month
Get BashEmail
- Incoming spam and malware filtering
- Outgoing abuse detection and control
- Quarantine and end-user self-service
- Per-domain and per-mailbox policies
- Up to 10 hosting accounts
Unlimited accounts
Standard
Unlimited hosting accounts
$23per month
Get BashEmail
- Everything in Lite
- Unlimited hosting accounts
- Unlimited hosted domains
Price per server, per month, excluding VAT. Cancel anytime. Talk to us.
Plesk spam filter questions
What Plesk hosting teams need to know before switching it on.
What is BashEmail for Plesk?
BashEmail is an on-server Plesk spam filter and email security product for hosting companies. It filters incoming threats, contains outgoing abuse, gives administrators server-wide visibility and lets subscription customers manage their own private quarantine.
Does this Plesk spam filter require an MX or DNS change?
No. BashEmail installs on the existing Plesk server and works with its current mail flow. Customer domains do not need to route messages through an external mail security gateway.
Where do Plesk customers find their quarantine?
Customers open the BashEmail view from the Mail tab of their subscription, beside the other Plesk mail tools. They can only access messages associated with domains inside that subscription.
Can an administrator deliver suspicious mail to Junk instead?
Yes. The administrator can choose whether caught mail is held in quarantine or delivered to the recipient's Junk folder. Strictness can also be adjusted for an individual domain or mailbox.
How does BashEmail handle outgoing spam in Plesk?
BashEmail can move suspicious sending through watch, hold and suspension stages by using Plesk's own Outgoing Mail Control. A suspension stops sending only, while incoming mail and other subscription services remain available.
Will an automatic outgoing restriction remain forever?
No. Automatic watch, hold and suspension actions expire on their own. This prevents a temporary response from remaining in place after the original risk has passed.
Which Plesk servers are supported?
BashEmail supports Plesk Obsidian on Ubuntu and Debian as well as RHEL-family and CloudLinux servers.
Can a BashEmail problem interrupt customer mail?
BashEmail is designed to fail open. If its filtering is unavailable, the server continues processing mail instead of deferring or bouncing messages because of the filter.
Can operators train the Plesk mail spam filter from quarantine?
Yes. Train and release improves future treatment when wanted mail was held, while train and delete reinforces an unwanted decision. Release-only and delete-only actions are also available when the operator does not want the decision to affect later messages.
BASHEMAIL FOR PLESK
Protect every subscription without changing the mail route.
Add incoming spam filtering, private quarantine and outgoing abuse control to the Plesk server you already operate.