3,070
edits
Changes
From SME Server
Jump to navigationJump to searchtraduction de la contribution en français
{{Languages|RoundCube}}
{{Level|Easy|Les instructions pour installation et l'utilisation de Roundcube peuvent être suivies par un débutant ; la modification des options nécessite une connaissance basique de Linux.}}
{{usefulnote}}
<blockquote style="float: right;">[[File:roundcube.png|250px]]</blockquote><br>
==RoundCube V1.0 pour le serveur SME Koozali==
===Maintaineur===
[mailto:stephdl@de-labrusse.fr stephdl] Stéphane de Labrusse AKA [[User:stephdl|Stephdl]]<br />
{{ #smeversion: smeserver-roundcube }}
{{ #smeversion: roundcubemail_plugins }}
{{ #smeversion: roundcubemail }}
{{ #smeversion: roundcube }}
===Installation===
<tabs container=""><tab name="Pour SME 10">
Ceci nécessite une refonte.
Nous pouvons utiliser le dépôt Remi pour Roundcube en soi.
https://wiki.contribs.org/Remi-roundcube
Il aura besoin de la réécriture du plugin smeserver-roundcube pour php-fpm :
yum install smeserver-extrarepositories-remi-roundcube -y
Pour la version LTS 1.5.3, ajouter ceci :
yum install yum-plugin-versionlock -y
yum versionlock roundcubemail-1.5.3
sinon vous mettrez à jour vers la version 1.6.
yum install smeserver-roundcube --enablerepo=smedev,smecontribs,smetest,remi-roundcube
semble faire l'installation même si vous obtenez une erreur : « Could not open input file: /usr/share/roundcubemail/composer.phar »
</tab><tab name="Pour SME 9">
yum install smeserver-roundcube --enablerepo=smecontribs
Répondre « oui » (y) pour tous les plugins que vous voulez activer
Si vous ne voulez pas redémarrer votre serveur :
signal-event roundcube-update
sinon :
signal-event post-upgrade; signal-event reboot
Mise à jour :
yum upgrade --enablerepo=smecontribs,remi-roundcube
</tab><tab name="Pour SME 8">
==== '''For SME8''' ====
Remember to first configure the two required repositories, [[stephdl]] and [[epel]],
then issue the following command on the SME Server shell:
yum install smeserver-roundcube --enablerepo=epel,stephdl
rcplugin_update.sh
answer yes (y) for all plugins you want to activate
If you do not want to restart your server
signal-event roundcube-update
or
signal-event post-upgrade; signal-event reboot
</tab>
</tabs>
===Désinstallation===
Pour supprimer le paquet, exécutez la commande suivante sur l'interface du serveur SME :
yum remove roundcube smeserver-roundcube smeserver-roundcube_plugins
Pour supprimer la base de données mysql et l'utilisateur, les deux appartenants à RoundCube, voir [[MySQL#Remove a database]] and [[MySQL#Remove a user]]. Il n'y a pas besoin de redémarrer.
===Utilisation===
http://nom_du_serveur/roundcube'' et se connecter avec votre compte utilisateur du serveur SME.
===Journaux===
Les journaux sont disponibles :
* pour sme8
less /opt/roundcube/logs/errors
* pour sme9
less /var/log/roundcubemail/errors
* pour SME 10
===Limiter l'accès à l'interface web===
{{Note box|type=Note : | par défaut, l'interface webmail Roundcube est accessible depuis tout l'internet sans nécessiter une authentication HTTP supplémentaire.}}
L'acès à Roundcube peut être ajusté finement en règlant la propriété correspondante dans la BDD de configuration du serveur SME :
config setprop roundcube PublicAccess OPTION
où « OPTION » est l'un des paramètres suivants :
none => Pas d'acès
local => Réseau local (mot de passe non requis)
local-pw => Réseau local (mot de passe requis)
global => Tout l'Internet (mot de passe non requis, c'est la configuration par défaut de SME)
global-pw => Tout l'Internet (mot de passe requis)
global-pw-remote => Tout l'Internet (mot de passe requis en dehors du réseau local)
Par exemple, pour restreindre l'accès au seul LAN :
config setprop roundcube PublicAccess local
Pour activer ces modifications dans la BDD de configuration, exécutez ensuite ces commandes :
expand-template /etc/httpd/conf/httpd.conf
sv h /service/httpd-e-smith
Note : pour une description générale sur la façon de régler une BDD sur le serveur SME, jeter un œil sur [[Web Application RPM#New DB settings]].
=== Customization ===
====Roundcube plugins====
=====Default plugins shipped with smeserver-roundcube=====
The smeserver-roundcube contrib is shipped with the following plugins already installed and enabled by default:
config getprop roundcube PluginsList
''globaladdressbook,carddav,calendar,libcalendaring,contextmenu,markasjunk,vcard_attachments,newmail_notifier,emoticons,tasklist,managesieve''
=====Installing additional plugins=====
{{Note box|The upstream Roundcube project is currently transitioning from making plugins available through http://trac.roundcube.net/wiki/Plugin_Repository to a new full fledged plugin repository at http://plugins.roundcube.net and a semi-automated plugin installation process. SME server admins are encouraged to use the new style method described below. }}
To install an additional (non-default) Roundcube plugin in SME server roundcube :
'''Step 1:''' Find the plugin page on http://plugins.roundcube.net/packages (eg. http://plugins.roundcube.net/packages/cor/message_highlight)
'''Step 2:''' Take note of the package name and version shown in the 'require:' line right below the title of the plugin's version heading (eg. "cor/message_highlight": "dev-master")
'''Step 3:''' Add the package name and version to the "require:" block in /opt/roundcube/composer.json. Take attention to the comma (,) separator, it is really important!
* for sme8
nano /opt/roundcube/composer.json
* for sme9
nano /usr/share/roundcubemail/composer.json
"require": {
"php": ">=5.3.0",
"roundcube/plugin-installer": ">=0.1.3",
"johndoh/markasjunk2": "dev-release-1.0",
"johndoh/contextmenu": "dev-master",
"johndoh/globaladdressbook": "dev-release-1.0",
"cor/message_highlight": "dev-master"
},
* for sme10 nothing to do there.
'''Step 4:''' after each modification to composer.json, in order to automatically download and install the plugin launch
rcplugin_update.sh
When asked, answer yes to automatically activate the plugin in the current Roundcube configuration.
'''Step 5:''' In order to keep the list of installed plugins persistent when this contrib is updated (ie. configuration templates are expanded again), you *absolutely* need to add the newly installed Roundcube plugin to the "PluginsList" property of "roundcube" in the configuration database of SME server in addition to steps above:
'''Step 5a:''' First show the list of plugins currently in the configuration DB:
config getprop roundcube PluginsList
''PluginsList=globaladdressbook,carddav,calendar,libcalendaring,contextmenu,markasjunk,vcard_attachments,newmail_notifier,emoticons,tasklist,managesieve''
'''Step 5b:''' Add your newly installed plugin to the list (separated by a comma (,) and without spaces) and activate the change:
config setprop roundcube PluginsList globaladdressbook,carddav,calendar,libcalendaring,contextmenu,markasjunk2,vcard_attachments,newmail_notifier,emoticons,tasklist,managesieve,message_highlight
'''Step 5c:''' Activate the changes to the config DB:
signal-event roundcube-update
Step 5 in short, using backticks:
config setprop roundcube PluginsList `config getprop roundcube PluginsList`,message_highlight
signal-event conf-roundcube
To check for updates to plugins already installed, you can at any time issue the following command again:
rcplugin_update.sh
====Customize Roundcube settings====
For special needs you should create your personal template file if you want your config file will not be overwritten by the smeserver-roundcube templates. This also applies to Roundcube plugins in /opt/roundcube/plugins/ which occasionally come with their own config.inc.php or generic config.php.inc.dist which you can use to set default options.
* The config file for Roundcube itself is now templated, so changes need to be made in a new custom template fragment
:*for sme8
ll /etc/e-smith/templates/opt/roundcube/config/config.inc.php/
''10default_host 15Ldap_addressbook 20plugins_configuration template-begin template-end ''
:* for sme9/sme10
ls /etc/e-smith/templates/etc/roundcubemail/config.inc.php/
10SQL_DATABASE 20LOGGING_DEBUGGING 30IMAP 40SMTP 50LDAP 60SYSTEM 70USER_INTERFACE 80ADDRESSBOOKS_SETTINGS 90USER_PREFERENCES 95PLUGINS template-begin template-end
* check which setting you want to change with
cat /etc/roundcubemail/defaults.inc.php
* Extend the default settings by adding a new template fragment and add your customizations/additions there, eg.:
vim /etc/e-smith/templates/etc/roundcubemail/config/config.inc.php/30my_custom_settings
* Finally, expand the template:
signal-event roundcube-update
Likewise, plugin customization can be done by creating custom template fragments.
For example, to set if and how the "vacation management panel" of the "managesieve" plugin should appear in the Roundcube webmail frontend:
* check the current configuration of the managesieve plugin:
cat /usr/share/roundcubemail/plugins/managesieve/config.inc.php
* check current template fragments for the plugin configuration:
ll /etc/e-smith/templates/usr/share/roundcubemail/plugins/managesieve/config.inc.php/
''...''
''-rw-r--r-- 1 root root 266 30. Nov 19:45 30showvacation''
''...''
* copy the relevant template fragment to /etc/e-smith/templates-custom/... and modify the setting:
mkdir -p /etc/e-smith/templates-custom/usr/share/roundcubemail/plugins/managesieve/config.inc.php
cp /etc/e-smith/templates/usr/share/roundcubemail/plugins/managesieve/config.inc.php/30showvacation /etc/e-smith/templates-custom/usr/share/roundcubemail/plugins/managesieve/config.inc.php/
vim /etc/e-smith/templates-custom/usr/share/roundcubemail/plugins/managesieve/config.inc.php/30showvacation
* Finally, expand the customized template:
signal-event roundcube-update
{{Note box|If you think your setting should be the SME default raise a bug}}
====Add an alternative URL====
If Roundcube should be reachable by an alternative URL to http://yourserver.net/roundcube, eg.
http://yourserver.net/webmail
or
http://yourserver.net/mail
{{warning box|The URL '''/webmail''' is by default used by the horde webmail, so you have to deactivate the webmail in the server-manager's "Configuration" -> "Email" panel if you want to use it for roundcube instead.}}
{{note box|this adds another url, it doesn't remove the default}}
config setprop roundcube URL webmail
or
config setprop roundcube URL mail
To enable your changes run these commands
expand-template /etc/httpd/conf/httpd.conf
sv h /service/httpd-e-smith
*If you want to remove completely the new url
config delprop roundcube URL
then
expand-template /etc/httpd/conf/httpd.conf
sv h /service/httpd-e-smith
===Miscellaneous notes===
====Mail filter support (Sieve)====
Roundcube V1.0 on SME server comes with the managesieve plugin installed and enabled by default. The managesieve plugin adds additional menu items to the settings in Roundcube's webinterface to allow users to define mail filters and vacation messages in a convenient way. However, to make use of these features, the [[Dovecot-extras|smeserver-dovecot-extras]] contrib also has to be installed (this adds sieve script support and a manage sieve daemon to SME server). If these features are not wanted, Roundcube's managesieve plugin should be disabled (reverse [[#Adding additional plugins|Step 5 described above]], ie. remove <tt>managesieve</tt> from the list of installed plugins).
{{Warning box|sieverules has been deprecated and you must only use managesieve}}
=====Troubleshooting=====
* If mails are not correctly filtered by the filters configured in user's roundcube settings, check the following:
** Is [[Dovecot-extras|smeserver-dovecot-extras]] installed and is the sieve service enabled ( <tt>config getprop sieve status</tt> => enabled )? If it is not enabled: <tt>config setprop sieve status enabled</tt>
** Is using sieve deliberately disabled for the user in question ( <tt>db accounts getprop $USER Sieve</tt> => disabled )? If it is disabled: <tt>db accounts setprop $USER Sieve enabled</tt> (Note the capital "S" in Sieve!)
** If [[Mailsorting|smeserver-mailsorting]] is also installed on the server, mails are first filtered by procmail or maildrop before they are handed off to the dovecot delivery agent and sieve filters. Chances are that a rule exists in a user's .procmailrc or .mailfilter file that intercepts all mails before they get to the latter stage in the mail delivery process.
------------------
=== Bugs ===
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-roundcube component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-roundcube|title=this link}}.
* smeserver-roundcube
{{#bugzilla:columns=id,product,version,status,summary |sort=id|order=desc |component=smeserver-roundcube|noresultsmessage="No open bugs found."}}
* roundcubemail_plugins
{{#bugzilla:columns=id,product,version,status,summary |sort=id|order=desc |component=roundcubemail_plugins|noresultsmessage="No open bugs found."}}
[[Category: Contrib/fr]]
[[Category: Webapps]]
[[Category: Dungog]]
[[Category: Mail/fr]]
{{Level|Easy|Les instructions pour installation et l'utilisation de Roundcube peuvent être suivies par un débutant ; la modification des options nécessite une connaissance basique de Linux.}}
{{usefulnote}}
<blockquote style="float: right;">[[File:roundcube.png|250px]]</blockquote><br>
==RoundCube V1.0 pour le serveur SME Koozali==
===Maintaineur===
[mailto:stephdl@de-labrusse.fr stephdl] Stéphane de Labrusse AKA [[User:stephdl|Stephdl]]<br />
{{ #smeversion: smeserver-roundcube }}
{{ #smeversion: roundcubemail_plugins }}
{{ #smeversion: roundcubemail }}
{{ #smeversion: roundcube }}
===Installation===
<tabs container=""><tab name="Pour SME 10">
Ceci nécessite une refonte.
Nous pouvons utiliser le dépôt Remi pour Roundcube en soi.
https://wiki.contribs.org/Remi-roundcube
Il aura besoin de la réécriture du plugin smeserver-roundcube pour php-fpm :
yum install smeserver-extrarepositories-remi-roundcube -y
Pour la version LTS 1.5.3, ajouter ceci :
yum install yum-plugin-versionlock -y
yum versionlock roundcubemail-1.5.3
sinon vous mettrez à jour vers la version 1.6.
yum install smeserver-roundcube --enablerepo=smedev,smecontribs,smetest,remi-roundcube
semble faire l'installation même si vous obtenez une erreur : « Could not open input file: /usr/share/roundcubemail/composer.phar »
</tab><tab name="Pour SME 9">
yum install smeserver-roundcube --enablerepo=smecontribs
Répondre « oui » (y) pour tous les plugins que vous voulez activer
Si vous ne voulez pas redémarrer votre serveur :
signal-event roundcube-update
sinon :
signal-event post-upgrade; signal-event reboot
Mise à jour :
yum upgrade --enablerepo=smecontribs,remi-roundcube
</tab><tab name="Pour SME 8">
==== '''For SME8''' ====
Remember to first configure the two required repositories, [[stephdl]] and [[epel]],
then issue the following command on the SME Server shell:
yum install smeserver-roundcube --enablerepo=epel,stephdl
rcplugin_update.sh
answer yes (y) for all plugins you want to activate
If you do not want to restart your server
signal-event roundcube-update
or
signal-event post-upgrade; signal-event reboot
</tab>
</tabs>
===Désinstallation===
Pour supprimer le paquet, exécutez la commande suivante sur l'interface du serveur SME :
yum remove roundcube smeserver-roundcube smeserver-roundcube_plugins
Pour supprimer la base de données mysql et l'utilisateur, les deux appartenants à RoundCube, voir [[MySQL#Remove a database]] and [[MySQL#Remove a user]]. Il n'y a pas besoin de redémarrer.
===Utilisation===
http://nom_du_serveur/roundcube'' et se connecter avec votre compte utilisateur du serveur SME.
===Journaux===
Les journaux sont disponibles :
* pour sme8
less /opt/roundcube/logs/errors
* pour sme9
less /var/log/roundcubemail/errors
* pour SME 10
===Limiter l'accès à l'interface web===
{{Note box|type=Note : | par défaut, l'interface webmail Roundcube est accessible depuis tout l'internet sans nécessiter une authentication HTTP supplémentaire.}}
L'acès à Roundcube peut être ajusté finement en règlant la propriété correspondante dans la BDD de configuration du serveur SME :
config setprop roundcube PublicAccess OPTION
où « OPTION » est l'un des paramètres suivants :
none => Pas d'acès
local => Réseau local (mot de passe non requis)
local-pw => Réseau local (mot de passe requis)
global => Tout l'Internet (mot de passe non requis, c'est la configuration par défaut de SME)
global-pw => Tout l'Internet (mot de passe requis)
global-pw-remote => Tout l'Internet (mot de passe requis en dehors du réseau local)
Par exemple, pour restreindre l'accès au seul LAN :
config setprop roundcube PublicAccess local
Pour activer ces modifications dans la BDD de configuration, exécutez ensuite ces commandes :
expand-template /etc/httpd/conf/httpd.conf
sv h /service/httpd-e-smith
Note : pour une description générale sur la façon de régler une BDD sur le serveur SME, jeter un œil sur [[Web Application RPM#New DB settings]].
=== Customization ===
====Roundcube plugins====
=====Default plugins shipped with smeserver-roundcube=====
The smeserver-roundcube contrib is shipped with the following plugins already installed and enabled by default:
config getprop roundcube PluginsList
''globaladdressbook,carddav,calendar,libcalendaring,contextmenu,markasjunk,vcard_attachments,newmail_notifier,emoticons,tasklist,managesieve''
=====Installing additional plugins=====
{{Note box|The upstream Roundcube project is currently transitioning from making plugins available through http://trac.roundcube.net/wiki/Plugin_Repository to a new full fledged plugin repository at http://plugins.roundcube.net and a semi-automated plugin installation process. SME server admins are encouraged to use the new style method described below. }}
To install an additional (non-default) Roundcube plugin in SME server roundcube :
'''Step 1:''' Find the plugin page on http://plugins.roundcube.net/packages (eg. http://plugins.roundcube.net/packages/cor/message_highlight)
'''Step 2:''' Take note of the package name and version shown in the 'require:' line right below the title of the plugin's version heading (eg. "cor/message_highlight": "dev-master")
'''Step 3:''' Add the package name and version to the "require:" block in /opt/roundcube/composer.json. Take attention to the comma (,) separator, it is really important!
* for sme8
nano /opt/roundcube/composer.json
* for sme9
nano /usr/share/roundcubemail/composer.json
"require": {
"php": ">=5.3.0",
"roundcube/plugin-installer": ">=0.1.3",
"johndoh/markasjunk2": "dev-release-1.0",
"johndoh/contextmenu": "dev-master",
"johndoh/globaladdressbook": "dev-release-1.0",
"cor/message_highlight": "dev-master"
},
* for sme10 nothing to do there.
'''Step 4:''' after each modification to composer.json, in order to automatically download and install the plugin launch
rcplugin_update.sh
When asked, answer yes to automatically activate the plugin in the current Roundcube configuration.
'''Step 5:''' In order to keep the list of installed plugins persistent when this contrib is updated (ie. configuration templates are expanded again), you *absolutely* need to add the newly installed Roundcube plugin to the "PluginsList" property of "roundcube" in the configuration database of SME server in addition to steps above:
'''Step 5a:''' First show the list of plugins currently in the configuration DB:
config getprop roundcube PluginsList
''PluginsList=globaladdressbook,carddav,calendar,libcalendaring,contextmenu,markasjunk,vcard_attachments,newmail_notifier,emoticons,tasklist,managesieve''
'''Step 5b:''' Add your newly installed plugin to the list (separated by a comma (,) and without spaces) and activate the change:
config setprop roundcube PluginsList globaladdressbook,carddav,calendar,libcalendaring,contextmenu,markasjunk2,vcard_attachments,newmail_notifier,emoticons,tasklist,managesieve,message_highlight
'''Step 5c:''' Activate the changes to the config DB:
signal-event roundcube-update
Step 5 in short, using backticks:
config setprop roundcube PluginsList `config getprop roundcube PluginsList`,message_highlight
signal-event conf-roundcube
To check for updates to plugins already installed, you can at any time issue the following command again:
rcplugin_update.sh
====Customize Roundcube settings====
For special needs you should create your personal template file if you want your config file will not be overwritten by the smeserver-roundcube templates. This also applies to Roundcube plugins in /opt/roundcube/plugins/ which occasionally come with their own config.inc.php or generic config.php.inc.dist which you can use to set default options.
* The config file for Roundcube itself is now templated, so changes need to be made in a new custom template fragment
:*for sme8
ll /etc/e-smith/templates/opt/roundcube/config/config.inc.php/
''10default_host 15Ldap_addressbook 20plugins_configuration template-begin template-end ''
:* for sme9/sme10
ls /etc/e-smith/templates/etc/roundcubemail/config.inc.php/
10SQL_DATABASE 20LOGGING_DEBUGGING 30IMAP 40SMTP 50LDAP 60SYSTEM 70USER_INTERFACE 80ADDRESSBOOKS_SETTINGS 90USER_PREFERENCES 95PLUGINS template-begin template-end
* check which setting you want to change with
cat /etc/roundcubemail/defaults.inc.php
* Extend the default settings by adding a new template fragment and add your customizations/additions there, eg.:
vim /etc/e-smith/templates/etc/roundcubemail/config/config.inc.php/30my_custom_settings
* Finally, expand the template:
signal-event roundcube-update
Likewise, plugin customization can be done by creating custom template fragments.
For example, to set if and how the "vacation management panel" of the "managesieve" plugin should appear in the Roundcube webmail frontend:
* check the current configuration of the managesieve plugin:
cat /usr/share/roundcubemail/plugins/managesieve/config.inc.php
* check current template fragments for the plugin configuration:
ll /etc/e-smith/templates/usr/share/roundcubemail/plugins/managesieve/config.inc.php/
''...''
''-rw-r--r-- 1 root root 266 30. Nov 19:45 30showvacation''
''...''
* copy the relevant template fragment to /etc/e-smith/templates-custom/... and modify the setting:
mkdir -p /etc/e-smith/templates-custom/usr/share/roundcubemail/plugins/managesieve/config.inc.php
cp /etc/e-smith/templates/usr/share/roundcubemail/plugins/managesieve/config.inc.php/30showvacation /etc/e-smith/templates-custom/usr/share/roundcubemail/plugins/managesieve/config.inc.php/
vim /etc/e-smith/templates-custom/usr/share/roundcubemail/plugins/managesieve/config.inc.php/30showvacation
* Finally, expand the customized template:
signal-event roundcube-update
{{Note box|If you think your setting should be the SME default raise a bug}}
====Add an alternative URL====
If Roundcube should be reachable by an alternative URL to http://yourserver.net/roundcube, eg.
http://yourserver.net/webmail
or
http://yourserver.net/mail
{{warning box|The URL '''/webmail''' is by default used by the horde webmail, so you have to deactivate the webmail in the server-manager's "Configuration" -> "Email" panel if you want to use it for roundcube instead.}}
{{note box|this adds another url, it doesn't remove the default}}
config setprop roundcube URL webmail
or
config setprop roundcube URL mail
To enable your changes run these commands
expand-template /etc/httpd/conf/httpd.conf
sv h /service/httpd-e-smith
*If you want to remove completely the new url
config delprop roundcube URL
then
expand-template /etc/httpd/conf/httpd.conf
sv h /service/httpd-e-smith
===Miscellaneous notes===
====Mail filter support (Sieve)====
Roundcube V1.0 on SME server comes with the managesieve plugin installed and enabled by default. The managesieve plugin adds additional menu items to the settings in Roundcube's webinterface to allow users to define mail filters and vacation messages in a convenient way. However, to make use of these features, the [[Dovecot-extras|smeserver-dovecot-extras]] contrib also has to be installed (this adds sieve script support and a manage sieve daemon to SME server). If these features are not wanted, Roundcube's managesieve plugin should be disabled (reverse [[#Adding additional plugins|Step 5 described above]], ie. remove <tt>managesieve</tt> from the list of installed plugins).
{{Warning box|sieverules has been deprecated and you must only use managesieve}}
=====Troubleshooting=====
* If mails are not correctly filtered by the filters configured in user's roundcube settings, check the following:
** Is [[Dovecot-extras|smeserver-dovecot-extras]] installed and is the sieve service enabled ( <tt>config getprop sieve status</tt> => enabled )? If it is not enabled: <tt>config setprop sieve status enabled</tt>
** Is using sieve deliberately disabled for the user in question ( <tt>db accounts getprop $USER Sieve</tt> => disabled )? If it is disabled: <tt>db accounts setprop $USER Sieve enabled</tt> (Note the capital "S" in Sieve!)
** If [[Mailsorting|smeserver-mailsorting]] is also installed on the server, mails are first filtered by procmail or maildrop before they are handed off to the dovecot delivery agent and sieve filters. Chances are that a rule exists in a user's .procmailrc or .mailfilter file that intercepts all mails before they get to the latter stage in the mail delivery process.
------------------
=== Bugs ===
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-roundcube component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-roundcube|title=this link}}.
* smeserver-roundcube
{{#bugzilla:columns=id,product,version,status,summary |sort=id|order=desc |component=smeserver-roundcube|noresultsmessage="No open bugs found."}}
* roundcubemail_plugins
{{#bugzilla:columns=id,product,version,status,summary |sort=id|order=desc |component=roundcubemail_plugins|noresultsmessage="No open bugs found."}}
[[Category: Contrib/fr]]
[[Category: Webapps]]
[[Category: Dungog]]
[[Category: Mail/fr]]
