Creating 'Mail Hosting' Resource Type

To create a resource type for Mail Hosting, perform the following actions:

1. Go to Products > Resources and click the Add New Resource Type button.
2. Click the Mail hosting (qmail with clustering support) resource class.

3. Fill out the following fields:

   • Name – The name of resource type, for example: Cqmail Hosting.
   • Description – resource type description.

   Click Next.

4. Fill out the following activation parameters:

   • IMAP/IMAPs load balancing rules ID (typically empty string) – Leave this field empty.
   • POP3/POP3s load balancing rules ID (typically empty string) – Leave this field empty.
   • SMTP load balancing rule ID string (e.g., 'with_antispam') – Leave this field empty.

   • Auto host domains (yes/no) – This activation parameter, when enabled, allows auto-provisioning of hosting to the domain by CloudBlue Commerce Public API call from external system. Such requests can be made using the pem.addDomain and pem.bindServicesToDomain Public API methods. There are the following use-cases:

     • Yes (1). In that case, hosting will be added to the domain.
     • No (0). In that case, hosting will not be added to the domain.

     We recommend entering this activation parameter at a service template creation stage.

     Note: To obtain detailed information about CloudBlue Commerce Public API methods, refer to the CloudBlue Commerce Public API Reference.

   • Custom SPF record – It allows to specify a custom SPF record for customer domains instead of the default one. The specified value should represent a correct SPF record. For details about SPF records and SPF rules syntax, refer to http://www.openspf.org.
   • Maximum Autoresponder invocations rate per day – We recommend entering this activation parameter at the service template creation stage.
   • Maximum number of autoresponders per mailname – We recommend entering this activation parameter at the service template creation stage.
   • Maximum number of forwardings per mailname – We recommend entering this activation parameter at the service template creation stage.
   • Maximum quota for a mailbox in Kb – We recommend entering this activation parameter at the service template creation stage.
   • Management of visibility of mailbox/maillist in GAL (yes/no) – This activation parameter defines whether the ability to manage Global Address List visibility of mailboxes and maillists is enabled for customers. Set Yes if the webmail service used with the clustered qmail service supports the visibility management for mailboxes and maillists. In other cases set No.
   • Maximum number of maillist subscribers per maillist – We recommend entering this activation parameter at the service template creation stage.
   • Mail throttling per day – We recommend entering this activation parameter at the service template creation stage.
   • Mail throttling per hour – We recommend entering this activation parameter at the service template creation stage.

   • Mail throttling per minute – We recommend entering this activation parameter at the service template creation stage.

     Note: Since throttling limit usage data is stored on the WHOSON server, please bear in mind the RAM usage: for instance, 30 000 customer mailboxes created in a Subscription with Messages per day limit set to 1024 (and used to the full) will occupy 128 MB RAM on WHOSON server. Throttling limits work only for users authenticated via SMTP.

   • Outgoing SMTP load balancing rule ID string – If this resource type is intended for single-host qmail services, leave this field empty. If it is intended for clustered qmail services, the Outgoing SMTP value should be specified.

   Click Next.

5. Select the required provisioning attributes and click Next.
6. Check the parameters and click Finish.

Note: To learn more about the IMAP/IMAPs load balancing rules ID, POP3/POP3s load balancing rules ID, SMTP load balancing rule ID, and Outgoing SMTP load balancing rule ID string activation parameters, see the https://kb.cloudblue.com/116240 KB article.