Roundcube Community Forum

News and Announcements => General Discussion => Topic started by: soprano on March 26, 2020, 11:15:25 AM

Title: Upgrading from a 1.0 release
Post by: soprano on March 26, 2020, 11:15:25 AM
Hi all,

I would like to know which steps i need to do for upgrading an old 1.0.1 version to at least 1.2 or 1.3 version if not 1.4 version.

I would like to know also from which version of roundcube is possibile to use PHP v7.1, from which 7.2, from which 7.3 and from which 7.4

I use up-imapproxy to connect to my imap server, i will have problems using this if i update roundcube.

I have a license to use if i remember good the droid skin for mobile phones, but i suppose it will not work anymore, is there a mobile skin available now ?

I use Roundcube on 2 machines both connected to the same mysql server and the users use it passing from a Load Balancer, can i continue to use it in this way or i need to change something ?

Thanks in advance for the help
Claudio
Title: Re: Upgrading from a 1.0 release
Post by: soprano on March 26, 2020, 11:17:19 AM
I tried to search Roundcube 1.0.x vesions or 1.1.x versions to download them but i can't find them.

Is there some way to download them i could also update the version at the latest 1.0.x version before and then move to the new ones later.

Let me know
Claudio
Title: Re: Upgrading from a 1.0 release
Post by: JohnDoh on March 26, 2020, 01:08:22 PM
Quote
I would like to know which steps i need to do for upgrading an old 1.0.1 version to at least 1.2 or 1.3 version if not 1.4 version.
1.4.3 is the current stable version of Roundcube

Quote
I would like to know also from which version of roundcube is possibile to use PHP v7.1, from which 7.2, from which 7.3 and from which 7.4
PHP7 compatibility was added in Roundcube 1.2. Information on the various changes and fixes is available in the changelog https://github.com/roundcube/roundcubemail/blob/release-1.4/CHANGELOG

Quote
I use up-imapproxy to connect to my imap server, i will have problems using this if i update roundcube.
There is no reason it would, since you are running such an old version you may need to carefully review your Roundcube config.

Quote
I have a license to use if i remember good the droid skin for mobile phones, but i suppose it will not work anymore, is there a mobile skin available now ?
No idea about "droid skin for mobile phones". 1.4 ships with the Elastic skin, a responsible skin designed to work on desktops, tables and phones.

Quote
I use Roundcube on 2 machines both connected to the same mysql server and the users use it passing from a Load Balancer, can i continue to use it in this way or i need to change something ?
I don't see why not. Some info for load balanced setups is available in the wiki https://github.com/roundcube/roundcubemail/wiki/Configuration:-Load-balanced-Setup

Make sure you read the upgrading instructions before you start
Title: Re: Upgrading from a 1.0 release
Post by: soprano on March 27, 2020, 05:01:22 AM
Quote
I would like to know which steps i need to do for upgrading an old 1.0.1 version to at least 1.2 or 1.3 version if not 1.4 version.
1.4.3 is the current stable version of Roundcube

But can i move from 1.0 release to 1.4 release straight forward ? or i need to move to 1.0.last first, then 1.1, then 1.2 then 1.3 and for last to 1.4 ?

Quote
I would like to know also from which version of roundcube is possibile to use PHP v7.1, from which 7.2, from which 7.3 and from which 7.4
PHP7 compatibility was added in Roundcube 1.2. Information on the various changes and fixes is available in the changelog https://github.com/roundcube/roundcubemail/blob/release-1.4/CHANGELOG
Thanks i will give it a look

Quote
I use up-imapproxy to connect to my imap server, i will have problems using this if i update roundcube.
There is no reason it would, since you are running such an old version you may need to carefully review your Roundcube config.
Which imap proxy software do you think i would use instead ?

