Skip to main content

ISPConfig 3 + RoundCube Mail 1.0 + Password Management

Most of the articles on the web are referring to older versions. Below are the steps to get it working.

Assumptions: This works on a Ubuntu Server 12.04 LTS updated with the latest patches, setup by following "Perfect Server" tutorial, then installed with RoundCube 1.0 as the Webmail. (SqurrielMail installation was skipped).

1. Enable the password plugin of RoundCube - The 1.0 version comes with the plugin in the package, but not activated.

Under config/config.inc.php

 // ----------------------------------
// PLUGINS
// ----------------------------------
// List of active plugins (in plugins/ directory)
$config['plugins'] = array('password');

This tells you will activate the 'password' plugin which sits inside the plugins/ directory.

2. Then edit the plugins/password/config.inc.php

$config['password_db_dsn'] = 'mysql://ispconfig:password@localhost/dbispconfig';

"password" is stored in /usr/local/ispconfig/interface/lib/config.inc.php.

 3. Edit $config['password_query'] in plugins/password/config.inc.php

 $config['password_query'] = 'UPDATE mail_user SET password=%c WHERE email=%u LIMIT 1';

4. Test the service under RoundCube 1.0

 Other reference:  

 http://bashprompt.net/using-roundcube-webmail-with-ispconfig-3-on-debian-wheezy-apache2/
Not tried.

http://helidium.wordpress.com/2011/12/30/ispconfig3-roundcube-password-change/
Good reference, I also followed the steps on database update - not sure if I needed it. If the above does not work, then do the database update under phpmyadmin but skipped the final step.

P.S. Be careful with the config.inc.php - the RoundCube main config and the plugin config files have the same name. I overwrote my config by mistake. Almost got into a panic mode.

Comments

  1. UnknownDecember 26, 2016 at 1:29 AM

    Thanks ! The only solution that worked for me.

    ReplyDelete
    Replies
    1. Kenneth CheukJune 4, 2017 at 10:12 PM

      Greetings from Hong Kong. Glad the post helped.

      Delete

Post a Comment

Popular posts from this blog

ISPConfig / Pure-FTP / SSL (TLS) setup

ISPConfig comes with LetsEncrypt integrated in its panel for web domains. However, it does not automatically use the SSL cert for FTP service (PureFTP). This post describes the steps to enable the support. 1. We need an FQDN so that Lets Encrypt (LE) will be able to generate SSL under ISPConfig panel. 2. PureFTP TLS support requires a cert in .pem format which can be generated by leveraging the LE cert generated: cat /etc/letsencrypt/live/mydomain.com/privkey.pem /etc/letsencrypt/live/mydomain.com/fullchain.pem > /etc/ssl/private/pure-ftpd.pem 3. Restart PureFTP so that it will not use the new certificate 4. LE certificates need to be renewed regularly so it is necessary to create a cron job to keep the .pem file updated. Setup a crontab 0 6 * * * /etc/letsencrypt/certbot-auto -n renew --quiet --no-self-upgrade && cat /etc/letsencrypt/live/mydomain.com/privkey.pem /etc/letsencrypt/live/mydomain.com/fullchain.pem > /etc/ssl/private/pure-ftpd.pem && se...
Post a Comment
Read more

ISPConfig 3 / Mail / Custom mail filter recipe

Recently trying to setup a mail re-direct (or a cc) to an external e-mail address. It is important to first determine if you are running courier or dovecot because the syntax is different. Under dovecot, it should be in sieve syntax. Therefore, under ISPConfig3 -> Email -> Email Mailbox -> Custom Rules, enter: redirect "mail@example.com"; Ensure it is double straight quotes and semi-colon at the end. Wait until the update is done (usually a few minutes) via the cron jobs of ISPConfig3 updating the /var/vmail/domain/username/.sieve
Post a Comment
Read more

Ubuntu 16.04 and ISPConfig 3.1 - stopping ClamAV

ClamAV requires quite a bit of resources to run in the background and this usually slows down the mail delivery. In the ISPConfig 3 (Under Perfect Server setup), clamAV is run within Amavis. Therefore, typical removal of clamAV commands will not remove it. When RAM is really low, Linux kills amavis and this will cause mail not being delivered. Therefore, if we run amavis to manage anti-virus and spam, consider a minimum of 2G or 4G RAM VM/Cloud servers. The steps to disable clamav and amavisd are: (1) edit postfix conf - note amavis uses a special port 10024 and 10026. Therefore, if you are not using these ports, consider closing them in your firewall settings. nano /etc/postfix/main.cf # content_filter = amavis:[127.0.0.1]:10024 # receive_override_options = no_address_mappings (2) Under ISPConfig 3.1, comment additional 2 lines nano /etc/postfix/tag_as_foreign.re # /^/ FILTER amavis:[127.0.0.1]:10024 nano /etc/postfix/tag_as_originating.re # /^/ FILTER amavi...
1 comment
Read more