Users May 2014

users@lists.roundcube.net

22 participants
18 discussions

Update 1.0.1 out now
by Thomas Bruederli 22 May '14

22 May '14

Dear Roundcube users We can proudly announce the first service release to update the stable version 1.0 of Roundcube webmail. It contains some important bug fixes and improvements, primarily a fix for the unintentional redirect from the compose page in Google Chrome which likely started to appear after a recent Chrome update. It's considered stable and we recommend to update all productive installations of Roundcube with this version. Download it from http://roundcube.net/download, see the full changelog here: http://trac.roundcube.net/wiki/Changelog Please note that the update includes a small MySQL database schema change, thus make sure you run the update script. Kind regards, Thomas

5 6

Plugin password error - driver chpasswd
by Daniel Lopez 22 May '14

22 May '14

Hello, I Install roundcubemail using EPEL repository: # wget http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm # rpm -ivh epel-release-6-8.noarch.rpm # yum install roundcubemail I have the following settings: CentOS 6.4 Apache 2.2.15 PHP 5.3.3 MySQL 5.1.69 Roundcube Webmail 0.9.5 Plugin password 3.2 Users are not saved in the database, are stored in the operating system: /etc/passwd /etc/shadow cat /etc/roundcubemail/main.inc.php $rcmail_config['default_host'] = 'domain.com'; $rcmail_config['plugins'] = array(password); cat /usr/share/roundcubemail/plugins/password/config.inc.php $rcmail_config['password_driver'] = 'chpasswd'; cat /etc/sudoers apache ALL=NOPASSWD: /usr/sbin/chpasswd When I try to save the password change displays the message: an error has occurred, it can not save the new password cat /var/log/roundcubemail/errors PHP Error: Password plugin: Unable to execute sudo /usr/sbin/chpasswd 2> /dev/null in /usr/share/roundcubemail/plugins/password/drivers/chpasswd.php on line 32 (POST /mail/?_task=settings&_action=plugin.password-save?_task=&_action=) please help to find the error Daniel Lopez

1 0

Re: [RCU] Testing Roundcube 1.0.x
by Steve Perkins 22 May '14

22 May '14

Surely the whole point about a test/staging system is any glitches won't impact on the production system. Mixing them the way you suggest would mean any problems with the test system would also impact the live one. Would this not be self defeating ? Sent from MyPhone David Carter <dpc22(a)cam.ac.uk> wrote: >We expect to upgrade from Roundcube 0.9.5 to 1.0.x over the summer >vacation (my management chain and I prefer not to make substantial >changes during the academic year). > >Something that I would like to do if possible is have a period of >parallel running so that people can kick the tires and make sure that >our small collection of local plugins and our local skin are working >correctly for a few days or weeks before we commit to running the new >version. > >I can of course dump and restore the existing Roundcube database to >build a completely independent Roundcube 1.0.1 test system off to one >side, away from the production servers. > >However if I look at the handful of database upgrade steps from 0.9.5 to >1.0.1, the only significant change would appear to be the attached >renaming of sequences (we aren't using any of the cache tables). > > .../SQL/postgres/2013042700.sql : > > ALTER SEQUENCE user_ids RENAME TO users_seq; > ALTER TABLE users ALTER COLUMN user_id SET DEFAULT >nextval('users_seq'::text); > > ALTER SEQUENCE identity_ids RENAME TO identities_seq; > ALTER TABLE identities ALTER COLUMN identity_id SET DEFAULT >nextval('identities_seq'::text); > > ALTER SEQUENCE contact_ids RENAME TO contacts_seq; > ALTER TABLE contacts ALTER COLUMN contact_id SET DEFAULT >nextval('contacts_seq'::text); > > ALTER SEQUENCE contactgroups_ids RENAME TO contactgroups_seq; > ALTER TABLE contactgroups ALTER COLUMN contactgroup_id SET DEFAULT >nextval('contactgroups_seq'::text); > > ALTER SEQUENCE search_ids RENAME TO searches_seq; > ALTER TABLE searches ALTER COLUMN search_id SET DEFAULT >nextval('searches_seq'::text); > >These sequence names appear to be hard-wired in 1.0.1. > >However Roundcube 0.9.5 can be reconfigured to use any names, including >the names used by 1.0.1: > > // you can define specific sequence names used in PostgreSQL > $rcmail_config['db_sequence_users'] = 'users_seq'; > $rcmail_config['db_sequence_identities'] = 'identities_seq'; > $rcmail_config['db_sequence_contacts'] = 'contacts_seq'; > $rcmail_config['db_sequence_contactgroups'] = 'contactgroups_seq'; > $rcmail_config['db_sequence_searches'] = 'searches_seq'; > >A brief experiment on a test system suggests that I can safely switch >back and forth between Roundcube 0.9.5 and 1.0.1 with this single >configuration change at the 0.9.5 end. > >My question is whether this is a sensible thing to try and do. Are there >incompatible changes in the various preferences databases which aren't >reflected in the database schema? That would require an independent test >system. > >Thanks, > >-- >David Carter Email: >David.Carter(a)uis.cam.ac.uk >University of Cambridge, Phone: (01223) 334502 >Information Services, Fax: (01223) 334679 >7 J J Thomson Avenue, >Cambridge UK. CB3 0RB > >_______________________________________________ >Roundcube Users mailing list >users(a)lists.roundcube.net >http://lists.roundcube.net/mailman/listinfo/users

2 1

Testing Roundcube 1.0.x
by David Carter 22 May '14

22 May '14