Quote
I have a license to use if i remember good the droid skin for mobile phones, but i suppose it will not work anymore, is there a mobile skin available now ?
No idea about "droid skin for mobile phones". 1.4 ships with the Elastic skin, a responsible skin designed to work on desktops, tables and phones.
Is it free ?

Quote
I use Roundcube on 2 machines both connected to the same mysql server and the users use it passing from a Load Balancer, can i continue to use it in this way or i need to change something ?
I don't see why not. Some info for load balanced setups is available in the wiki https://github.com/roundcube/roundcubemail/wiki/Configuration:-Load-balanced-Setup
Thanks i will give it a look

Make sure you read the upgrading instructions before you start
Yes but it instruction don't talk about moving from 1.0.x release to the latest one

And a final question is possibile to upgrade from 1.0.x to the 1.0.last or 1.1.last because i can't find where download them

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: soprano on March 27, 2020, 05:27:43 AM
Can someone fill the missing latest versions

For v1.4 the latest is 1.4.3

For v1.3 the latest is 1.3.10

For v1.2 the latest is 1.2.9

For v1.1 the latest is ???

For v1.0 the latest is ???

Thanks in advance
Claudio
Title: Re: Upgrading from a 1.0 release
Post by: JohnDoh on March 27, 2020, 09:06:38 AM
Quote
But can i move from 1.0 release to 1.4 release straight forward ?
You should be able to

About the IMAP proxy. I made a typo I meant to say there is no reason it wouldn't work.

The Elastic skin is free yes, it is distributed with Roundcube.

The upgrading instructions are the same for all versoins you can run `./bin/installto.sh <TARGET-FOLDER>` or you can follow the manual steps listed in the UPGRADING file.

The last versions of 1.0.x and 1.1.x where 1.0.12 and 1.1.12 all the old relases are available on github.
Title: Re: Upgrading from a 1.0 release
Post by: soprano on March 30, 2020, 11:33:38 AM
Quote
But can i move from 1.0 release to 1.4 release straight forward ?
You should be able to

About the IMAP proxy. I made a typo I meant to say there is no reason it wouldn't work.

The Elastic skin is free yes, it is distributed with Roundcube.

The upgrading instructions are the same for all versoins you can run `./bin/installto.sh <TARGET-FOLDER>` or you can follow the manual steps listed in the UPGRADING file.

The last versions of 1.0.x and 1.1.x where 1.0.12 and 1.1.12 all the old relases are available on github.

Ok thank you for all your answers, for now i upgrade to the latest 1.0.x i will do some tests and then i will move to 1.1.x then again tests and go on.

We use LDAP autentication, mysql DB server, imapproxy, do you think we will have to change something in the configuration files moving from a version to another one ?

Are there some settings that will be need to be removed moving to newer versions ?

Are there any tweaks (memcache or other software to use) to speed up the roundcube clients experience ?

Thanks again for your help
Claudio
Title: Re: Upgrading from a 1.0 release
Post by: JohnDoh on March 30, 2020, 01:54:13 PM
Quote
We use LDAP autentication, mysql DB server, imapproxy, do you think we will have to change something in the configuration files moving from a version to another one ?
No one here can answer that with any certainty since we don't know your config.

I understand that you have a lot of concerns because you are making such a big jump, your current version is way out of date so its a bit scary. Do you have an test environment you can run the update in first? If you are using only the skins and plugins distributed with Roundcube then it should be pretty smooth.

Quote
Are there some settings that will be need to be removed moving to newer versions ?
For sure there will have been some changes to the default config in all this time, if you need to change anything though I can't answer because I don't know your config. Your config.inc.php file should only contain things you have changed from the defaults so if you review those configs against the current defaults.inc.php you should be fine. Any breaking changes to config should be mentioned in the release notes of the various versions - there was a problem with 1.4 where the info only went into the release notes with 1.4.1.

In general though I think Roundcube has good backwards compatibility.

