Worked this one for me 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://ispconfigassword@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
@Keagan: Really bad idea what you did. You bypassed ISPconfig which means that your password changes are not creating valid configuration transactions so all actions bound to a password change were skipped on your system. This might work on a first glace for simple single server systems, but might give you email issues later and will fail on multiserver systems completely plus you opened up a potentially big security hole by giving RoundCube full access to the ISPConfig database. Use the plugin that @Steini86 pointed out as it uses the correct way to communicate with the server by using the ISPConfig remote API.
@Keagan as well as what @Steini86 and @till suggests, you should also probably look at updating your roundcube install, 1.0 is ancient.