We expect to upgrade from Roundcube 0.9.5 to 1.0.x over the summer vacation (my management chain and I prefer not to make substantial changes during the academic year). Something that I would like to do if possible is have a period of parallel running so that people can kick the tires and make sure that our small collection of local plugins and our local skin are working correctly for a few days or weeks before we commit to running the new version. I can of course dump and restore the existing Roundcube database to build a completely independent Roundcube 1.0.1 test system off to one side, away from the production servers. However if I look at the handful of database upgrade steps from 0.9.5 to 1.0.1, the only significant change would appear to be the attached renaming of sequences (we aren't using any of the cache tables). .../SQL/postgres/2013042700.sql : ALTER SEQUENCE user_ids RENAME TO users_seq; ALTER TABLE users ALTER COLUMN user_id SET DEFAULT nextval('users_seq'::text); ALTER SEQUENCE identity_ids RENAME TO identities_seq; ALTER TABLE identities ALTER COLUMN identity_id SET DEFAULT nextval('identities_seq'::text); ALTER SEQUENCE contact_ids RENAME TO contacts_seq; ALTER TABLE contacts ALTER COLUMN contact_id SET DEFAULT nextval('contacts_seq'::text); ALTER SEQUENCE contactgroups_ids RENAME TO contactgroups_seq; ALTER TABLE contactgroups ALTER COLUMN contactgroup_id SET DEFAULT nextval('contactgroups_seq'::text); ALTER SEQUENCE search_ids RENAME TO searches_seq; ALTER TABLE searches ALTER COLUMN search_id SET DEFAULT nextval('searches_seq'::text); These sequence names appear to be hard-wired in 1.0.1. However Roundcube 0.9.5 can be reconfigured to use any names, including the names used by 1.0.1: // you can define specific sequence names used in PostgreSQL $rcmail_config['db_sequence_users'] = 'users_seq'; $rcmail_config['db_sequence_identities'] = 'identities_seq'; $rcmail_config['db_sequence_contacts'] = 'contacts_seq'; $rcmail_config['db_sequence_contactgroups'] = 'contactgroups_seq'; $rcmail_config['db_sequence_searches'] = 'searches_seq'; A brief experiment on a test system suggests that I can safely switch back and forth between Roundcube 0.9.5 and 1.0.1 with this single configuration change at the 0.9.5 end. My question is whether this is a sensible thing to try and do. Are there incompatible changes in the various preferences databases which aren't reflected in the database schema? That would require an independent test system. Thanks, -- David Carter Email: David.Carter(a)uis.cam.ac.uk University of Cambridge, Phone: (01223) 334502 Information Services, Fax: (01223) 334679 7 J J Thomson Avenue, Cambridge UK. CB3 0RB

1 0

Upgrade from 0.95 to 1.0.1 : only first three emails displayed
by S Loewenthal 20 May '14

20 May '14

Hi, I was wondering if somebody had seen this issue when after initial upgrade from 0.9.5 to 1.0.1 the RC displays only the first three emails. I used ./bin/install.sh <target_dir> for my update. I rolled back to 0.9.5 by removing the newly installed directory and rolling back my previous copy and all emails were displayed again. Below I've copied how my upgrade unfolded, because it had some errors but I don't see how they should have caused the 3 email only issue. Running update script at target... NOTICE: Obsolete config options: (You still have some obsolete or inexistent properties set. This isn't a problem but should be noticed) - 'mime_magic' Do you want me to fix your local configuration? (y/N) y . backing up the current config file(s)... . writing /www/roundcube/config/config.inc.php... Done. Your configuration files are now up-to-date! WARNING: File type detection doesn't work properly! Please check the 'mime_magic' config option or the finfo functions of PHP and run this script again. Executing database schema update. Updating database schema (2013042700)... [OK] Updating database schema (2013052500)... [OK] ERROR: Error in DDL upgrade 2013061000: [1146] Table 'roundcubemail.cache_index' doesn't existUpdating database schema (2013061000)... [FAILED] All done. Lots of thanks if anybody could give me some help. Si. -- "I decided that I was a lemon for a couple of weeks. I kept myself amused all that time jumping in and out of a gin and tonic." pgp 4BA78604

3 2

Increase attachment file size in php.ini
by barul 03 May '14

03 May '14

Hello, I'd like to be able to send attachment bigger than default 2M size limit. In my php.ini's (I have 2 files, one in /etc/php/cgi, the other in /etc/php/cli), I've changed upload_max_filesize to 10M, but I still cannot send big attachments. Do I need to restart something to make the changes effective? Thanks, -- barul

3 3

Roundcube 1.0.0 exits "compose" after a time
by Zach La Celle 02 May '14

02 May '14

On Roundcube 1.0.0, if the user starts composing an email then leaves it for a few (5?) minutes, the software saves the composition to draft then exits back to the inbox. This did not used to happen on 7.1.0. Is there any way to prevent autosave of draft from kicking the user out of Compose?

3 6

Cannot resize pages on smartphone on RC upgrade (7.1.0 -> 1.0.0)
by Zach La Celle 01 May '14

01 May '14

Hello, After upgrading Roundcube from 7.1.0 (the repo version for Ubuntu 12.0.4) to 1.0.0 (downloaded from the website), users are reporting that they can no longer resize the page in their smartphone browser. I've confirmed this with Chrome on a Galaxy S3. Two finger dragging no longer works, and thus the software is much more difficult to use on the mobile device. Is there any reason that this functionality was broken from 7.1.0 to 1.0.0? Thank you.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Users May 2014