Quote
Are there any tweaks (memcache or other software to use) to speed up the roundcube clients experience ?
There are a few tips here https://github.com/roundcube/roundcubemail/wiki/Configuration:-Load-balanced-Setup
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 07, 2020, 10:12:51 AM
Quote
We use LDAP autentication, mysql DB server, imapproxy, do you think we will have to change something in the configuration files moving from a version to another one ?
No one here can answer that with any certainty since we don't know your config.

I understand that you have a lot of concerns because you are making such a big jump, your current version is way out of date so its a bit scary. Do you have an test environment you can run the update in first? If you are using only the skins and plugins distributed with Roundcube then it should be pretty smooth.

Ok i moved from v1.0.x to v1.0.12 and then i moved from v1.0.12 to v1.1.12, i had to change the captcha plugin because the old one drcaptcha was not available anymore and outdated i suppose, so i change it with rcguard plugin, i configured it to use recaptcha v2 from google and now it seems to work, i can't get the pictures but only the tick box, but some other user told me he had the pictures, so maybe it is working i suppose.
Other strange thing is that it would use the new table rcguard but it is empty, always, anyway i enabled the plugin always, so attempts set to 0, maybe with this value it doesn't need to use the DB.

I have only the capthca and the keyboard_shortcuts (i hope this will work with newer release of roundcube) plugins installed so i suppose i will not have too problems moving forward again.

Quote
Are there some settings that will be need to be removed moving to newer versions ?
For sure there will have been some changes to the default config in all this time, if you need to change anything though I can't answer because I don't know your config. Your config.inc.php file should only contain things you have changed from the defaults so if you review those configs against the current defaults.inc.php you should be fine. Any breaking changes to config should be mentioned in the release notes of the various versions - there was a problem with 1.4 where the info only went into the release notes with 1.4.1.

In general though I think Roundcube has good backwards compatibility.

Ok no problem i will switch to v1.2.9 then v1.3.10, then if all works i will move to v1.4.3, i always will use the latest version of each main release.

Quote
Are there any tweaks (memcache or other software to use) to speed up the roundcube clients experience ?
There are a few tips here https://github.com/roundcube/roundcubemail/wiki/Configuration:-Load-balanced-Setup

Ok i read that document and i have already this kind of setup, so i don't need to upgrade nothing about it

But now i have a new question:

I have found that i can have two mysql user account, one for WRITE and one for READ using the

$config['db_dsnw'] = ''; for WRITE operations

$config['db_dsnr'] = ''; for READ operations

and then

$config['db_dsnw_noread'] = true;

i set it now but how i can check if it is working or not ?

in the documentation it tell for the db_dsnr config

// Database DSN for read-only operations (if empty write database will be used)
// useful for database replication

and for the db_dsnw_noread config
// Disable the use of already established dsnw connections for subsequent reads

Is true the right value if i want to use the READ account for read operations also if the WRITE account was used before ?

Thanks again
Claudio
Title: Re: Upgrading from a 1.0 release
Post by: JohnDoh on April 08, 2020, 01:05:39 PM
It sounds like you have done your configuration correctly. I don't know how you can verify it. I'm not sure if the sql_debug logs show that information. I guess the most reliable way is to have a look at the transaction log on your sql server.
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 09, 2020, 06:43:11 AM
Ok i have set the READ account to have only SELECT privileges to roundcube DB, is that the only privilege that it needs to have ?

I found no documentation about the read account or some wiki page how to create/use it.

Let me know if you know something more.

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 09, 2020, 11:34:58 AM
Ok i solved the problem for the READ account, the SELECT privilege is all it needs, i enable the transaction logs and found it works with no error.

Now i payed attention to the logs because i have a lot of authentication error on imap server but always for the same users

Apr  9 16:23:55 imap1 dovecot: imap-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<>, method=PLAIN, rip=172.17.23.41, lip=193.206.84.43, TLS, session=<55nGXdyiFLCsERcp>

and then

