centos:mail_c7:roundcube_1

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen Revision Vorhergehende Überarbeitung
Nächste Überarbeitung		 Vorhergehende Überarbeitung
centos:mail_c7:roundcube_1 [09.09.2014 21:08. ] – [Installations-/Konfigurationsdokumentation] djangocentos:mail_c7:roundcube_1 [18.11.2024 19:10. ] (aktuell) – Externe Bearbeitung 127.0.0.1
Zeile 13: Zeile 13:
    # yum install php-pspell aspell-de php-mcrypt GraphicsMagick -y    # yum install php-pspell aspell-de php-mcrypt GraphicsMagick -y
  
-Für die deutsche Rechtschreibkorrektur gibt es im [[centos:epel7|EPEL-Repository]] für CentOS 7.x (noch)((Stand: September 2014)) kein RPM. Abhilfe schafft hier das [[centos:mailserver.guru|Repository mailserver.guru]]. Haben wir das **[[centos:mailserver.guru|mailserver.guru Repository]]** eingebunden wir das Paket **aspell-de** automatisch bei der Installation mit dem obigen Aufruf installiert.+Für die deutsche Rechtschreibkorrektur gibt es im [[centos:epel7|EPEL-Repository]] für CentOS 7.x (noch)((Stand: September 2014)) kein RPM. Abhilfe schafft hier das [[centos:nausch.org|Repository nausch.org]]. Haben wir das **[[centos:nausch.org|nausch.org Repository]]** eingebunden wir das Paket **aspell-de** automatisch bei der Installation mit dem obigen Aufruf installiert.
  
-Alternativ kann man natürlich acu das Paket manuell installieren. Hierzu laden wir das Paket [[http://repo.mailserver.guru/7/x86_64/aspell-de-20030222-1.el7.centos.x86_64.rpm|aspell-de-20030222-1.el7.centos.x86_64.rpm]] auf unseren Rechner.+Alternativ kann man natürlich acu das Paket manuell installieren. Hierzu laden wir das Paket [[http://repo.nausch.org/7/x86_64/aspell-de-20030222-1.el7.centos.x86_64.rpm|aspell-de-20030222-1.el7.centos.x86_64.rpm]] auf unseren Rechner.
    # cd /usr/local/src/packages/    # cd /usr/local/src/packages/
  
-   # wget http://repo.mailserver.guru/7/x86_64/aspell-de-20030222-1.el7.centos.x86_64.rpm+   # wget http://repo.nausch.org/7/x86_64/aspell-de-20030222-1.el7.centos.x86_64.rpm
  
 Anschließend installieren wir dieses RPM mit Hilfe von **yum**. Anschließend installieren wir dieses RPM mit Hilfe von **yum**.
Zeile 29: Zeile 29:
    # yum install roundcubemail -y    # yum install roundcubemail -y
  
-===== Konfiguration ===== +==== Installations-/Konfigurationsdokumentation ====
-==== Apachekonfig aus dem RPM ==== +
-Da wir einen eigenen vHOST für den WEB-Mailer anbieten wollen und keine Unterverzeichniss-Konfiguration, kommentieren wir den Inhalt der Apache-Konfigurationsdatei //**/etc/httpd/conf.d/roundcubemail.conf**// aus. +
-   # vim /etc/httpd/conf.d/roundcubemail.conf +
- +
-<file apache /etc/httpd/conf.d/roundcubemail.conf>## +
-## Round Cube Webmail is a browser-based multilingual IMAP client +
-## +
-# +
-#Alias /roundcubemail /usr/share/roundcubemail +
-# +
-## Define who can access the Webmail +
-## You can enlarge permissions once configured +
-# +
-#<Directory /usr/share/roundcubemail/> +
-#    <IfModule mod_authz_core.c> +
-#        # Apache 2.4 +
-#        Require local +
-#    </IfModule> +
-#    <IfModule !mod_authz_core.c> +
-#        # Apache 2.2 +
-#        Order Deny,Allow +
-#        Deny from all +
-#        Allow from 127.0.0.1 +
-#        Allow from ::1 +
-#    </IfModule> +
-#</Directory> +
-# +
-## Define who can access the installer +
-## keep this secured once configured +
-# +
-#<Directory /usr/share/roundcubemail/installer/> +
-#    <IfModule mod_authz_core.c> +
-#        # Apache 2.4 +
-#        Require local +
-#    </IfModule> +
-#    <IfModule !mod_authz_core.c> +
-#        # Apache 2.2 +
-#        Order Deny,Allow +
-#        Deny from all +
-#        Allow from 127.0.0.1 +
-#        Allow from ::1 +
-#    </IfModule> +
-#</Directory> +
-# +
-## Those directories should not be viewed by Web clients. +
-#<Directory /usr/share/roundcubemail/bin/> +
-#    Order Allow,Deny +
-#    Deny from all +
-#</Directory> +
-#<Directory /usr/share/roundcubemail/plugins/enigma/home/> +
-#    Order Allow,Deny +
-#    Deny from all +
-#</Directory> +
-</file> +
- +
- +
-==== Apache vHost ==== +
-Für unsere Webmailer richten wir uns nun einen geeigneten vHost ein. Im Konfigurationsverzeichnis unseres [[centos:web_c7:apache_1|Apache-Webservers]] legen wir uns eine neue vHOST-Konfigurationsdatei an. +
-   # vim /etc/httpd/conf.d/vhost_443_roundcubemail.conf +
-<file apache /etc/httpd/conf.d/vhost_443_roundcubemail.conf># +
-# roundcubemail.sec-mail.guru +
-# +
-<VirtualHost *:80> +
-        ServerAdmin webmaster@nausch.org +
-        ServerName roundcubemail.sec-mail.guru +
-        ServerPath / +
- +
-        <Location /> +
-                Options -Indexes +FollowSymLinks +
-                Require all granted +
-        </Location> +
- +
-        RewriteEngine on +
-        RewriteCond %{HTTPS} off +
-        RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} +
- +
-        DirectoryIndex index.php +
- +
-        ErrorLog logs/roundcubemail_error.log +
-        CustomLog logs/roundcubemail_access.log combined +
-</VirtualHost> +
-<VirtualHost *:443> +
-        ServerAdmin webmaster@nausch.org +
-        ServerName roundcubemail.sec-mail.guru +
-        ServerPath / +
-        DocumentRoot "/usr/share/roundcubemail" +
- +
-        # Django +
-        # Required, because there is a host with same ServerName and +
-        # ServerAlias LISTENING ON PORT 80, - and if these lines are +
-        # not present, and .htaccess-Files or LDAP-Access is enabled +
-        # for one or more Directory the host on PORT 443 and PORT 80 +
-        # will ASK for .htaccess ord LDAP-Access, so please remember +
-        # ---------------------------------------------------------- +
-        # -- DO NOT DELETE THE FOLLOWING LINES, STARTING WITH SSL -- +
-        # --         WHEN USING .htaccess or LDAP-Access!         -- +
-        # ---------------------------------------------------------- +
-        SSLEngine on +
-        SSLProtocol -ALL +SSLv3 +TLSv1 +
-        SSLCipherSuite EECDH+AES256:DHE+AES256:EECDH+AES:EDH+AES:-SHA1:EECDH+RC4:EDH+RC4:RC4-SHA:AES256-SHA:!aNULL:!eNULL:!EXP:!LOW:!MD5 +
-        SSLHonorCipherOrder on +
-        SSLCertificateFile /etc/pki/tls/private/CAcert-class3-wildcard.crt +
-        SSLCertificateKeyFile /etc/pki/tls/private/ca.key +
-        SSLCertificateChainFile /etc/pki/tls/private/CAcert_chain.crt +
- +
-        # Define who can access the Webmail +
-        # You can enlarge permissions once configured +
-        <Directory /usr/share/roundcubemail/> +
-                <IfModule mod_authz_core.c> +
-                # before configuration +
-                Require local +
-                # after configuration +
-                # Require all granted +
-                </IfModule> +
-        </Directory> +
- +
-        # Define who can access the installer +
-        # keep this secured once configured +
-        <Directory /usr/share/roundcubemail/installer/> +
-                <IfModule mod_authz_core.c> +
-                # while configuration +
-                Require host nausch.org +
-                # after configuration +
-                # Require local +
-                </IfModule> +
-        </Directory> +
- +
-        # Those directories should not be viewed by Web clients. +
-        <Directory /usr/share/roundcubemail/bin/> +
-                Require all denied +
-        </Directory> +
-        <Directory /usr/share/roundcubemail/plugins/enigma/home/> +
-                Require all denied +
-        </Directory> +
- +
-        DirectoryIndex index.php +
-        ErrorLog logs/postfixadmin_error.log +
-        CustomLog logs/postfixadmin_access.log combined +
-</VirtualHost> +
-</file> +
- +
-<WRAP round important>**Wichtig:** +
- +
-Solange wir unseren vHost noch nicht in der Produktionsumgebung steht und fertig konfiguriert wurde, beschränken wir den Zugriff auf den vHost noch. In der obigen Apache-vHOST ist dies bereits berücksichtigt! +
- +
-Erst nach erfolgter Konfiguration geben wir den vHOST für unsere Nutzer frei; hierzu tragen wir in der **Directive //Directory//** wie folgt ab: +
-<code apache>... +
- +
-        # Define who can access the Webmail +
-        # You can enlarge permissions once configured +
- +
-        <Directory /usr/share/roundcubemail/> +
-                <IfModule mod_authz_core.c> +
-                # before configuration +
-                # Require local +
-                # after configuration +
-                Require all granted +
-                </IfModule> +
-        </Directory> +
- +
- +
-        # Define who can access the installer +
-        # keep this secured once configured +
-        <Directory /usr/share/roundcubemail/installer/> +
-                <IfModule mod_authz_core.c> +
-                # while configuration +
-                # Require host 10.0.0 +
-                # after configuration +
-                Require local +
-                </IfModule> +
-        </Directory> +
- +
-... +
-</code> +
-</WRAP> +
- +
-Bevor unseren Webserver starten, damit der neue vHost auch bedient werden kann, überprüfen wir die Konfiguration noch auf syntaktische Fehler.  +
-   # apachectl -t +
- +
-Ist alles O.K. dann steht einem Reload des Apache httpd nichts mehr im Wege. +
-   # systemctl reload httpd.service +
- +
-Wollen wir den Reload kontrollieren, fragen wir den Status des Webservers ab. +
-   # systemctl status httpd.service +
- +
-<code>httpd.service - The Apache HTTP Server +
-   Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled) +
-   Active: active (running) since Tue 2014-09-09 18:26:47 CEST; 3h 48min ago +
-  Process: 20019 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=0/SUCCESS) +
-  Process: 20368 ExecReload=/usr/sbin/httpd $OPTIONS -k graceful (code=exited, status=0/SUCCESS) +
- Main PID: 20024 (httpd) +
-   Status: "Total requests: 0; Current requests/sec: 0; Current traffic:   0 B/sec" +
-   CGroup: /system.slice/httpd.service +
-           ├─20024 /usr/sbin/httpd -DFOREGROUND +
-           ├─20372 /usr/sbin/httpd -DFOREGROUND +
-           ├─20373 /usr/sbin/httpd -DFOREGROUND +
-           ├─20374 /usr/sbin/httpd -DFOREGROUND +
-           ├─20375 /usr/sbin/httpd -DFOREGROUND +
-           └─20376 /usr/sbin/httpd -DFOREGROUND +
- +
-Sep 09 22:15:07 vml000097.dmz.nausch.org systemd[1]: Reloading The Apache HTTP Server. +
-Sep 09 22:15:07 vml000097.dmz.nausch.org systemd[1]: Reloaded The Apache HTTP Server. +
-</code> +
- +
-===== Installations-/Konfigurationsdokumentation =====+
 Im RPM finden wir eine ausführliche Dokumentation zur Konfiguration von **roundcubemail**  Im RPM finden wir eine ausführliche Dokumentation zur Konfiguration von **roundcubemail** 
    # cat /usr/share/doc/roundcubemail-1.0.2/INSTALL    # cat /usr/share/doc/roundcubemail-1.0.2/INSTALL
  
