Request Samples

Update domain templates that belong to different Plesk user

To update settings of a domain template that belongs to Plesk Client, specify this client either by id, or by login.

<packet version="1.4.1.0">

<domain-template>

<set>

   <filter>

      <name>base_template</name>

   </filter>

   <client-login>tecnhnolux</client-login>

   <mail>

      <webmail>true</webmail>

   </mail>

</set>

</domain-template>

</packet>

Or:

<packet version="1.4.1.0">

<domain-template>

<set>

   <filter>

      <name>base_template</name>

   </filter>

   <client-id>1234</client-id>

   <mail>

      <webmail>true</webmail>

   </mail>

</set>

</domain-template>

</packet>

To update settings of a domain template that belongs to Plesk Administrator, don't use nodes client-id and client-login:

<packet version="1.4.1.0">

<domain-template>

<set>

   <filter>

      <name>base_template</name>

   </filter>

   <mail>

      <webmail>true</webmail>

   </mail>

</set>

</domain-template>

</packet>

Operating multiple domain templates

Here is the sample packet that sets similar domain template settings for two different domain templates, both specified by id.

<packet version="1.4.1.0">

<domain-template>

<set>

   <filter>

      <id>11</id>

      <id>12</id>

   </filter>

   <mail>

      <webmail>true</webmail>

   </mail>

</set>

</domain-template>

</packet>

To set different settings for two domain templates, use two different <set> blocks:

<packet version="1.4.1.0">

<domain-template>

<set>

   <filter>

      <id>12</id>

   </filter>

   <client-login>tecnhnolux</client-login>

   <mail>

      <webmail>false</webmail>

   </mail>

</set>

<set>

   <filter>

      <name>base_template</name>

   </filter>

   <mail>

      <webmail>true</webmail>

   </mail>

</set>

</domain-template>

</packet>

The following packet updates all domain templates belonging to the specified Plesk Client:

<packet version="1.4.1.0">

<domain-template>

<set>

   <filter/>

   <client-login>tecnhnolux</client-login>

   <mail>

      <webmail>false</webmail>

   </mail>

</set>

</domain-template>

</packet>

The following packet updates all domain templates that belong to Plesk Administrator:

<packet version="1.4.1.0">

<domain-template>

<set>

   <filter/>

   <mail>

      <webmail>false</webmail>

   </mail>

</set>

</domain-template>

</packet>

Mailing settings

The following packet updates mailing settings of three domain templates that belong to Plesk Administrator. The new mailing settings are as follows:

• the 'bounce_template' domain template allows email users to access the email service of Plesk (the WebMail application) and specifies the text sent back if a message is addressed to a non-existing user;
• the 'forward_template' forwards mail addressed to a non-existing user to a certain email box;
• the 'reject_template' rejects mail addressed to a non-existing user (such messages are not accepted by the mail server.

<packet version="1.4.1.0">

<domain-template>

<set>

   <filter>

      <name>bounce_template</name>

   </filter>

   <mail>

      <webmail>true</webmail>

      <nonexistent-user>

           <bounce>Email address you specified does not exist.</bounce>

      </nonexistent-user>

   </mail>

</set>

<set>

   <filter>

      <name>forward_template</name>

   </filter>

   <mail>

      <nonexistent-user>

           <forward>spam@technolux.co.uk</forward>

      </nonexistent-user>

   </mail>

</set>

<set>

   <filter>

      <name>reject_template</name>

   </filter>

   <mail>

      <nonexistent-user>

           <reject/>

      </nonexistent-user>

   </mail>

</set>

</domain-template>

</packet>

Setting limits

<packet version="1.4.1.0">

<domain-template>

<set>

   <filter>

      <id>12</id>

   </filter>

   <limits>

      <disk_space>2048</disk_space>

      <max_traffic>10240</max_traffic>

      <max_db>50</max_db>

      <mysql_dbase_space>1024</mysql_dbase_space>

      <expiration>63072000</expiration>

   </limits>

</set>

</domain-template>

</packet>

Log rotation

To disable log rotation in the specified template, use the following packet:

<packet version="1.4.1.0">

<domain-template>

<set>

   <filter>

      <id>12</id>

   </filter>

   <log-rotation>

      <off/>

   </log-rotation>

</set>

</domain-template>

</packet>

The following packet enables log file rotation on a domain created using this domain template, allows the storage of up to 30 handled log files related to this domain, and removes active log files related to this domain from logging once a week:

<packet version="1.4.1.0">

<domain-template>

<set>

   <filter>

      <id>12</id>

   </filter>

   <log-rotation>

      <on>

           <log-condition>

              <log-bytime>weekly</log-bytime>

           </log-condition>

           <log-max-num-files>30</log-max-num-files>

           <log-compress>true</log-compress>

      </on>

   </log-rotation>

</set>

</domain-template>

</packet>

Preferences

The following packet specifies preferences for a domain template:

<packet version="1.4.1.0">

<domain-template>

<set>

   <filter>

      <id>12</id>

   </filter>

   <preferences>

      <stat>6</stat>

      <maillists>true</maillists>

      <dns_zone_type>master</dns_zone_type>

   </preferences>

</set>

</domain-template>

</packet>

Hosting

Here is the sample packet that sets physical hosting settings to a domain template under Plesk Client permissions.

<packet version="1.4.1.0">

<domain-template>

<set>

   <filter>

      <id>12</id>

   </filter>

   <hosting>

      <vrt_hst>

           <ftp_quota>100</ftp_quota>

           <ssl>true</ssl>

           <php>true</php>

           <php_safe_mode>true</php_safe_mode>

           <ssi>true</ssi>

           <cgi>true</cgi>

           <mod_perl>true</mod_perl>

           <mod_python>true</mod_python>

           <webstat>webalizer</webstat>

           <errdocs>true</errdocs>

      </vrt_hst>

   </hosting>

</set>

</domain-template>

</packet>