Apr  9 16:24:55 imap1 dovecot: imap-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<>, method=PLAIN, rip=172.17.23.41, lip=193.206.84.43, TLS, session=<D3JaYdyi3LKsERcp>

and again 1 minute after this another one and so on

they are there each minute one entry for the same user after the first one, i'm sure that the user can login else i will have received an email

This is with v1.0.12 (i updated the production webmail servers), i tried to search old logs and i had some entry but each 5-10 minutes and not for the same user, no messages repeated.

There is some default settings set to 60 seconds ?

I use UW imapproxy, the configuration is the same i changed nothing on it.

Thanks for any help.

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 09, 2020, 11:52:31 AM
in the default.inc.php i found these two maybe relevant settings

$config['min_refresh_interval'] = 60;
$config['refresh_interval'] = 60;

refresh for what ? to search for a new email in the inbox ? i suppose it needs to authenticate again ?

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: JohnDoh on April 09, 2020, 12:38:30 PM
refresh interval is how often the server is polled for new messages while the user is on the mailbox screen.

as for your dovecot errors, are you sure its coming from roundcube? are there corresponding failed logins noted in the roundcube error log?
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 09, 2020, 12:45:58 PM
The /var/www/html/logs dir is empty but i don't know if login_errors are enabled.

I will check now

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 09, 2020, 12:50:21 PM
In the syslog logs there are some failed login errors but are a lot less, errors are not each 60 seconds

I don't know why now, the old version 1.0.1 has some imap failed login errors but not so many.

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: JohnDoh on April 09, 2020, 02:19:32 PM
But the login entries you posted come from dovecot right? So unless there are corresponding entries in your roundcube logs then the requests are not coming from roundcube.
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 10, 2020, 03:35:10 AM
Yes the previous logs were from dovecot.

I suppose maybe is it the imapproxy, but its configuration is not changed in the while.

And i don't understand because the authentication error is each one after 60 seconds from the previous for the same user.

Do you have some imapproxy software to reccomend ?

We use UWimapproxy maybe there is a better one ?

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: JohnDoh on April 10, 2020, 03:55:31 AM
Quote
I suppose maybe is it the imapproxy
how do you not know for sure where the request are coming from? The dovecot logs have the remote IP and and I know for sure Roundcube logs errors and I presume your imapproxy has logs.
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 10, 2020, 05:44:11 AM
On dovecot (imap server) i have login errors coming from my roundcube IP addresses (remember i have a load balancing setup), so i know for sure they are coming from roundcube servers.

I know that on the imapproxy i have these entries:

Apr 10 11:31:50 webmail1 in.imapproxyd[812]: LOGIN: 'XXXXX' (127.0.0.1:51986) failed: non-OK server response to LOGIN command: NO [AUTHENTICATIONFAILED] Authentication failed.

Apr 10 11:31:50 webmail1new roundcube: IMAP Error: Login failed for XXXXX from <IPADDRESS>. LOGIN: Authentication failed. in /var/www/html/program/lib/Roundcube/rcube_imap.php on line 184 (POST /?_task=login?_task=login&_action=login)

These are from yesterday from same user

Apr  9 17:26:55 webmail1 in.imapproxyd[812]: LOGIN: 'YYYYYYY' (127.0.0.1:52936) failed: non-OK server response to LOGIN command: NO [AUTHENTICATIONFAILED] Authentication failed.

Apr  9 17:27:55 webmail1 in.imapproxyd[812]: LOGIN: 'YYYYYYY' (127.0.0.1:53260) failed: non-OK server response to LOGIN command: NO [AUTHENTICATIONFAILED] Authentication failed.

Apr  9 17:28:59 webmail1 in.imapproxyd[812]: LOGIN: 'YYYYYYY' (127.0.0.1:53648) failed: non-OK server response to LOGIN command: NO [AUTHENTICATIONFAILED] Authentication failed.

