Mailborder licenses determine the capabilities of not only your Master server, but also the entire cluster. Child servers inherit their capabilities from the Master server, which means that Child server licenses never need to be upgraded.
Licenses work on Managed Objects, which is explained below. How many Managed Objects you need will determine which Mailborder license you need.
If you require an upgrade to the capabilities of your Master server or cluster, only the Master server license needs to be upgraded. This is managed on the Mailborder website under Account > Licenses.
Managed Objects calculated in licensing include the following:
- Email Objects (not regular email)
- Authenticators (groups of 10)
How Licensing Works
Licensing is calculated by determining the number of Managed Objects that are being used on the Master server. Managed Objects are items that have policies assigned to them. Objects that pass through Mailborder that do not have a policy assigned are unmanaged objects.
Authenticators are username:password combinations that allow remote users or devices to relay email through the Mailborder server. Authenticators are calculated for licensing in groups of 10, or 0.1 for each authenticator. If you create 5 authenticators, it counts a 1 in licensing. If you have 12 authenticators, it counts as 2 in licensing. See Example 4 below.
Example 1: Domain
You own the domain example.com and have it listed in your Domains with policies assigned to it. This is a managed domain. Your user email@example.com gets an email from firstname.lastname@example.org. The Gmail server's IP address is 172.16.39.34. Here is a list of the components and how they are classified:
The policies you have set for example.com match and apply to email@example.com. The license count being used here is 1.
*The number of user@ is unlimited. A single domain managed object will cover every user. You do not need a license for each email user.
Example 2: Network
You have an internal email server with the IP address 10.10.1.25 and handles the email boxes for the domain foo.com. The user firstname.lastname@example.org sends an email out to email@example.com. You want to allow this server to relay outbound through the Mailborder server and add it to your Networks. This becomes a managed network. Here are the component classifications:
The policies you have set for the Network 10.10.1.25 will apply to the firstname.lastname@example.org outbound email. The license count being used here is 1.
Example 3: Email Object
You own the domain example.com and have it listed in Mailborder as a Domain. You have an internal user you wish to grant special email permissions. For example, you do not allow .zip files in file attachments for example.com, but email@example.com needs to be able to receive these files. You can add firstname.lastname@example.org to Mailborder as an Email Object and assign that email address its own set of policies that allow .zip file attachments. Here is an example email from email@example.com:
The policies for example.com match everyone except firstname.lastname@example.org because Mark has his own special policy for his email. The license count being used here is 2.
Example 4: Authenticator
You have a printer that you want to allow to send email through the Mailborder server. You create a username:password combination for that printer in Mailborder under Cluster > Authenticators. The printer can send email "From" any email address and "To" any email address. Polices on the Mailborder server may or may not match the email. If nothing matches the default policy will be used.
|Authenticator Count||License Count|