In addition to the publication of your website, our offers allow the creation of a personalized email to your domain name.
Create email addresses and use different protocols to manage your emails from anywhere and on any device.Our offers are compatible with most of the Content Management Systems : Joomla, Prestashop, WordPress, Drupal …
Whether you have a personnal or institutional website or even an online shop, our web hosting offers can fit your needs for any project.
With PLESK, you have access to a complete interface for the daily administration of your hosting.
All Cloud Services Store hosting services are backed by our pioneering Hosting Guarantee. This guarantee is a mark of the high quality you can expect from Cloud Services Store and underlines our commitment to providing excellence in our hosting division. Our Hosting Guarantee explains that we treat each service you have with Cloud Services Store individually. You can subscribe, modify or cancel any service you have with us at any time.
DKIM “provides a method for validating a domain name identity that is associated with a message through cryptographic authentication” (www.dkim.org).
You enable DKIM email signing for domains that use the Plesk DNS server and those that use an external DNS server in a different way.
Enabling DKIM Email Signing for Domains That Use the Plesk DNS Server
To enable DKIM signing of outgoing email, go to Websites & Domains > Mail Settings of a domain, select the Use DKIM spam protection system to sign outgoing email messages checkbox and click OK.
If you have activated DKIM for a domain, Plesk adds the following two records to the DNS zone of the domain (example.com stands for your domain name):
default._domainkey.example.com - contains the public part of the generated key.
_domainkey.example.com - contains the DKIM policy. You can edit this policy.
Enabling DKIM Email Signing for Domains That Use an External DNS Server
If you use an external DNS service, DKIM signing will work for outgoing messages, but the receiving mail server will not be able to validate these messages. As a workaround, you can switch off Plesk DNS server and add a corresponding DKIM-related DNS record on the external DNS service. In this case, the receiving server will be able to validate the messages.
SPF and DMARC Policies for Outgoing Mail
In addition to DKIM, Plesk supports SPF and DMARC policies for outgoing mail. DMARC carries out the specified policy as to how to treat email messages depending on the results of the DKIM and SPF checking. By default, DMARC uses general policy, and messages that did not pass checking are not deleted. You can use stricter policy. For example, you can specify that it is necessary for a message to pass both SPF and DKIM checking to be accepted by the recipient mail server.
You can change the SPF and DMARC policies for your domain in the domain’s DNS settings.
To set up DMARC or SPF policy for your domain:
Go to Websites & Domains > navigate to the domain > DNS Settings and edit the DNS records related to SPF or DMARC. For example, this record contains the default DMARC policy:
_dmarc.<your domain>. TXT v=DMARC1; p=none
For information on DMARC and SPF, including policy notations, refer to:
It is not possible to manage the default mailbox size via Plesk user interface in Web Admin edition, because the main purpose of the license is to keep everything unlimited excepting the number of domains.
The only way to manage it is through command-line with administrator privileges.
Note: if direct SSH/RDP access to the server is not possible, contact server administrator for further assistance.
Examples (both for Linux and Windows):
Set default quota to 100M:
# plesk bin subscription_settings --update example.com -mbox_quota 100M
Set the default mailbox size to the default value (Unlimited):
Note: default value for subscription is inherited from its service plan
# plesk bin subscription_settings --update example.com -mbox_quota -1
To change the limit for a specific mailbox, use plesk bin mail utility (or from the User Interface at Mail > [email protected]):