Apr  9 17:29:55 webmail1 in.imapproxyd[812]: LOGIN: 'YYYYYYY' (127.0.0.1:54120) failed: non-OK server response to LOGIN command: NO [AUTHENTICATIONFAILED] Authentication failed.

Apr  9 17:30:55 webmail1 in.imapproxyd[812]: LOGIN: 'YYYYYYY' (127.0.0.1:54474) failed: non-OK server response to LOGIN command: NO [AUTHENTICATIONFAILED] Authentication failed.

and so on up to 17:44:55 each minute at 55 seconds and i don't know why, anyway all the night i have no authentication problems at all, i'll check today if these problems occurs again (i don't think a user can digit the wrong password each minute at the exact same seconds each time for 20 times).

Claudio
Claudio

Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 10, 2020, 10:24:47 AM
anyway today the authentication errors seems come back to normal level, anymore i see all these messages each minute.

maybe a brute force attack on roundcube ? but they have to know the username of those users or there were some security flaws after v1.0.12 was released and never fixed ?

Anyway i will move very soon to v1.2.9 at least so we will be in LTS security support and if possibile we will move then to the latest version.

I saw that v1.2.9 works on mobile devices, finally in landscape i can see the message titles and can read the messages, is it not still the right mobile interface but at least it is usable on mobile phones.

Thanks for now
Claudio
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 15, 2020, 10:03:13 AM
Hi all,

i'm again here, i moved a cloned webmail machine from v1.0.2 to v.1.2.9 without any apparent problem.

I moved from php v5.4 to php v7.3.16 (latest available) because v1.3.x needs php > 5.4 so i don't know if the problems are related to the new PHP

Today i tried to move to v1.3.10 latest LTS version, the upgrade gone well, no errors, but then i had 3 problems, 1 was fixed but i would like to know why it is there now, 1 is a layout problem and 1 can't make me use roundcube.

These are the problems i had:

1) php sessions that before worked without problem, now give problem with the uid

Apr 15 12:33:18 webmailnew httpd-webmailnew[14059]: [proxy_fcgi:error] [pid 14100] [client
 10.15.66.13:51177] AH01071: Got error 'PHP message: PHP Warning:  session_start(): Session data file
is not created by your uid in /var/www/html/program/lib/Roundcube/rcube_session.php on line 129PHP mes
sage: PHP Warning:  session_start(): Failed to read session data: files (path: /XXX/XXX/webmailnew/phpsessions) in /var/www/html/program/lib/Roundcube/rcube_session.php on
 line 129', referer: https://webmailnew/?_task=login

The session storage is a shared storage where i can't change the owner of the folder, but apache user (that runs httpd) can write/read without problems.

For now I solved this one moving the sessions from php to DB but i would like to know why it is not working anymore.

2) I can connect to roundcube, login, read the emails, download the attachments, but i can't send emails anymore, it gives always

Apr 15 15:43:26 webmailnew httpd-webmailnew[25254]: [proxy_fcgi:error] [pid 25260] [client
 10.15.66.13:51691] AH01071: Got error 'PHP message: ERROR: STARTTLS failed ()PHP message: ERROR: Inva
lid response code received from server (-1)PHP message: ERROR: Invalid response code received from ser
ver (-1)', referer: https://webmailnew/?_task=mail&_action=compose&_id=3002398545e970db56a
5a1&_search=aa79f5c436586296d1b7e8e366b4a611

Before moving to roundcube v1.3.10 all was working really good.

I remember you that i'm using imapproxy on the roundcube server.

3) i see the new roundcube layout has 3 sections divided in columns, one column for imap folders, one to list the title of emails in the inbox and the third one to show the email content, is it possible to move the section for the email content in another place ? mobile devices can't display very well this
 roundcube layout, neither the login page (it is some way trunked), neither the inbox contents, i prefer v1.2.9 layout is it possible to revert to it ? if yes how ?

