What is Baruwa Enterprise Edition
Baruwa Enterprise Edition is a fully fledged Mail Security solution, based on a blend of best of breed open source and proprietary software packages. It provides protection from spam, viruses, phishing attempts and malware attacks.
Baruwa Enterprise Edition is a proven email security platform for organizations of any size from small to medium businesses to large service providers, carriers and enterprises.
Baruwa Enterprise Edition works with any standard SMTP server, is highly accurate, scalable, easy to integrate as well as manage.
Automated installation, configuration management tools and an API with several API Libraries are provided to ensure the efficient and easy management of the System. You can even craft your own Infrastructure as Code deployment solution using SaltStack and our packaged salt states.
The management interface is implemented using web 2.0 features (AJAX) where deemed fit. It has full support for i18n, enabling you to translate it into any language of your choosing. It has already been translated into to over 25 languages. Current Languages supported
Also included is reporting functionality with an easy to use query builder, whose results can be displayed as message lists or graphed as colorful and pretty interactive graphs.
Built in Full text search functionality allows you to find information very fast and easily. Advanced searching options available in leading web search engines are supported.
Baruwa Enterprise Edition is built on an open source core and runs on a
slimmed down and customized Linux OS. All the bloat has been trimmed leaving
only an OS dedicated to email security. The current version of
Baruwa Enterprise Edition
BaruwaOS 6 will be supported until Jun 2024.
Baruwa Enterprise Edition can be installed on Premise or in the cloud.
How does it work
It operates as an Email security gateway accepting mail from untrusted sources, running extensive checks on it and then passing the clean mail to the destination. It does not support the hosting of user mailboxes.
For incoming messages, it is configured to accept mail on behalf of your internal mail server run extensive checks on it then forward the clean mail to your internal mail server.
For outgoing messages, your internal mail server can be configured to pass all outbound messages to it for processing before being sent on to the destination. From the internal servers point of view the system is its smart host.
It can operate as a standalone all in one solution or as a cluster of servers. Clusters are made up of frontend and backend segments. In the frontend segment the traditional concept of a cluster master is not supported, all the nodes in the cluster have equal status and can be brought into and taken out of the cluster without any special changes. Backend segment clustering was introduced in version 2.1.7.
- Spam, Virus, Phishing, Malware protection
- Extensive Spam Detection checks
- AJAX support for most operations
- Ultra fast full text search
- Reporting with AJAX enabled query builder
- I18n support, allows use of multiple languages
- Themes/Skins for rebranding
- Signature management / Branding
- Mail queue management and reporting
- Message delivery/relay information
- DKIM management
- DMARC Checks and Reporting
- Reporting graphs
- Emailed PDF reports
- Audit trails
- Archiving of old message logs
- Multi Tenancy
- IP / network addresses supported in approved/banned list manager
- System status information
- IPv6 Support
- Import and Export of User accounts and Domains
- AD/Exchange integration to auto populate account and group information
- TOTP OTP Two Factor Authentication
- Easy plug-in authentication to external authentication systems
- AD/LDAP, POP3, IMAP, SMTP, RADIUS, SAML2 Authentication support
- REST OAUTH based API
- Tools for housekeeping tasks
- Easy clustering of multiple servers
- No limits on domains and users add as many as your hardware can support.
- Free Certbot/Lets Encrypt TLS/SSL certificates
- Email Address tagging support
A full feature list is available at Feature List
Baruwa Enterprise Edition is available under a
PAID subscription, subscriptions
can be paid for monthly or annually.
NO restrictions or limitations on the number of domains, email addresses
and users that you can configure on your systems. You are only limited by the system
resources on your hardware. Unlike competing products we do not charge based on the
number of domains or users.
Subscription are purchased via the Baruwa website, using PayPal or PayFast. The order system is automated, as soon as PayPal/PayFast processes the payment and notifies our system your subscription will be generated and the subscription details emailed to you. This should take no more than 5 minutes. If you do not receive email confirmation of your subscription within 15 minutes please contact Support.
30 day Trial subscriptions can be obtained via the Baruwa website, a valid PayPal/PayFast account is required to access the Trial subscription. There is no obligation and the Trial can be cancelled at any point within the 30 Days.
Refer to Why do you require a PayPal/PayFast account for the 30 day Trial ? for the reason why a valid PayPal/PayFast account is required.
- Intel/AMD 2.0 GHZ+ 64-bit CPU
- Minimum - 6 GB RAM
- 12 GB free disk space for OS
- Additional disk space for Mail and Data storage
NOTE: The amount of resources allocated to system is directly related to the amount of email the system will be processing as well as the number of users connected to the web interface.
Baruwa Enterprise Edition can be configured in various topologies.
which is the default configuration, and works well in small scale environments
in larger environments with higher mail volumes and user numbers as well as
stricter uptime requirements clustered topologies should be used.
standalone system cannot later down the line get converted to
a clustered system. If you intend on running a cluster do not use the
The supported clustered topologies are described below.
Distributed Backend Distributed Frontend
In this topology all the backend components are each installed on standalone systems and the frontend components are also installed on standalone systems. This solution is the recommended for very large environments as it performs better and scales out and in easily.
Distributed Backend Hybrid Frontend
In this topology all the backend components are each installed on standalone systems and the frontend components are combined on to a node. Scaling is achieved by growing the frontend or backend cluster segments.
Single Backend Distributed Frontend
In this topology all backend components are installed on a single system and the frontend components are each installed on standalone systems. Scaling is achieved by growing the frontend or backend cluster segments.
Single Backend Hybrid Frontend
In this topology all backend components are installed on a single system in and the frontend components are combined on to a node. Scaling is achieved by growing the frontend or backend cluster segments.
NOTE: The smallest cluster that can be created is based on the
Single Backend Hybrid Frontend topology and is made up of a
clustered frontend and none clustered backend. The number of devices
in this cluster is three (3). Two (2) frontend and one (1) backend.