-<file bash /usr/share/doc/roundcubemail-1.0.2/INSTALL>INTRODUCTION+<file /usr/share/doc/roundcubemail-1.0.2/INSTALL>INTRODUCTION
 ============ ============
  
Zeile 481: Zeile 276:
 in main configuration file. ESEARCH implementation in this server is broken (#1489184). in main configuration file. ESEARCH implementation in this server is broken (#1489184).
 </file> </file>
 +
 +===== Konfiguration =====
 +==== Apachekonfig aus dem RPM ====
 +Da wir einen eigenen vHOST für den WEB-Mailer anbieten wollen und keine Unterverzeichniss-Konfiguration, kommentieren wir den Inhalt der Apache-Konfigurationsdatei //**/etc/httpd/conf.d/roundcubemail.conf**// aus.
 +   # vim /etc/httpd/conf.d/roundcubemail.conf
 +
 +<file apache /etc/httpd/conf.d/roundcubemail.conf>##
 +## Round Cube Webmail is a browser-based multilingual IMAP client
 +##
 +#
 +#Alias /roundcubemail /usr/share/roundcubemail
 +#
 +## Define who can access the Webmail
 +## You can enlarge permissions once configured
 +#
 +#<Directory /usr/share/roundcubemail/>
 +#    <IfModule mod_authz_core.c>
 +#        # Apache 2.4
 +#        Require local
 +#    </IfModule>
 +#    <IfModule !mod_authz_core.c>
 +#        # Apache 2.2
 +#        Order Deny,Allow
 +#        Deny from all
 +#        Allow from 127.0.0.1
 +#        Allow from ::1
 +#    </IfModule>
 +#</Directory>
 +#
 +## Define who can access the installer
 +## keep this secured once configured
 +#
 +#<Directory /usr/share/roundcubemail/installer/>
 +#    <IfModule mod_authz_core.c>
 +#        # Apache 2.4
 +#        Require local
 +#    </IfModule>
 +#    <IfModule !mod_authz_core.c>
 +#        # Apache 2.2
 +#        Order Deny,Allow
 +#        Deny from all
 +#        Allow from 127.0.0.1
 +#        Allow from ::1
 +#    </IfModule>
 +#</Directory>
 +#
 +## Those directories should not be viewed by Web clients.
 +#<Directory /usr/share/roundcubemail/bin/>
 +#    Order Allow,Deny
 +#    Deny from all
 +#</Directory>
 +#<Directory /usr/share/roundcubemail/plugins/enigma/home/>
 +#    Order Allow,Deny
 +#    Deny from all
 +#</Directory>
 +</file>
 +
 +
 +==== Apache vHost ====
 +Für unsere Webmailer richten wir uns nun einen geeigneten vHost ein. Im Konfigurationsverzeichnis unseres [[centos:web_c7:apache_1|Apache-Webservers]] legen wir uns eine neue vHOST-Konfigurationsdatei an.
 +   # vim /etc/httpd/conf.d/vhost_443_roundcubemail.conf
 +<file apache /etc/httpd/conf.d/vhost_443_roundcubemail.conf>#
 +# roundcubemail.sec-mail.guru
 +#
 +<VirtualHost *:80>
 +        ServerAdmin webmaster@nausch.org
 +        ServerName roundcubemail.sec-mail.guru
 +        ServerPath /
 +
 +        <Location />
 +                Options -Indexes +FollowSymLinks
 +                Require all granted
 +        </Location>
 +
 +        RewriteEngine on
 +        RewriteCond %{HTTPS} off
 +        RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
 +
 +        DirectoryIndex index.php
 +
 +        ErrorLog logs/roundcubemail_error.log
 +        CustomLog logs/roundcubemail_access.log combined
 +</VirtualHost>
 +<VirtualHost *:443>
 +        ServerAdmin webmaster@nausch.org
 +        ServerName roundcubemail.sec-mail.guru
 +        ServerPath /
 +        DocumentRoot "/usr/share/roundcubemail"
 +
 +        # Django
 +        # Required, because there is a host with same ServerName and
 +        # ServerAlias LISTENING ON PORT 80, - and if these lines are
 +        # not present, and .htaccess-Files or LDAP-Access is enabled
 +        # for one or more Directory the host on PORT 443 and PORT 80
 +        # will ASK for .htaccess ord LDAP-Access, so please remember
 +        # ----------------------------------------------------------
 +        # -- DO NOT DELETE THE FOLLOWING LINES, STARTING WITH SSL --
 +        # --         WHEN USING .htaccess or LDAP-Access!         --
 +        # ----------------------------------------------------------
 +        SSLEngine on
 +        SSLProtocol -ALL +SSLv3 +TLSv1
 +        SSLCipherSuite EECDH+AES256:DHE+AES256:EECDH+AES:EDH+AES:-SHA1:EECDH+RC4:EDH+RC4:RC4-SHA:AES256-SHA:!aNULL:!eNULL:!EXP:!LOW:!MD5
 +        SSLHonorCipherOrder on
 +        SSLCertificateFile /etc/pki/tls/private/CAcert-class3-wildcard.crt
 +        SSLCertificateKeyFile /etc/pki/tls/private/ca.key
 +        SSLCertificateChainFile /etc/pki/tls/private/CAcert_chain.crt
 +
 +        # Define who can access the Webmail
 +        # You can enlarge permissions once configured
 +        <Directory /usr/share/roundcubemail/>
 +                <IfModule mod_authz_core.c>
 +                # before configuration
 +                Require local
 +                # after configuration
 +                # Require all granted
 +                </IfModule>
 +        </Directory>
 +
 +        # Define who can access the installer
 +        # keep this secured once configured
 +        <Directory /usr/share/roundcubemail/installer/>
 +                <IfModule mod_authz_core.c>
 +                # while configuration
 +                Require host nausch.org
 +                # after configuration
 +                # Require local
 +                </IfModule>
 +        </Directory>
 +
 +        # Those directories should not be viewed by Web clients.
 +        <Directory /usr/share/roundcubemail/bin/>
 +                Require all denied
 +        </Directory>
 +        <Directory /usr/share/roundcubemail/plugins/enigma/home/>
 +                Require all denied
 +        </Directory>
 +
 +        DirectoryIndex index.php
 +        ErrorLog logs/postfixadmin_error.log
 +        CustomLog logs/postfixadmin_access.log combined
 +</VirtualHost>
 +</file>
 +
 +<WRAP round important>**Wichtig:**
 +
 +Solange wir unseren vHost noch nicht in der Produktionsumgebung steht und fertig konfiguriert wurde, beschränken wir den Zugriff auf den vHost noch. In der obigen Apache-vHOST ist dies bereits berücksichtigt!
 +
 +Erst nach erfolgter Konfiguration geben wir den vHOST für unsere Nutzer frei; hierzu tragen wir in der **Directive //Directory//** wie folgt ab:
 +<code apache>...
 +
 +        # Define who can access the Webmail
 +        # You can enlarge permissions once configured
 +
 +        <Directory /usr/share/roundcubemail/>
 +                <IfModule mod_authz_core.c>
 +                # before configuration
 +                # Require local
 +                # after configuration
 +                Require all granted
 +                </IfModule>
 +        </Directory>
 +
 +
 +        # Define who can access the installer
 +        # keep this secured once configured
 +        <Directory /usr/share/roundcubemail/installer/>
 +                <IfModule mod_authz_core.c>
 +                # while configuration
 +                # Require host 10.0.0
 +                # after configuration
 +                Require local
 +                </IfModule>
 +        </Directory>
 +
 +...
 +</code>
 +</WRAP>
 +
 +Bevor unseren Webserver starten, damit der neue vHost auch bedient werden kann, überprüfen wir die Konfiguration noch auf syntaktische Fehler. 
 +   # apachectl -t
 +
 +Ist alles O.K. dann steht einem Reload des Apache httpd nichts mehr im Wege.
 +   # systemctl reload httpd.service
 +
 +Wollen wir den Reload kontrollieren, fragen wir den Status des Webservers ab.
 +   # systemctl status httpd.service
 +
 +<code>httpd.service - The Apache HTTP Server
 +   Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled)
 +   Active: active (running) since Tue 2014-09-09 18:26:47 CEST; 3h 48min ago
 +  Process: 20019 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=0/SUCCESS)
 +  Process: 20368 ExecReload=/usr/sbin/httpd $OPTIONS -k graceful (code=exited, status=0/SUCCESS)
 + Main PID: 20024 (httpd)
 +   Status: "Total requests: 0; Current requests/sec: 0; Current traffic:   0 B/sec"
 +   CGroup: /system.slice/httpd.service
 +           ├─20024 /usr/sbin/httpd -DFOREGROUND
 +           ├─20372 /usr/sbin/httpd -DFOREGROUND
 +           ├─20373 /usr/sbin/httpd -DFOREGROUND
 +           ├─20374 /usr/sbin/httpd -DFOREGROUND
 +           ├─20375 /usr/sbin/httpd -DFOREGROUND
 +           └─20376 /usr/sbin/httpd -DFOREGROUND
 +
 +Sep 09 22:15:07 vml000097.dmz.nausch.org systemd[1]: Reloading The Apache HTTP Server.
 +Sep 09 22:15:07 vml000097.dmz.nausch.org systemd[1]: Reloaded The Apache HTTP Server.
 +</code>
 +
  
 ==== mySQL Datenbank ==== ==== mySQL Datenbank ====