I didn't change any configuration settings in the config.inc.php and it worked like a charm before the upgrade to v1.3.10

Thanks for any suggestion
Claudio
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 15, 2020, 10:28:06 AM
I enabled log to 4 and smtp_debug

in /var/log/maillog i found this

Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Recv: 220 lnf.infn.it ESMTP server; Wed, 15 Apr 2020 16:20:23 +0200
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Send: EHLO webmailnew
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Recv: 250-smtp Hello webmailnew [XXX.XXX.XXX.XXX], pleased to meet you
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Recv: 250-ENHANCEDSTATUSCODES
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Recv: 250-PIPELINING
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Recv: 250-8BITMIME
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Recv: 250-SIZE 30000000
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Recv: 250-DSN
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Recv: 250-AUTH GSSAPI
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Recv: 250-STARTTLS
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Recv: 250-DELIVERBY
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Recv: 250 HELP
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Send: STARTTLS
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Recv: 220 2.0.0 Ready to start TLS
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Send: RSET
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Recv: \x16\x03\x03\x01M\x0c
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Send: QUIT
Apr 15 16:20:24 webmailnew roundcube: <hnfdc92e> Recv: \x13\x0bEntrust.net1;09\x06\x03U\x04\x0b\x132www.entrust.net/CPS incorp. by ref. (limits liab.)1%0#\x06\x03U\x04\x0b\x13\x1c(c) 1999 Entrust.net Limited1:08\x06\x03U\x04\x03\x131Entrust.net Secure Server Certification Authority

Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 15, 2020, 10:43:02 AM
my config.inc.php

$config['smtp_server'] = 'tls://server.domain';

$config['smtp_port'] = 587;

$config['smtp_user'] = '%u';

$config['smtp_pass'] = '%p';

$config['debug_level'] = 4;

$config['smtp_debug'] = true;
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 15, 2020, 10:43:54 AM
We are using LDAP something is changed ?

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 15, 2020, 11:26:45 AM
The strange thing is that i have no log file for roundcube in the /var/www/html/logs/ folder

Maybe it is normal i send all to syslog.

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: JohnDoh on April 15, 2020, 01:08:17 PM
Quote
1) php sessions that before worked without problem, now give problem with the uid
no idea, sorry

Quote
2) I can connect to roundcube, login, read the emails, download the attachments, but i can't send emails anymore, it gives always
SSL/TLS certificate verification was enabled by default starting with PHP 5.6 perhaps this is the issue. see here https://github.com/roundcube/roundcubemail/wiki/FAQ#problems-connecting-imapsmtp-server-via-ssltls

Quote
3) i see the new roundcube layout has 3 sections divided in columns
The Larry skin has 3 layout modes - list (no preview pane), widescreen (3 columns), desktop (preview pane below the message list). The layout mode can be changed from the settings screen or from the gear/cog icon in the top left coner of the message list

Quote
mobile devices can't display very well this
The Larry skin is not designed to work on mobiles. Support for mobiles (and tablets) was added to Roundcube in versoin 1.4 as part of the Elastic skin.
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 16, 2020, 04:11:10 AM
Quote
1) php sessions that before worked without problem, now give problem with the uid
no idea, sorry

No problem i will switch to DB, just curios

Quote
2) I can connect to roundcube, login, read the emails, download the attachments, but i can't send emails anymore, it gives always
SSL/TLS certificate verification was enabled by default starting with PHP 5.6 perhaps this is the issue. see here https://github.com/roundcube/roundcubemail/wiki/FAQ#problems-connecting-imapsmtp-server-via-ssltls

Ok the problem seems this, if i disable the verify_peer all works, but now i want to enable it but i can't seems to resolve it, my smtp certificate use an intermediate CA, so i have

certficate -> intermediate ca -> root ca

in the local ca files can i put inside both ? i need to respect an order ? if yes can you explain it, please ?

