Typo in iredmail-easy.best.practice.html.
This commit is contained in:
Zhang Huangbin
parent
eb5e6d2a0b
commit
df2c2e6f18
|
|
@ -253,36 +253,61 @@ overrode by the last one.
|
|||
|
||||
### Roundcube
|
||||
|
||||
- `/opt/iredmail/custom/roundcube/custom.inc.php`.
|
||||
- File `/opt/iredmail/custom/roundcube/custom.inc.php`
|
||||
|
||||
All your custom settings should be placed in this file, and do __NOT__
|
||||
touch main config file `/opt/www/roundcubemail/config/config.inc.php`.
|
||||
All your custom settings should be placed in this file, and do __NOT__
|
||||
touch main config file `/opt/www/roundcubemail/config/config.inc.php`.
|
||||
|
||||
- `/opt/iredmail/custom/roundcube/plugins/`: all third-party / custom
|
||||
plugins should be placed under this directory. Plugins will be linked
|
||||
to `/opt/www/roundcubemail/plugins/` automatically.
|
||||
- Directory `/opt/iredmail/custom/roundcube/plugins/`
|
||||
|
||||
- `/opt/iredmail/custom/roundcube/skins/`: all third-party / custom
|
||||
skins should be placed under this directory. Skins will be linked
|
||||
to `/opt/www/roundcubemail/skins/` automatically.
|
||||
All third-party or custom plugins should be placed under this directory.
|
||||
Plugins will be linked to `/opt/www/roundcubemail/plugins/` automatically
|
||||
during iRedMail Easy deployment, but you need to create the symbol
|
||||
link manually if you don't want to run another deployment.
|
||||
|
||||
- Directory `/opt/iredmail/custom/roundcube/skins/`
|
||||
|
||||
All third-party or custom skins should be placed under this directory.
|
||||
Skins will be linked to `/opt/www/roundcubemail/skins/` automatically
|
||||
during iRedMail Easy deployment, but you need to create the symbol link
|
||||
manually if you don't want to run another deployment.
|
||||
|
||||
### SOGo
|
||||
|
||||
- `/opt/iredmail/custom/sogo/sogo.conf`: If this file exists, `/etc/sogo/sogo.conf` will be a symbol link to this file.
|
||||
- `/opt/iredmail/custom/sogo/custom.sh`: a bash shell script for advanced customization
|
||||
SOGo doesn’t support directive like `include` to load extra settings
|
||||
from multiple files, so you have to either maintain your own SOGo config
|
||||
file (`/opt/iredmail/custom/sogo/sogo.conf`) or use the `custom.sh`
|
||||
shell script to do some customization based on the config file generated by
|
||||
iRedMail Easy platform.
|
||||
|
||||
Currently SOGo doesn’t support `include` directive to load config
|
||||
from multiple files, so you can either maintain your own SOGo config
|
||||
file (`/opt/iredmail/custom/sogo/sogo.conf`) or use the `custom.sh`
|
||||
shell script to do even more complex customization.
|
||||
- File `/opt/iredmail/custom/sogo/sogo.conf`
|
||||
|
||||
If this file exists, `/etc/sogo/sogo.conf` will be created as a symbol link
|
||||
to this file during iRedMail Easy deployment.
|
||||
|
||||
- Shell script `/opt/iredmail/custom/sogo/custom.sh`
|
||||
|
||||
A bash shell script for advanced customization, you can customize SOGo
|
||||
config file with shell commands organized in this file.
|
||||
|
||||
This file will be ran by iRedMail Easy deployment each time it deploys
|
||||
or upgrade SOGo component.
|
||||
|
||||
### iRedAPD
|
||||
|
||||
- `/opt/iredmail/custom/iredapd/settings.py`. It will be linked to `/opt/www/iredapd/custom_settings.py` also.
|
||||
- File `/opt/iredmail/custom/iredapd/settings.py`
|
||||
|
||||
All custom settings must be stored in this file.
|
||||
It will be linked to `/opt/www/iredapd/custom_settings.py` during iRedMail
|
||||
Easy deployment or upgrade.
|
||||
|
||||
### iRedAdmin
|
||||
|
||||
- `/opt/iredmail/custom/iredadmin/settings.py`. it will be linked to `/opt/www/iredadmin/custom_settings.py` also.
|
||||
- File `/opt/iredmail/custom/iredadmin/settings.py`
|
||||
|
||||
All custom settings must be stored in this file.
|
||||
It will be linked to `/opt/www/iredadmin/custom_settings.py` during iRedMail
|
||||
Easy deployment or upgrade.
|
||||
|
||||
### Amavisd
|
||||
|
||||
|
|
|
|||
|
|
@ -251,7 +251,7 @@ postconf -P "submission/inet/smtpd_client_restrictions=permit_sasl_authenti
|
|||
postconf -P "submission/inet/content_filter=smtp-amavis:[127.0.0.1]:10026
|
||||
</code></pre>
|
||||
|
||||
<p>For more details about <code>postconf</code> command, please check its manual page:
|
||||
<p>For more details about <code>postconf</code> command, please check its manual page:
|
||||
<a href="http://www.postfix.org/postconf.1.html">postconf(1)</a>.</p>
|
||||
<h3 id="dovecot">Dovecot</h3>
|
||||
<p>Dovecot supports loading from mulitple config files, and settings will be
|
||||
|
|
@ -262,40 +262,63 @@ overrode by the last one.</p>
|
|||
</ul>
|
||||
<h3 id="roundcube">Roundcube</h3>
|
||||
<ul>
|
||||
<li><code>/opt/iredmail/custom/roundcube/custom.inc.php</code>.</li>
|
||||
</ul>
|
||||
<p>All your custom settings should be placed in this file, and do <strong>NOT</strong>
|
||||
touch main config file <code>/opt/www/roundcubemail/config/config.inc.php</code>.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><code>/opt/iredmail/custom/roundcube/plugins/</code>: all third-party / custom
|
||||
plugins should be placed under this directory. Plugins will be linked
|
||||
to <code>/opt/www/roundcubemail/plugins/</code> automatically.</p>
|
||||
<p>File <code>/opt/iredmail/custom/roundcube/custom.inc.php</code></p>
|
||||
<p>All your custom settings should be placed in this file, and do <strong>NOT</strong>
|
||||
touch main config file <code>/opt/www/roundcubemail/config/config.inc.php</code>.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>/opt/iredmail/custom/roundcube/skins/</code>: all third-party / custom
|
||||
skins should be placed under this directory. Skins will be linked
|
||||
to <code>/opt/www/roundcubemail/skins/</code> automatically.</p>
|
||||
<p>Directory <code>/opt/iredmail/custom/roundcube/plugins/</code></p>
|
||||
<p>All third-party or custom plugins should be placed under this directory.
|
||||
Plugins will be linked to <code>/opt/www/roundcubemail/plugins/</code> automatically
|
||||
during iRedMail Easy deployment, but you need to create the symbol
|
||||
link manually if you don't want to run another deployment.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Directory <code>/opt/iredmail/custom/roundcube/skins/</code></p>
|
||||
<p>All third-party or custom skins should be placed under this directory.
|
||||
Skins will be linked to <code>/opt/www/roundcubemail/skins/</code> automatically
|
||||
during iRedMail Easy deployment, but you need to create the symbol link
|
||||
manually if you don't want to run another deployment.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h3 id="sogo">SOGo</h3>
|
||||
<ul>
|
||||
<li><code>/opt/iredmail/custom/sogo/sogo.conf</code>: If this file exists, <code>/etc/sogo/sogo.conf</code> will be a symbol link to this file.</li>
|
||||
<li>
|
||||
<p><code>/opt/iredmail/custom/sogo/custom.sh</code>: a bash shell script for advanced customization</p>
|
||||
<p>Currently SOGo doesn’t support <code>include</code> directive to load config
|
||||
from multiple files, so you can either maintain your own SOGo config
|
||||
<p>SOGo doesn’t support directive like <code>include</code> to load extra settings
|
||||
from multiple files, so you have to either maintain your own SOGo config
|
||||
file (<code>/opt/iredmail/custom/sogo/sogo.conf</code>) or use the <code>custom.sh</code>
|
||||
shell script to do even more complex customization.</p>
|
||||
shell script to do some customization based on the config file generated by
|
||||
iRedMail Easy platform.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>File <code>/opt/iredmail/custom/sogo/sogo.conf</code></p>
|
||||
<p>If this file exists, <code>/etc/sogo/sogo.conf</code> will be created as a symbol link
|
||||
to this file during iRedMail Easy deployment.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Shell script <code>/opt/iredmail/custom/sogo/custom.sh</code></p>
|
||||
<p>A bash shell script for advanced customization, you can customize SOGo
|
||||
config file with shell commands organized in this file.</p>
|
||||
<p>This file will be ran by iRedMail Easy deployment each time it deploys
|
||||
or upgrade SOGo component.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h3 id="iredapd">iRedAPD</h3>
|
||||
<ul>
|
||||
<li><code>/opt/iredmail/custom/iredapd/settings.py</code>. It will be linked to <code>/opt/www/iredapd/custom_settings.py</code> also.</li>
|
||||
<li>
|
||||
<p>File <code>/opt/iredmail/custom/iredapd/settings.py</code></p>
|
||||
<p>All custom settings must be stored in this file.
|
||||
It will be linked to <code>/opt/www/iredapd/custom_settings.py</code> during iRedMail
|
||||
Easy deployment or upgrade.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h3 id="iredadmin">iRedAdmin</h3>
|
||||
<ul>
|
||||
<li><code>/opt/iredmail/custom/iredadmin/settings.py</code>. it will be linked to <code>/opt/www/iredadmin/custom_settings.py</code> also.</li>
|
||||
<li>
|
||||
<p>File <code>/opt/iredmail/custom/iredadmin/settings.py</code></p>
|
||||
<p>All custom settings must be stored in this file.
|
||||
It will be linked to <code>/opt/www/iredadmin/custom_settings.py</code> during iRedMail
|
||||
Easy deployment or upgrade.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h3 id="amavisd">Amavisd</h3>
|
||||
<ul>
|
||||
|
|
|
|||
Loading…
Reference in New Issue