Zeile 579: Zeile 580:
    Enter password:     Enter password: 
  
-==== Datenbank-Anbindung ==== +==== PHP Date.Timezone ==== 
-Damit roundcube später auf unsere Datenbank auch zugreifen kann, definieren wir nun die Datenbankanbindung von roundcube an unseren MySQL-Datenbank-Server.+Damit der Installer später nicht beklagt, dass keine **date.timezone** gesetzt ist, kontrollieren wir noch kurz die Einstellungen in der Datei //**/etc/php.ini**//. 
 +   # vim /etc/php.ini 
 + 
 +<code php>... 
 + 
 +[Date] 
 +; Defines the default timezone used by the date functions 
 +; http://php.net/date.timezone 
 +; Django : 2014-09-09 
 +; default: ;date.timezone = 
 +date.timezone = "Europe/Berlin" 
 + 
 +; http://php.net/date.default-latitude 
 +;date.default_latitude = 31.7667 
 + 
 +; http://php.net/date.default-longitude 
 +;date.default_longitude = 35.2333 
 + 
 +; http://php.net/date.sunrise-zenith 
 +;date.sunrise_zenith = 90.583333 
 + 
 +; http://php.net/date.sunset-zenith 
 +;date.sunset_zenith = 90.583333 
 + 
 +... 
 +</code> 
 + 
 +Haben wir eine Änderung vorgenommen, veranlassen wir zur Aktivierung der Option einen Reload des http-Daemon. 
 +   # systemctl reload httpd.service 
 + 
 +==== Roundcube Konfiguration ==== 
 +Die Konfiguration von Roundcube erfolgt über die zentrale Konfigurationsdatei **config.inc.php** im Verzeichnis //**/etc/roundcubemail/**//. 
 + 
 +Die einfachste Variante diese Konfigurationsdatei zu erstellen ist über die WEB-GUI. Alternativ kann man natürlich auch die Datei direkt per Hand installieren. Werfen wir zu erst einmal einen Blick auf die Konfiguration mit Hilfe der WEB-GUI; hierzu rufen wir die **/installer**-URL auf. 
 +   $ firefox https://roundcubemail.sec-mail/installer/ 
 + 
 +{{ :centos:mail_c7:roundcubemail_01.png?direct&850 |Bild: Bildschirmhardcopy des Roundcube Installers (WEB-GUI) "Check environment"}} 
 + 
 +Auf der ersten Seite **//Check environment//** wird geprüft, ob die notwendigen Voraussetzungen gegeben sind. Wird ein Punkt beanstandet, kann man entsprechend eingreifen und den Fehler beheben. Passt alles, klickt man auf die Schaltfläche **[ NEXT ]** und man gelangt zum Schritt 2: **//Create config//**. 
 + 
 +{{ :centos:mail_c7:roundcubemail_02.png?direct&850 |Bild: Bildschirmhardcopy des Roundcube Installers (WEB-GUI) "Create config"}} 
 + 
 +Hat man alle Angaben für die Konfiguration unseres WEB-Mailers eingetragen, klicken wir auf die Schaltfläche **[ CREATE CONFIG ]** um die Konfigurationsdatei online zu erstellen. 
 + 
 +{{ :centos:mail_c7:roundcubemail_03.png?direct&850 |Bild: Bildschirmhardcopy des Roundcube Installers (WEB-GUI) "Create config"}} 
 + 
 +Hier haben wir zwei Möglichkeiten. Entweder wir kopieren den Text direkt aus dem Anzeigefenster und fügen den kopierten Text dann in die Datei //**/etc/roundcubemail/config.inc.php**// oder wir klicken auf die Schaltfläche **[ Download ]** und kopieren die Datei dann mit Hilfe von **scp** auf den Webserver. 
 + 
 +   # less /etc/roundcubemail/config.inc.php  
 +<file php /etc/roundcubemail/config.inc.php><?php                                                                                                                                                                             
 + 
 +/* Local configuration for Roundcube Webmail */ 
 + 
 +// ---------------------------------- 
 +// SQL DATABASE 
 +// ---------------------------------- 
 +// Database connection string (DSN) for read+write operations 
 +// Format (compatible with PEAR MDB2): db_provider://user:password@host/database 
 +// Currently supported db_providers: mysql, pgsql, sqlite, mssql or sqlsrv 
 +// For examples see http://pear.php.net/manual/en/package.database.mdb2.intro-dsn.php 
 +// NOTE: for SQLite use absolute path: 'sqlite:////full/path/to/sqlite.db?mode=0646' 
 +$config['db_dsnw'] = 'mysql://roundcube_user:n491o5rbgsDK67DeM9sCHfzd@mysql.dmz.nausch.org/roundcubemail'; 
 + 
 +// ---------------------------------- 
 +// IMAP 
 +// ---------------------------------- 
 +// The mail host chosen to perform the log-in. 
 +// Leave blank to show a textbox at login, give a list of hosts 
 +// to display a pulldown menu or set one host as string. 
 +// To use SSL/TLS connection, enter hostname with prefix ssl:// or tls:// 
 +// Supported replacement variables: 
 +// %n - hostname ($_SERVER['SERVER_NAME']) 
 +// %t - hostname without the first part 
 +// %d - domain (http hostname $_SERVER['HTTP_HOST'] without the first part) 
 +// %s - domain name after the '@' from e-mail address provided at login screen 
 +// For example %n = mail.domain.tld, %t = domain.tld 
 +// WARNING: After hostname change update of mail_host column in users table is 
 +//          required to match old user data records with the new host. 
 +$config['default_host'] = 'tls://imap.nausch.org'; 
 + 
 +// ---------------------------------- 
 +// SMTP 
 +// ---------------------------------- 
 +// SMTP server host (for sending mails). 
 +// To use SSL/TLS connection, enter hostname with prefix ssl:// or tls:// 
 +// If left blank, the PHP mail() function is used 
 +// Supported replacement variables: 
 +// %h - user's IMAP hostname 
 +// %n - hostname ($_SERVER['SERVER_NAME']) 
 +// %t - hostname without the first part 
 +// %d - domain (http hostname $_SERVER['HTTP_HOST'] without the first part) 
 +// %z - IMAP domain (IMAP hostname without the first part) 
 +// For example %n = mail.domain.tld, %t = domain.tld 
 +$config['smtp_server'] = 'smtp.dmz.nausch.org'; 
 + 
 +// provide an URL where a user can get support for this Roundcube installation 
 +// PLEASE DO NOT LINK TO THE ROUNDCUBE.NET WEBSITE HERE! 
 +$config['support_url'] = 'https://dokuwiki.nausch.org/doku.php/centos:mail_c7:start'; 
 + 
 +// automatically create a new Roundcube user when log-in the first time. 
 +// a new user will be created once the IMAP login succeeds. 
 +// set to false if only registered users can use this service 
 +$config['auto_create_user'] = true; 
 + 
 +// this key is used to encrypt the users imap password which is stored 
 +// in the session record (and the client cookie if remember password is enabled). 
 +// please provide a string of exactly 24 chars. 
 +$config['des_key'] = 'x5-Lx+B!1i?EElMdyPUE4t_6'; 
 + 
 +// ---------------------------------- 
 +// PLUGINS 
 +// ---------------------------------- 
 +// List of active plugins (in plugins/ directory) 
 +$config['plugins'] = array( ); 
 + 
 +// the default locale setting (leave empty for auto-detection) 
 +// RFC1766 formatted language name like en_US, de_DE, de_CH, fr_FR, pt_BR 
 +$config['language'] = 'de_DE'; 
 + 
 +// store spam messages in this mailbox 
 +// NOTE: Use folder names with namespace prefix (INBOX. on Courier-IMAP) 
 +$config['junk_mbox'] = ''; 
 + 
 +// display these folders separately in the mailbox list. 
 +// these folders will also be displayed with localized names 
 +// NOTE: Use folder names with namespace prefix (INBOX. on Courier-IMAP) 
 +$config['default_folders'] = array('INBOX', 'Drafts', 'Sent', '', 'Trash'); 
 + 
 +// Set the spell checking engine. Possible values: 
 +// - 'googie'  - the default 
 +// - 'pspell'  - requires the PHP Pspell module and aspell installed 
 +// - 'enchant' - requires the PHP Enchant module 
 +// - 'atd'     - install your own After the Deadline server or check with the people at http://www.afterthedeadline.com before using their API 
 +// Since Google shut down their public spell checking service, you need to  
 +// connect to a Nox Spell Server when using 'googie' here. Therefore specify the 'spellcheck_uri' 
 +$config['spellcheck_engine'] = 'pspell'; 
 + 
 +// prefer displaying HTML messages 
 +$config['prefer_html'] = false; 
 + 
 +// Encoding of long/non-ascii attachment names: 
 +// 0 - Full RFC 2231 compatible 
 +// 1 - RFC 2047 for 'name' and RFC 2231 for 'filename' parameter (Thunderbird's default) 
 +// 2 - Full 2047 compatible 
 +$config['mime_param_folding'] = 0; 
 + 
 + 
 +</file> 
 + 
 +Anschließend passen wir noch die Dateirechte der konfigurationsdatei an. 
 +   # chmod 640 /etc/roundcubemail/config.inc.php 
 + 
 +   # chown root.apache /etc/roundcubemail/config.inc.php 
 + 
 +Nun können wir auf der WEB-GUI die Schaltfläche **[ CONTINUE ]** anklicken um zum dritten Schritt //**Test config**// zu gelangen. 
 + 
 + 
 +{{ :centos:mail_c7:roundcubemail_04.png?direct&850 |Bild: Bildschirmhardcopy des Roundcube Installers (WEB-GUI) "Test config"}} 
 + 
 +Sind alle Tests bestanden, können wir den **installer** deaktivieren und die Anwendung für den abschließenden Test "Anmeldung als User an unserem neunen Webmailer. 
 + 
 +<WRAP round tip> 
 +Wir ändern nun die **Directive //Directory//** in der Konfigurationsdatei //**/etc/httpd/conf.d/vhost_443_roundcubemail.conf**// die entsprechenden Einträge ab. 
 +<code> # vim /etc/httpd/conf.d/vhost_443_roundcubemail.conf</code> <code apache>... 
 + 
 +        # Define who can access the Webmail 
 +        # You can enlarge permissions once configured 
 + 
 +        <Directory /usr/share/roundcubemail/> 
 +                <IfModule mod_authz_core.c> 
 +                # before configuration 
 +                # Require local 
 +                # after configuration 
 +                Require all granted 
 +                </IfModule> 
 +        </Directory> 
 + 
 + 
 +        # Define who can access the installer 
 +        # keep this secured once configured 
 +        <Directory /usr/share/roundcubemail/installer/> 
 +                <IfModule mod_authz_core.c> 
 +                # while configuration 
 +                # Require host 10.0.0 
 +                # after configuration 
 +                Require local 
 +                </IfModule> 
 +        </Directory> 
 + 
 +... 
 +</code> Anschließend führen wir einen Reload des HTTP-Daemon durch, damit die Änderung der Zugriffsrechte aktiv wird. <code> # systemctl reload httpd.service</code> 
 +</WRAP> 
 + 
 +Ob die Sperrung des **installer** passt, kontrollieren wir einfach durch einen erneuten Aufruf der betreffenden URL. 
 +   $ firefox https://roundcubemail.sec-mail/installer/ 
 + 
 +{{ :centos:mail_c7:roundcubemail_05.png?direct&700 |Bild: Bildschirmhardcopy des gesperrten Roundcube Installers (WEB-GUI)}} 
 + 
 +Test eins ist schon mal bestanden, wir rufen also als nächstes die URL unseres Webmailers auf. 
 +   $ firefox https://roundcubemail.sec-mail 
 + 
 +{{ :centos:mail_c7:roundcubemail_06.png?direct&850 |Bild: Bildschirmhardcopy der Loginmaske des Roundcube Webmailers}} 
 + 
 +Wir erreichen die Anmeldemaske und nun steht nur noch der Test an, ob wir uns auch anmelden können. 
 + 
 + 
 +{{ :centos:mail_c7:roundcubemail_07.png?direct&850 |Bild: Bildschirmhardcopy des Roundcube Webmailers (bei erfolgreichem Login)}} 
 + 
 +===== Plugins ===== 
 +Mit Hilfe von Plugins kann Roundcube um verschiedene Funktionen und Fähigkeiten erweitert werden. Bei der Installation des RPM wurden bereits alle Plugins in das Verzeichnis //**/usr/share/roundcubemail/plugins/**// kopiert. Einen Überblick verschaffen wir uns mit einem Blick in das betreffende Verzeichnis. 
 +   # /usr/share/roundcubemail/plugins/ 
 + 
 +<code>/usr/share/roundcubemail/plugins/ 
 +├── acl 
 +├── additional_message_headers 
 +├── archive 
 +├── attachment_reminder 
 +├── autologon 
 +├── database_attachments 
 +├── debug_logger 
 +├── emoticons 
 +├── enigma 
 +├── example_addressbook 
 +├── filesystem_attachments 
 +├── help 
 +├── hide_blockquote 
 +├── http_authentication 
 +├── identity_select 
 +├── jqueryui 
 +├── managesieve 
 +├── markasjunk 
 +├── newmail_notifier 
 +├── new_user_dialog 
 +├── new_user_identity 
 +├── password 
 +├── redundant_attachments 
 +├── show_additional_headers 
 +├── squirrelmail_usercopy 
 +├── subscriptions_option 
 +├── userinfo 
 +├── vcard_attachments 
 +├── virtuser_file 
 +├── virtuser_query 
 +└── zipdownload 
 +</code> 
 + 
 +In unserem konfigurationsbeispiel beschränken wir uns dabei auf die drei wichtigsten Plugins, nämlich **Password** und **Managesieve** und **ACL**. Hierzu tragen wir die drei Plugins bei der Konfigurations-Array **plugins** ein. 
 + 
 +   # vim /etc/roundcubemail/config.inc.php 
 +<code php>... 
 + 
 +// ---------------------------------- 
 +// PLUGINS 
 +// ---------------------------------- 
 +// List of active plugins (in plugins/ directory) 
 +$config['plugins'] = array('acl','managesieve','password'); 
 + 
 +... 
 +</code> 
 +==== Password ==== 
 +Damit unsere User später Ihr **[[centos:mail_c7:dovecot_6|Passwort]]** eigenständig ändern können, konfigurieren wir nun das zugehörige Plugin **password**. 
 +Als erstes kopieren wir die Vorgabedatei, die im RPM-Paket enthalten ist. 
 +   # cp -a /usr/share/roundcubemail/plugins/password/config.inc.php.dist /usr/share/roundcubemail/plugins/password/config.inc.php 
 + 
 +Anschließend bearbeiten wir diese Datei und tragen dort die Datenbankanbindung zur MySQL sowie das benötigte SQL-Statement ein. In dem nachfolgenden Beispiel sind die nötigen Änderungen mit //**Django**// und //**Datum**// gekennzeichnet. 
 +   # vim /usr/share/roundcubemail/plugins/password/config.inc.php 
 +<file php /usr/share/roundcubemail/plugins/password/config.inc.php><?php 
 + 
 +// Password Plugin options 
 +// ----------------------- 
 +// A driver to use for password change. Default: "sql". 
 +// See README file for list of supported driver names. 
 +$config['password_driver'] = 'sql'; 
 + 
 +// Determine whether current password is required to change password. 
 +// Default: false. 
 +$config['password_confirm_current'] = true; 
 + 
 +// Require the new password to be a certain length. 
 +// set to blank to allow passwords of any length 
 +// Django : 2014-09-10 
 +// default: $config['password_minimum_length'] = 0; 
 +$config['password_minimum_length'] = 8; 
 + 
 +// Require the new password to contain a letter and punctuation character 
 +// Change to false to remove this check. 
 +// Django : 2014-09-10 
 +// default: $config['password_require_nonalpha'] = false; 
 +$config['password_require_nonalpha'] = true; 
 + 
 +// Enables logging of password changes into logs/password 
 +$config['password_log'] = false; 
 + 
 +// Comma-separated list of login exceptions for which password change 
 +// will be not available (no Password tab in Settings) 
 +$config['password_login_exceptions'] = null; 
 + 
 +// Array of hosts that support password changing. Default is NULL. 
 +// Listed hosts will feature a Password option in Settings; others will not. 
 +// Example: 
 +//$config['password_hosts'] = array('mail.example.com', 'mail2.example.org'); 
 +$config['password_hosts'] = null; 
 + 
 +// Enables saving the new password even if it matches the old password. Useful 
 +// for upgrading the stored passwords after the encryption scheme has changed. 
 +$config['password_force_save'] = false; 
 + 
 + 
 +// SQL Driver options 
 +// ------------------ 
 +// PEAR database DSN for performing the query. By default 
 +// Roundcube DB settings are used. 
 +// Django : 2014-09-10 
 +// default: $config['password_db_dsn'] = ''; 
 +$config['password_db_dsn'] = 'mysql://pfadmin_user:rbgsDK39DeM2b2btx9iMHfzd@mysql.dmz.nausch.org/postfix'; 
 + 
 +// The SQL query used to change the password. 
 +// The query can contain the following macros that will be expanded as follows: 
 +//      %p is replaced with the plaintext new password 
 +//      %c is replaced with the crypt version of the new password, MD5 if available 
 +//         otherwise DES. More hash function can be enabled using the password_crypt_hash  
 +//         configuration parameter. 
 +//      %D is replaced with the dovecotpw-crypted version of the new password 
 +//      %o is replaced with the password before the change 
 +//      %n is replaced with the hashed version of the new password 
 +//      %q is replaced with the hashed password before the change 
 +//      %h is replaced with the imap host (from the session info) 
 +//      %u is replaced with the username (from the session info) 
 +//      %l is replaced with the local part of the username 
 +//         (in case the username is an email address) 
 +//      %d is replaced with the domain part of the username 
 +//         (in case the username is an email address) 
 +// Escaping of macros is handled by this module. 
 +// Default: "SELECT update_passwd(%c, %u)" 
 +// Django : 2014-09-10 
 +// default: $config['password_query'] = 'SELECT update_passwd(%c, %u)'; 
 +$config['password_query'] = 'UPDATE mailbox SET password = %p, modified=NOW() WHERE username = %u LIMIT 1'; 
 + 
 +// By default the crypt() function which is used to create the '%c'  
 +// parameter uses the md5 algorithm. To use different algorithms  
 +// you can choose between: des, md5, blowfish, sha256, sha512. 
 +// Before using other hash functions than des or md5 please make sure 
 +// your operating system supports the other hash functions. 
 +$config['password_crypt_hash'] = 'md5'; 
 + 
 +// By default domains in variables are using unicode. 
 +// Enable this option to use punycoded names 
 +$config['password_idn_ascii'] = false; 
 + 
 +// Path for dovecotpw (if not in $PATH) 
 +// $config['password_dovecotpw'] = '/usr/local/sbin/dovecotpw'; 
 + 
 +// Dovecot method (dovecotpw -s 'method') 
 +// Django : 2014-09-10 
 +// default: $config['password_dovecotpw_method'] = 'CRAM-MD5'; 
 +$config['password_dovecotpw_method'] = 'CRAM-MD5'; 
 + 
 +// Enables use of password with crypt method prefix in %D, e.g. {MD5}$1$LUiMYWqx$fEkg/ggr/L6Mb2X7be4i1/ 
 +$config['password_dovecotpw_with_method'] = false; 
 + 
 +// Using a password hash for %n and %q variables. 
 +// Determine which hashing algorithm should be used to generate 
 +// the hashed new and current password for using them within the 
 +// SQL query. Requires PHP's 'hash' extension. 
 +$config['password_hash_algorithm'] = 'sha1'; 
 + 
 +// You can also decide whether the hash should be provided 
 +// as hex string or in base64 encoded format. 
 +$config['password_hash_base64'] = false; 
 + 
 + 
 +// Poppassd Driver options 
 +// ----------------------- 
 +// The host which changes the password 
 +$config['password_pop_host'] = 'localhost'; 
 + 
 +// TCP port used for poppassd connections 
 +$config['password_pop_port'] = 106; 
 + 
 + 
 +// SASL Driver options 
 +// ------------------- 
 +// Additional arguments for the saslpasswd2 call 
 +$config['password_saslpasswd_args'] = ''; 
 + 
 + 
 +// LDAP and LDAP_SIMPLE Driver options 
 +// ----------------------------------- 
 +// LDAP server name to connect to.  
 +// You can provide one or several hosts in an array in which case the hosts are tried from left to right. 
 +// Exemple: array('ldap1.exemple.com', 'ldap2.exemple.com'); 
 +// Default: 'localhost' 
 +$config['password_ldap_host'] = 'localhost'; 
 + 
 +// LDAP server port to connect to 
 +// Default: '389' 
 +$config['password_ldap_port'] = '389'; 
 + 
 +// TLS is started after connecting 
 +// Using TLS for password modification is recommanded. 
 +// Default: false 
 +$config['password_ldap_starttls'] = false; 
 + 
 +// LDAP version 
 +// Default: '3' 
 +$config['password_ldap_version'] = '3'; 
 + 
 +// LDAP base name (root directory) 
 +// Exemple: 'dc=exemple,dc=com' 
 +$config['password_ldap_basedn'] = 'dc=exemple,dc=com'; 
 + 
 +// LDAP connection method 
 +// There is two connection method for changing a user's LDAP password. 
 +// 'user': use user credential (recommanded, require password_confirm_current=true) 
 +// 'admin': use admin credential (this mode require password_ldap_adminDN and password_ldap_adminPW) 
 +// Default: 'user' 
 +$config['password_ldap_method'] = 'user'; 
 + 
 +// LDAP Admin DN 
 +// Used only in admin connection mode 
 +// Default: null 
 +$config['password_ldap_adminDN'] = null; 
 + 
 +// LDAP Admin Password 
 +// Used only in admin connection mode 
 +// Default: null 
 +$config['password_ldap_adminPW'] = null; 
 + 
 +// LDAP user DN mask 
 +// The user's DN is mandatory and as we only have his login, 
 +// we need to re-create his DN using a mask 
 +// '%login' will be replaced by the current roundcube user's login 
 +// '%name' will be replaced by the current roundcube user's name part 
 +// '%domain' will be replaced by the current roundcube user's domain part 
 +// '%dc' will be replaced by domain name hierarchal string e.g. "dc=test,dc=domain,dc=com" 
 +// Exemple: 'uid=%login,ou=people,dc=exemple,dc=com' 
 +$config['password_ldap_userDN_mask'] = 'uid=%login,ou=people,dc=exemple,dc=com'; 
 + 
 +// LDAP search DN 
 +// The DN roundcube should bind with to find out user's DN 
 +// based on his login. Note that you should comment out the default 
 +// password_ldap_userDN_mask setting for this to take effect. 
 +// Use this if you cannot specify a general template for user DN with 
 +// password_ldap_userDN_mask. You need to perform a search based on 
 +// users login to find his DN instead. A common reason might be that 
 +// your users are placed under different ou's like engineering or 
 +// sales which cannot be derived from their login only. 
 +$config['password_ldap_searchDN'] = 'cn=roundcube,ou=services,dc=example,dc=com'; 
 + 
 +// LDAP search password 
 +// If password_ldap_searchDN is set, the password to use for 
 +// binding to search for user's DN. Note that you should comment out the default 
 +// password_ldap_userDN_mask setting for this to take effect. 
 +// Warning: Be sure to set approperiate permissions on this file so this password 
 +// is only accesible to roundcube and don't forget to restrict roundcube's access to 
 +// your directory as much as possible using ACLs. Should this password be compromised 
 +// you want to minimize the damage. 
 +$config['password_ldap_searchPW'] = 'secret'; 
 + 
 +// LDAP search base 
 +// If password_ldap_searchDN is set, the base to search in using the filter below. 
 +// Note that you should comment out the default password_ldap_userDN_mask setting 
 +// for this to take effect. 
 +$config['password_ldap_search_base'] = 'ou=people,dc=example,dc=com'; 
 + 
 +// LDAP search filter 
 +// If password_ldap_searchDN is set, the filter to use when 
 +// searching for user's DN. Note that you should comment out the default 
 +// password_ldap_userDN_mask setting for this to take effect. 
 +// '%login' will be replaced by the current roundcube user's login 
 +// '%name' will be replaced by the current roundcube user's name part 
 +// '%domain' will be replaced by the current roundcube user's domain part 
 +// '%dc' will be replaced by domain name hierarchal string e.g. "dc=test,dc=domain,dc=com" 
 +// Example: '(uid=%login)' 
 +// Example: '(&(objectClass=posixAccount)(uid=%login))' 
 +$config['password_ldap_search_filter'] = '(uid=%login)'; 
 + 
 +// LDAP password hash type 
 +// Standard LDAP encryption type which must be one of: crypt, 
 +// ext_des, md5crypt, blowfish, md5, sha, smd5, ssha, ad or clear. 
 +// Please note that most encodage types require external libraries 
 +// to be included in your PHP installation, see function hashPassword in drivers/ldap.php for more info. 
 +// Default: 'crypt' 
 +$config['password_ldap_encodage'] = 'crypt'; 
 + 
 +// LDAP password attribute 
 +// Name of the ldap's attribute used for storing user password 
 +// Default: 'userPassword' 
 +$config['password_ldap_pwattr'] = 'userPassword'; 
 + 
 +// LDAP password force replace 
 +// Force LDAP replace in cases where ACL allows only replace not read 
 +// See http://pear.php.net/package/Net_LDAP2/docs/latest/Net_LDAP2/Net_LDAP2_Entry.html#methodreplace 
 +// Default: true 
 +$config['password_ldap_force_replace'] = true; 
 + 
 +// LDAP Password Last Change Date 
 +// Some places use an attribute to store the date of the last password change 
 +// The date is meassured in "days since epoch" (an integer value) 
 +// Whenever the password is changed, the attribute will be updated if set (e.g. shadowLastChange) 
 +$config['password_ldap_lchattr'] = ''; 
 + 
 +// LDAP Samba password attribute, e.g. sambaNTPassword 
 +// Name of the LDAP's Samba attribute used for storing user password 
 +$config['password_ldap_samba_pwattr'] = ''; 
 +  
 +// LDAP Samba Password Last Change Date attribute, e.g. sambaPwdLastSet 
 +// Some places use an attribute to store the date of the last password change 
 +// The date is meassured in "seconds since epoch" (an integer value) 
 +// Whenever the password is changed, the attribute will be updated if set 
 +$config['password_ldap_samba_lchattr'] = ''; 
 + 
 + 
 +// DirectAdmin Driver options 
 +// -------------------------- 
 +// The host which changes the password 
 +// Use 'ssl://host' instead of 'tcp://host' when running DirectAdmin over SSL. 
 +// The host can contain the following macros that will be expanded as follows: 
 +//     %h is replaced with the imap host (from the session info) 
 +//     %d is replaced with the domain part of the username (if the username is an email) 
 +$config['password_directadmin_host'] = 'tcp://localhost'; 
 + 
 +// TCP port used for DirectAdmin connections 
 +$config['password_directadmin_port'] = 2222; 
 + 
 + 
 +// vpopmaild Driver options 
 +// ----------------------- 
 +// The host which changes the password 
 +$config['password_vpopmaild_host'] = 'localhost'; 
 + 
 +// TCP port used for vpopmaild connections 
 +$config['password_vpopmaild_port'] = 89; 
 + 
 + 
 +// cPanel Driver options 
 +// -------------------------- 
 +// The cPanel Host name 
 +$config['password_cpanel_host'] = 'host.domain.com'; 
 + 
 +// The cPanel admin username 
 +$config['password_cpanel_username'] = 'username'; 
 + 
 +// The cPanel admin password 
 +$config['password_cpanel_password'] = 'password'; 
 + 
 +// The cPanel port to use 
 +$config['password_cpanel_port'] = 2087; 
 + 
 + 
 +// XIMSS (Communigate server) Driver options 
 +// ----------------------------------------- 
 +// Host name of the Communigate server 
 +$config['password_ximss_host'] = 'mail.example.com'; 
 + 
 +// XIMSS port on Communigate server 
 +$config['password_ximss_port'] = 11024; 
 + 
 + 
 +// chpasswd Driver options 
 +// --------------------- 
 +// Command to use 
 +$config['password_chpasswd_cmd'] = 'sudo /usr/sbin/chpasswd 2> /dev/null'; 
 + 
 + 
 +// XMail Driver options 
 +// --------------------- 
 +$config['xmail_host'] = 'localhost'; 
 +$config['xmail_user'] = 'YourXmailControlUser'; 
 +$config['xmail_pass'] = 'YourXmailControlPass'; 
 +$config['xmail_port'] = 6017; 
 + 
 + 
 +// hMail Driver options 
 +// ----------------------- 
 +// Remote hMailServer configuration 
 +// true:  HMailserver is on a remote box (php.ini: com.allow_dcom = true) 
 +// false: Hmailserver is on same box as PHP 
 +$config['hmailserver_remote_dcom'] = false; 
 +// Windows credentials 
 +$config['hmailserver_server'] = array( 
 +    'Server' => 'localhost', // hostname or ip address 
 +    'Username' => 'administrator', // windows username 
 +    'Password' => 'password' // windows user password 
 +); 
 + 
 + 
 +// Virtualmin Driver options 
 +// ------------------------- 
 +// Username format: 
 +// 0: username@domain 
 +// 1: username%domain 
 +// 2: username.domain 
 +// 3: domain.username 
 +// 4: username-domain 
 +// 5: domain-username 
 +// 6: username_domain 
 +// 7: domain_username 
 +$config['password_virtualmin_format'] = 0; 
 + 
 + 
 +// pw_usermod Driver options 
 +// -------------------------- 
 +// Use comma delimited exlist to disable password change for users 
 +// Add the following line to visudo to tighten security: 
 +// www  ALL=NOPASSWORD: /usr/sbin/pw 
 +$config['password_pw_usermod_cmd'] = 'sudo /usr/sbin/pw usermod -h 0 -n'; 
 + 
 + 
 +// DBMail Driver options 
 +// ------------------- 
 +// Additional arguments for the dbmail-users call 
 +$config['password_dbmail_args'] = '-p sha512'; 
 + 
 + 
 +// Expect Driver options 
 +// --------------------- 
 +// Location of expect binary 
 +$config['password_expect_bin'] = '/usr/bin/expect'; 
 + 
 +// Location of expect script (see helpers/passwd-expect) 
 +$config['password_expect_script'] = ''; 
 + 
 +// Arguments for the expect script. See the helpers/passwd-expect file for details. 
 +// This is probably a good starting default: 
 +//   -telent -host localhost -output /tmp/passwd.log -log /tmp/passwd.log 
 +$config['password_expect_params'] = ''; 
 + 
 + 
 +// smb Driver options 
 +// --------------------- 
 +// Samba host (default: localhost) 
 +// Supported replacement variables: 
 +// %n - hostname ($_SERVER['SERVER_NAME']) 
 +// %t - hostname without the first part 
 +// %d - domain (http hostname $_SERVER['HTTP_HOST'] without the first part) 
 +$config['password_smb_host'] = 'localhost'; 
 +// Location of smbpasswd binary 
 +$config['password_smb_cmd'] = '/usr/bin/smbpasswd'; 
 +</file> 
 + 
 +Über den Menüpunkt **Einstellungen / Passwort** können wir nun vom Webmailer aus das Passwort ändern. 
 + 
 +{{ :centos:mail_c7:roundcubemail_08.png?direct&700 |Bild: Roundcube Webmailer - Dialog zum Ändern des Passwortes}}  
 + 
 + 
 +==== Managesieve ==== 
 +Damit unsere Mailkunden ihre **[[centos:mail_c7:dovecot_3|sieve-Regeln]]** direkt aus Roundcube heraus komfortabel ändern können, aktivieren wir das zugehörige Plugin **managesieve** 
 + 
 +Auch hier kopieren wir als erstes die Vorgabedatei aus dem RPM-Paket. 
 +   # cp /usr/share/roundcubemail/plugins/managesieve/config.inc.php.dist /usr/share/roundcubemail/plugins/managesieve/config.inc.php -a 
 + 
 +Anschließend bearbeiten wir diese Datei und tragen dort die benötigten sieve-Konfigurationsdetail ein. Auch hier sind in dem nachfolgenden Beispiel die Änderungen mit //**Django**// und //**Datum**// gekennzeichnet. 
 +   # vim /usr/share/roundcubemail/plugins/managesieve/config.inc.php 
 +<file php /usr/share/roundcubemail/plugins/managesieve/config.inc.php><?php 
 + 
 +// managesieve server port. When empty the port will be determined automatically 
 +// using getservbyname() function, with 4190 as a fallback. 
 +// Django : 2014-09-10 
 +// default: $config['managesieve_port'] = null; 
 +$config['managesieve_port'] = 4190; 
 + 
 +// managesieve server address, default is localhost. 
 +// Replacement variables supported in host name: 
 +// %h - user's IMAP hostname 
 +// %n - http hostname ($_SERVER['SERVER_NAME']) 
 +// %d - domain (http hostname without the first part) 
 +// For example %n = mail.domain.tld, %d = domain.tld 
 +// Django : 2014-09-10 
 +// default: $config['managesieve_host'] = 'localhost'; 
 +$config['managesieve_host'] = 'imap.dmz.nausch.org'; 
 + 
 +// authentication method. Can be CRAM-MD5, DIGEST-MD5, PLAIN, LOGIN, EXTERNAL 
 +// or none. Optional, defaults to best method supported by server. 
 +$config['managesieve_auth_type'] = null; 
 + 
 +// Optional managesieve authentication identifier to be used as authorization proxy. 
 +// Authenticate as a different user but act on behalf of the logged in user. 
 +// Works with PLAIN and DIGEST-MD5 auth. 
 +$config['managesieve_auth_cid'] = null; 
 + 
 +// Optional managesieve authentication password to be used for imap_auth_cid 
 +$config['managesieve_auth_pw'] = null; 
 + 
 +// use or not TLS for managesieve server connection 
 +// Note: tls:// prefix in managesieve_host is also supported 
 +// Django : 2014-09-10 
 +// default: $config['managesieve_usetls'] = false; 
 +$config['managesieve_usetls'] = true; 
 + 
 +// default contents of filters script (eg. default spam filter) 
 +$config['managesieve_default'] = '/etc/dovecot/sieve/global'; 
 + 
 +// The name of the script which will be used when there's no user script 
 +$config['managesieve_script_name'] = 'managesieve'; 
 + 
 +// Sieve RFC says that we should use UTF-8 endcoding for mailbox names, 
 +// but some implementations does not covert UTF-8 to modified UTF-7. 
 +// Defaults to UTF7-IMAP 
 +$config['managesieve_mbox_encoding'] = 'UTF-8'; 
 + 
 +// I need this because my dovecot (with listescape plugin) uses 
 +// ':' delimiter, but creates folders with dot delimiter 
 +$config['managesieve_replace_delimiter'] = ''; 
 + 
 +// disabled sieve extensions (body, copy, date, editheader, encoded-character, 
 +// envelope, environment, ereject, fileinto, ihave, imap4flags, index, 
 +// mailbox, mboxmetadata, regex, reject, relational, servermetadata, 
 +// spamtest, spamtestplus, subaddress, vacation, variables, virustest, etc. 
 +// Note: not all extensions are implemented 
 +$config['managesieve_disabled_extensions'] = array(); 
 + 
 +// Enables debugging of conversation with sieve server. Logs it into <log_dir>/sieve 
 +$config['managesieve_debug'] = false; 
 + 
 +// Enables features described in http://wiki.kolab.org/KEP:14 
 +$config['managesieve_kolab_master'] = false; 
 + 
 +// Script name extension used for scripts including. Dovecot uses '.sieve', 
 +// Cyrus uses '.siv'. Doesn't matter if you have managesieve_kolab_master disabled. 
 +$config['managesieve_filename_extension'] = '.sieve'; 
 + 
 +// List of reserved script names (without extension). 
 +// Scripts listed here will be not presented to the user. 
 +$config['managesieve_filename_exceptions'] = array(); 
 + 
 +// List of domains limiting destination emails in redirect action 
 +// If not empty, user will need to select domain from a list 
 +$config['managesieve_domains'] = array(); 
 + 
 +// Enables separate management interface for vacation responses (out-of-office) 
 +// 0 - no separate section (default), 
 +// 1 - add Vacation section, 
 +// 2 - add Vacation section, but hide Filters section 
 +$config['managesieve_vacation'] = 0; 
 + 
 +// Supported methods of notify extension. Default: 'mailto' 
 +$config['managesieve_notify_methods'] = array('mailto'); 
 +</file> 
 + 
 +Über den Menüpunkt **Einstellungen / Filter** können wir nun vom Webmailer aus das Passwort ändern. 
 + 
 +{{ :centos:mail_c7:roundcubemail_09.png?direct&850 |Bild: Roundcube Webmailer - Dialog zum Verwalter der sieve-Regeln}}  
 + 
 + 
 +==== ACL ==== 
 +Für die Verwaltung von **[[centos:mail_c7:dovecot_7|Shared Foldern]]** konfigurieren wir nun noch das **ACL**-Plugin. 
 +Als erstes kopieren wir die Konfigurationsdatei aus dem RPM. 
 +   # cp /usr/share/roundcubemail/plugins/acl/config.inc.php.dist /usr/share/roundcubemail/plugins/acl/config.inc.php -a 
 + 
 +Anschließend bearbeiten wir nun diese neue Datei. 
 +   # vim /usr/share/roundcubemail/plugins/acl/config.inc.php 
 +<file php /usr/share/roundcubemail/plugins/acl/config.inc.php><?php 
 + 
 +// Default look of access rights table 
 +// In advanced mode all access rights are displayed separately 
 +// In simple mode access rights are grouped into four groups: read, write, delete, full  
 +$config['acl_advanced_mode'] = false; 
 + 
 +// LDAP addressbook that would be searched for user names autocomplete. 
 +// That should be an array refering to the $config['ldap_public'] array key 
 +// or complete addressbook configuration array. 
 +$config['acl_users_source'] = ''; 
 + 
 +// The LDAP attribute which will be used as ACL user identifier 
 +$config['acl_users_field'] = 'mail'; 
 + 
 +// The LDAP search filter will be &'d with search queries 
 +$config['acl_users_filter'] = ''; 
 + 
 +// Include the following 'special' access control subjects in the ACL dialog; 
 +// Defaults to array('anyone', 'anonymous') (not when set to an empty array) 
 +// Example: array('anyone') to exclude 'anonymous'. 
 +// Set to an empty array to exclude all special aci subjects. 
 +$config['acl_specials'] = array('anyone', 'anonymous'); 
 + 
 +?> 
 +</file> 
 + 
 +Über den Menüpunkt **Einstellungen / Ordner / Ordnereigenschaften / Freigabe** können wir nun vom Webmailer aus die Zugriffsrechte für andere auf einzelne Ordner verwalten. 
 + 
 +{{ :centos:mail_c7:roundcubemail_10.png?direct&850 |Bild: Roundcube Webmailer - Dialog zum Verwalten von ACLs für Shared Folders}} 
  
-Im Verzeichnis //**/etc/roundcubemail/**// finden wir die entsprechende Konfigurationsdatei **db.inc.php**. Diese bearbeiten wir mit dem Editor unserer Wahl, z.B. **vim**. +====== Links ====== 
-   # vim /etc/roundcubemail/db.inc.php+  * **[[centos:mail_c7:start|Zurück zum Kapitel >>Mailserverinstallation unter CentOS 7<<]]** 
 +  * **[[wiki:start|Zurück zu >>Projekte und Themenkapitel<<]]** 
 +  * **[[http://dokuwiki.nausch.org/doku.php/|Zurück zur Startseite]]**
  
  
  • centos/mail_c7/roundcube_1.1410296882.txt.gz
  • Zuletzt geändert: 09.09.2014 21:08.
  • von django