Quote
3) i see the new roundcube layout has 3 sections divided in columns
The Larry skin has 3 layout modes - list (no preview pane), widescreen (3 columns), desktop (preview pane below the message list). The layout mode can be changed from the settings screen or from the gear/cog icon in the top left coner of the message list

is it possible to set it for all users ? a general setting i mean.

Quote
mobile devices can't display very well this
The Larry skin is not designed to work on mobiles. Support for mobiles (and tablets) was added to Roundcube in versoin 1.4 as part of the Elastic skin.

version 1.2.9 worked good on mobile devices in landscape mode

thanks for now
Claudio
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 16, 2020, 04:17:09 AM
Ok i solved the problem with the CA file

i put intermediate e root ca in the smtp-ca.crt file and now i can send messages

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 16, 2020, 05:01:50 AM
I added 2 images one for v1.2.9 appearance and one for v1.3.10 appearance

Is it possible to switch v1.3.10 like v.1.2.9 for all users ?

If yes which file i have to modify and how ?

Thanks in advance
Claudio

Title: Re: Upgrading from a 1.0 release
Post by: JohnDoh on April 16, 2020, 12:50:50 PM
Have a look at the `layout` config option.
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 17, 2020, 05:09:54 AM
Thanks john

Finally i moved my cloned VM to v1.4.3

i have seen that defaults config has the elastic skin enabled, but users that had larry will see still larry and not elastic, they need to change it manually ?

is there a script or something that change larry to elastic in the DB ?

or is there a way to change elastic to default for all ?

Elastic works very well on mobile devices.

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 17, 2020, 05:16:37 AM
I suppose that the elastic skin works automatically, i mean

while for larry skin i can choose 3 columns, 2 columns or list

for elastic i can't choose nothing, we have on desktop always 3 panels-columns

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 17, 2020, 06:25:06 AM
And another question.

I have installed the rcguard recaptcha plugin, it works very well, but when i logout, the main login page appears but not the recaptcha box, i need to it reload to have it shown.

I had this problem with all the versions of roundcube starting from v1.0.12, v1.1.12, v1.2.9, v1.3.10 up to 1.4.3

Is it normal ? or i need to modify something to have it shown again when i logout from roundcube.

A page reload makes it shown again but i would like to have it shown automatically after the logout

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: JohnDoh on April 17, 2020, 11:57:03 AM
Quote
i have seen that defaults config has the elastic skin enabled, but users that had larry will see still larry and not elastic, they need to change it manually ?
Yes, user settings override the defaults unless the option is sepcificed in your `dont_override` config. If you want to change existing users' settings but still allow them to modify them if they want there is a script `bin/moduserprefs.sh` which is shipped with roundcube. run `bin/moduserprefs.sh help` for usage information.

Quote
for elastic i can't choose nothing, we have on desktop always 3 panels-columns
The Elastic skin supports the `widescreen` layout option only.

Quote
I have installed the rcguard recaptcha plugin
Please contact the plugin author for support.
Title: Re: Upgrading from a 1.0 release
Post by: soprano on April 19, 2020, 09:30:18 AM
Ok, thanks johndoh for all your helps and hints.

I think i can live with these "problems" for now.

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: soprano on May 19, 2020, 11:59:18 AM
Sorry again to disturb you, but i searched and didn't find how to solve it.

In the elastic skin i can see emails divided for threads while in the larry skin there is a threads icon in the elastic skin it is not present.

I searched Thread in the options under order for

but it is not there

i'm using v1.4.4

i attach a jpeg (language is italian)

thanks for any help

Claudio
Title: Re: Upgrading from a 1.0 release
Post by: JohnDoh on May 19, 2020, 12:20:32 PM
it sounds like you are looking in the right place. the option is automatically hidden if your imap server does not support threads. the option is also shown in the settings section in the Folders tab for each folder there is an option called "List view mode". Again this option should be hidden if your imap server does not support threads.