Re: [SOGo] ANN: SOGo v2.3.1
Am 04.08.2015 um 22:21 schrieb Michal Kminek mkmi...@getnet.cz: Dne 4.8.2015 v 11:38 Marc Patermann napsal(a): Hi, Am 30.07.2015 um 15:05 Uhr schrieb Chris Coleman: On 7/30/2015 8:57 AM, Christian Mack wrote: Am 30.07.2015 um 14:24 schrieb Márcio Merlone: On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? No! You have to do that manually. I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. whatever is done, remember: The db don't have to be on the same host as the SOGo daemon is! We have i.e. have multiple SOGo frontend server and a postgresql cluster (with pgpool) in the background. Single server scenarios are not all there is. Marc I agree but SOGo always accesses its database using a defined connection from sogo.conf. The same connection can be used to deliver a DB update. It's not important if the database is on the same server. I have no experience with pgpool but I believe any DB update can be delivered too. It would be really helpful if these DB changes come with the corresponding binary packages. Michal Just as an idea, if binary might not be achievable or too many efforts - maybe the DB upgrade script can be embedded in PHP. Right after the update is done you call a PHP script (which will have access to sogo.conf) ether manually or this is done automatically with the first access… Thomas -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
Hi, Am 30.07.2015 um 15:05 Uhr schrieb Chris Coleman: On 7/30/2015 8:57 AM, Christian Mack wrote: Am 30.07.2015 um 14:24 schrieb Márcio Merlone: On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? No! You have to do that manually. I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. whatever is done, remember: The db don't have to be on the same host as the SOGo daemon is! We have i.e. have multiple SOGo frontend server and a postgresql cluster (with pgpool) in the background. Single server scenarios are not all there is. Marc -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
Dne 4.8.2015 v 11:38 Marc Patermann napsal(a): Hi, Am 30.07.2015 um 15:05 Uhr schrieb Chris Coleman: On 7/30/2015 8:57 AM, Christian Mack wrote: Am 30.07.2015 um 14:24 schrieb Márcio Merlone: On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? No! You have to do that manually. I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. whatever is done, remember: The db don't have to be on the same host as the SOGo daemon is! We have i.e. have multiple SOGo frontend server and a postgresql cluster (with pgpool) in the background. Single server scenarios are not all there is. Marc I agree but SOGo always accesses its database using a defined connection from sogo.conf. The same connection can be used to deliver a DB update. It's not important if the database is on the same server. I have no experience with pgpool but I believe any DB update can be delivered too. It would be really helpful if these DB changes come with the corresponding binary packages. Michal -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
Dne 31.7.2015 v 18:25 Ben napsal(a): I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. It is not that easy. It first would have to scan your config, in order to find which DBMS you use. Some are even using multiple DBs. I think it would be relatively straight-forward and avoid lots of upgrade confusion for SOGo to store in the db the db schema version. Then when SOGo starts up and connects to the db, it checks that the db schema version matches the version it is expecting. If it isn't, it throws an error and stops. This forces the admin to read the instructions and do the db backup, run the upgrade script, etc. But it prevents someone from doing a quick upgrade and running a new version SOGo against an old db schema and having weird problems, etc. Ben I also agree. It would be nice if all database changes were applied when upgrading binary packages like rpm. Just imagine a scenario when a new major update is released and installed automatically except its database part and the responsible admin is out somewhere and SOGo stops operating after a service reload. All packages are installed under root user and it means that upgrade scripts can see SOGo configuration and react appropriately. Best regards, Michal Kminek -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. It is not that easy. It first would have to scan your config, in order to find which DBMS you use. Some are even using multiple DBs. I think it would be relatively straight-forward and avoid lots of upgrade confusion for SOGo to store in the db the db schema version. Then when SOGo starts up and connects to the db, it checks that the db schema version matches the version it is expecting. If it isn't, it throws an error and stops. This forces the admin to read the instructions and do the db backup, run the upgrade script, etc. But it prevents someone from doing a quick upgrade and running a new version SOGo against an old db schema and having weird problems, etc. Ben -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
On 7/30/2015 8:57 AM, Christian Mack wrote: Hello Am 30.07.2015 um 14:24 schrieb Márcio Merlone: On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? No! You have to do that manually. Kind regards, Christian Mack I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? Regards, -- *Marcio Merlone* -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
Hello Am 30.07.2015 um 14:24 schrieb Márcio Merlone: On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? No! You have to do that manually. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416 smime.p7s Description: S/MIME Cryptographic Signature
Re: [SOGo] ANN: SOGo v2.3.1
Am 30.07.2015 um 15:05 schrieb Chris Coleman: On 7/30/2015 8:57 AM, Christian Mack wrote: Hello Am 30.07.2015 um 14:24 schrieb Márcio Merlone: On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? No! You have to do that manually. Kind regards, Christian Mack I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. It is not that easy. It first would have to scan your config, in order to find which DBMS you use. Some are even using multiple DBs. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416 smime.p7s Description: S/MIME Cryptographic Signature
Re: [SOGo] ANN: SOGo v2.3.1
On 2015-07-30 15:05, Chris Coleman wrote: On 7/30/2015 8:57 AM, Christian Mack wrote: Hello Am 30.07.2015 um 14:24 schrieb Márcio Merlone: On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? No! You have to do that manually. Kind regards, Christian Mack I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. Assuming it doesn't have any bugs and blows up your whole database. You should read the notes anyway, because schema migrations aren't the only changes between versions. -- Mit freundlichen Grüßen, / Best Regards, Sven Schwedas Systemadministrator TAO Beratungs- und Management GmbH | Lendplatz 45 | A - 8020 Graz Mail/XMPP: sven.schwe...@tao.at | +43 (0)680 301 7167 http://software.tao.at signature.asc Description: OpenPGP digital signature
Re: [SOGo] ANN: SOGo v2.3.1
On 7/30/2015 9:09 AM, Sven Schwedas wrote: On 2015-07-30 15:05, Chris Coleman wrote: On 7/30/2015 8:57 AM, Christian Mack wrote: Hello Am 30.07.2015 um 14:24 schrieb Márcio Merlone: On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? No! You have to do that manually. Kind regards, Christian Mack I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. Assuming it doesn't have any bugs and blows up your whole database. You should read the notes anyway, because schema migrations aren't the only changes between versions. Reading notes is good, the upgrade script could and probably should take an automatic backup of the database (similar to a system restore point) before applying schema updates. mysqldump. pg_dump. The upgrade script including the schema upgrades, would minimize the human element of errors, forgetfulness, typing error, copy/paste error, leading to blowing up the database. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
On 07/30/2015 09:14 AM, Christian Mack wrote: Am 30.07.2015 um 15:05 schrieb Chris Coleman: On 7/30/2015 8:57 AM, Christian Mack wrote: Hello Am 30.07.2015 um 14:24 schrieb Márcio Merlone: On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? No! You have to do that manually. Kind regards, Christian Mack I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. It is not that easy. It first would have to scan your config, in order to find which DBMS you use. Some are even using multiple DBs. Kind regards, Christian Mack I nominate a having a warning PLEASE READ INSTRUCTIONS before upgrading! It's very clearly spelled out in the instructions (as well as in various places on this mailing list) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
On 7/30/2015 9:14 AM, Christian Mack wrote: Am 30.07.2015 um 15:05 schrieb Chris Coleman: On 7/30/2015 8:57 AM, Christian Mack wrote: Hello Am 30.07.2015 um 14:24 schrieb Márcio Merlone: On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? No! You have to do that manually. Kind regards, Christian Mack I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. It is not that easy. It first would have to scan your config, in order to find which DBMS you use. Some are even using multiple DBs. Kind regards, Christian Mack Yes, but when these deb/rpm scripts install SOGo for the first time, don't they rely on classes which create the db with whichever supported DBMS the admin has chosen (mysql postrgres or oracle), install the latest schema, and from then onward, interact with the db using classes? Upgrading existing schema should mean query the db class for schema version, and invoke the schema upgrader by supplying path names for the relevant differential schema upgrade files. This is how many/most application projects handle db schema upgrades. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
Make a separate upgrade rpm/deb and make it a dependency on upgrading existing install. During it's install stop output text to screen to look at the users guide as well as a list of the detected databases and ask for which ones to upgrade and the then prompt for the dbuser and pass required. The users guide would be referred for in depth analysis of the procedure. If they want to study the users guide they can opt out of the upgrade right there. Simple user friendly and problem prevention way to do upgrades. signaturehtmlsteve *Steve Boley* http://www.nams.net On 7/30/2015 8:09 AM, Sven Schwedas wrote: On 2015-07-30 15:05, Chris Coleman wrote: On 7/30/2015 8:57 AM, Christian Mack wrote: Hello Am 30.07.2015 um 14:24 schrieb Márcio Merlone: On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? No! You have to do that manually. Kind regards, Christian Mack I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. Assuming it doesn't have any bugs and blows up your whole database. You should read the notes anyway, because schema migrations aren't the only changes between versions. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
Am 30.07.2015 um 15:32 schrieb Chris Coleman: On 7/30/2015 9:14 AM, Christian Mack wrote: Am 30.07.2015 um 15:05 schrieb Chris Coleman: On 7/30/2015 8:57 AM, Christian Mack wrote: Hello Am 30.07.2015 um 14:24 schrieb Márcio Merlone: On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? No! You have to do that manually. Kind regards, Christian Mack I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. It is not that easy. It first would have to scan your config, in order to find which DBMS you use. Some are even using multiple DBs. Kind regards, Christian Mack Yes, but when these deb/rpm scripts install SOGo for the first time, don't they rely on classes which create the db with whichever supported DBMS the admin has chosen (mysql postrgres or oracle), install the latest schema, and from then onward, interact with the db using classes? No, there is no DB creation rpm/deb. SOGo creates the tables on startup after configuration and creation of the databases through the admin. And an admin can choose to use different DBs for different parts. E.g. use a MySQL with memory backend for sessions, an oracle for user data and an postgresql for user authentication data. With that you have all the connectors for those DBMS installed. Which one to upgrade is only defined in sogo.conf. Upgrading existing schema should mean query the db class for schema version, and invoke the schema upgrader by supplying path names for the relevant differential schema upgrade files. This is how many/most application projects handle db schema upgrades. Partly this is possible, but as I said needs to parse the SOGo config first. Therefore this is not as trivial as it seems. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416 smime.p7s Description: S/MIME Cryptographic Signature
Re: [SOGo] ANN: SOGo v2.3.1
On 7/30/2015 11:59 AM, Christian Mack wrote: Am 30.07.2015 um 15:32 schrieb Chris Coleman: On 7/30/2015 9:14 AM, Christian Mack wrote: Am 30.07.2015 um 15:05 schrieb Chris Coleman: On 7/30/2015 8:57 AM, Christian Mack wrote: Hello Am 30.07.2015 um 14:24 schrieb Márcio Merlone: On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? No! You have to do that manually. Kind regards, Christian Mack I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. It is not that easy. It first would have to scan your config, in order to find which DBMS you use. Some are even using multiple DBs. Kind regards, Christian Mack Yes, but when these deb/rpm scripts install SOGo for the first time, don't they rely on classes which create the db with whichever supported DBMS the admin has chosen (mysql postrgres or oracle), install the latest schema, and from then onward, interact with the db using classes? No, there is no DB creation rpm/deb. SOGo creates the tables on startup after configuration and creation of the databases through the admin. And an admin can choose to use different DBs for different parts. E.g. use a MySQL with memory backend for sessions, an oracle for user data and an postgresql for user authentication data. With that you have all the connectors for those DBMS installed. Which one to upgrade is only defined in sogo.conf. Upgrading existing schema should mean query the db class for schema version, and invoke the schema upgrader by supplying path names for the relevant differential schema upgrade files. This is how many/most application projects handle db schema upgrades. Partly this is possible, but as I said needs to parse the SOGo config first. Therefore this is not as trivial as it seems. Kind regards, Christian Mack It sounds what's needed is to add a generalized class to parse a standard .conf or .ini file. The good news is, many working classes have already been developed, ready to be reused, in many languages, python, php, C, perl, you name it. http://stackoverflow.com/questions/20708627/parsing-a-config-file Which language would SGOo invoke this code from? Is it the admin section of the SOGo web based gui, which is written in Objective-C ? -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
On 7/30/2015 9:30 AM, Steve Ankeny wrote: On 07/30/2015 09:14 AM, Christian Mack wrote: Am 30.07.2015 um 15:05 schrieb Chris Coleman: On 7/30/2015 8:57 AM, Christian Mack wrote: Hello Am 30.07.2015 um 14:24 schrieb Márcio Merlone: On 24-07-2015 08:07, Steve Ankeny wrote: The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) Since I run Ubuntu, I assume the install/upgrade procedure from apt already does that, is this correct? No! You have to do that manually. Kind regards, Christian Mack I nominate adding the database schema upgrade script to the deb and rpm install/upgrade scripts. It would need to detect the current db schema version and apply the appropriate db updates. Which it surely does already... That automation alone would probably reduce friction by 5%. It is not that easy. It first would have to scan your config, in order to find which DBMS you use. Some are even using multiple DBs. Kind regards, Christian Mack I nominate a having a warning PLEASE READ INSTRUCTIONS before upgrading! It's very clearly spelled out in the instructions (as well as in various places on this mailing list) Yes, but I believe the goal is (and needs to be) zero-effort upgrades, to whatever extent possible within reason. For the admins using 3 different database engines, to provide separate login (microsoft ldap), session (mysql in memory), and data storage (postgres) , to achieve extreme high performance, maybe we can let them risk manually running db schema upgrade scripts (and run the wrong versions of the schema scripts, or completely forget to run them), but even then, a config file parser class should automatically extract those 3 sets of db credentials from sogo.conf and perform automated schema upgrades. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
It’s the same for me, I would also like to upgrade from 2.2.16. Where do I find the information about the database upgrade script procedure? There seemed to be a lot of issues with it - will it run smoothly? Thanks a lot in advance. Thomas Am 23.07.2015 um 23:30 schrieb Ludovic Marcotte lmarco...@inverse.ca: On 23/07/2015 17:23, Kai-Uwe Rommel wrote: What about the database update script? Is that no longer needed? I did not yet upgrade to 2.3.0 but still run 2.2.17a. If you're upgrading from a version prior to 2.3.0, you still need to run the script. -- Ludovic Marcotte lmarco...@inverse.ca mailto:lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca http://inverse.ca/ Inverse inc. :: Leaders behind SOGo (http://sogo.nu http://sogo.nu/) and PacketFence (http://packetfence.org http://packetfence.org/) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
The only issues I remember with the running of the script were -- (1) users fail to run it (2) or, they run the wrong script Instructions are *always* at the back pages of the Installation Guide -- http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58) On 07/24/2015 01:08 AM, Thomas Trepper wrote: It’s the same for me, I would also like to upgrade from 2.2.16. Where do I find the information about the database upgrade script procedure? There seemed to be a lot of issues with it - will it run smoothly? Thanks a lot in advance. Thomas -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
On 7/23/2015 4:42 PM, christ...@cmjscripter.net wrote: and seems to run smoothly on Outlook 2015 2015? Maybe you mean 2013? Or even 2016? -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v2.3.1
Hi. 2013: Outlook/15.0 (15.0.4737.1000; MSI; x64) i mixed up the version number. nonetheless it's still running, it just have some troubles with keeping the headers like List-* and In-Reply-To On 24-07-2015 13:20, Tanstaafl wrote: On 7/23/2015 4:42 PM, christ...@cmjscripter.net wrote: and seems to run smoothly on Outlook 2015 2015? Maybe you mean 2013? Or even 2016? smime.p7s Description: S/MIME Cryptographic Signature
Re: [SOGo] ANN: SOGo v2.3.1
On 23/07/2015 17:23, Kai-Uwe Rommel wrote: What about the database update script? Is that no longer needed? I did not yet upgrade to 2.3.0 but still run 2.2.17a. If you're upgrading from a version prior to 2.3.0, you still need to run the script. -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] ANN: SOGo v2.3.1
The Inverse Team is pleased to announce the immediate availability of SOGo 2.3.1. This is a minor release of SOGo which focuses on improved stability over previous versions. What is SOGo SOGo is a free and modern scalable groupware server. It offers shared calendars, address books and emails through your favorite Web browser or by using a native client such as Mozilla Thunderbird and Lightning, Apple Calendar and Address Book (Mac OS X and iOS) and Microsoft Outlook.SSOGo is standard-compliant and supports CalDAV, CardDAV and reuses existing IMAP, SMTP and database servers - making the solution easy to deploy and interoperable with many applications. SOGo features: * Scalable architecture suitable for deployments from dozen to many thousand users * Rich Web-based interface that shares the look and feel, the features and the data of Mozilla Thunderbird and Lightning * Improved integration with Mozilla Thunderbird and Lightning by using the SOGo Connector and the SOGo Integrator * Native compatibility for Microsoft Outlook 2003, 2007, 2010 and 2013 * Two-way synchronization support with any Microsoft ActiveSync-capable device (Apple iOS, Android, Windows Phone, BlackBerry 10) or Outlook 2013 * Excellent native integration with Apple software (Mac OS X and iOS) and Android-based devices and many more! SOGo and our connectors are completely free. Changes from the previous release *Enhancements* * improved EAS speed, especially when fetching big attachments * now always enforce the organizer's default identity in appointments * improved the handling of default calendar categories/colors (#3200) * added support for DeletesAsMoves over EAS * added create-folder subcommand to sogo-tool to create contact and calendar folders * group mail addresses can be used as recipient in Outlook * added 'ActiveSync' module constraints * added Slovenian translation - thanks to Jens Riecken * added Chinese (Taiwan) translation *Bug fixes* * EAS's GetItemEstimate/ItemOperations now support fetching mails and empty folders * fixed some rare cornercases in multidomain configurations * properly escape folder after creation using EAS (#3237) * fixed potential organizer highjacking when using EAS (#3131) * properly support big characters in EAS and fix encoding QP EAS error for Outlook (#3082) * properly encode id of DOM elements in Address Book module (#3239, #3245) * fixed multi-domain support for sogo-tool backup/restore (#2600) * fixed data ordering in events list of Calendar module (#3261) * fixed data ordering in tasks list of Calendar module (#3267) * Android EAS Lollipop fixes (#3268 and #3269) * improved EAS email flagging handling (#3140) * fixed computation of GlobalObjectId (#3235) * fixed EAS conversation ID issues on BB10 (#3152) * fixed CR/LF printing in event's description (#3228) * optimized Calendar module in multidomain configurations Seehttp://www.sogo.nu/bugs/changelog_page.php?project_id=1for closed tickets andhttps://github.com/inverse-inc/sogo/commits/SOGo-2.3.1for the complete change log. Getting SOGo SOGo is free software and is distributed under the GNU GPL. As such, you are free to download and try it by visiting the following page: http://www.sogo.nu/downloads/backend.html You can also download the sources by following the instructions on this page: http://www.sogo.nu/development/source_code.html Frontend clients such as Mozilla Thunderbird, Mozilla Lightning (Inverse Edition), SOGo Connector and SOGo Integrator extensions are available for download from: http://www.sogo.nu/downloads/frontends.html Documentation about the installation and configuration of SOGo, Thunderbird or the native Microsoft Outlook compatibility layer is available from: http://www.sogo.nu/downloads/documentation.html You can also try our online SOGo demo at: http://www.sogo.nu/tour/online_demo.html Upgrading to v2.3.1 No special measure needs to be taken when upgrading. How can I help ? SOGo is a collaborative effort in order to create the best Free and Open Source groupware solution. There are multiple ways you can contribute to the project: * Documentation reviews, enhancements and translations * Write test cases - if you know Python, join in! * Feature requests or by sharing your ideas (see the roadmap) * Participate to the discussion in mailing lists * Patches for bugs or enhancements (http://www.sogo.nu/bugs) * Provide new translations (http://sogo.nu/english/support/faq/article/how-to-translate-sogo-in-another-language-2.html) Feel free to send us your questions. You can also post them to the SOGo mailing list:http://sogo.nu/lists/ Getting Support For any questions, do not hesitate to contact us by writing tosupp...@inverse.ca mailto:supp...@inverse.ca Customer support packages for SOGo are available
Re: [SOGo] ANN: SOGo v2.3.1
Just had to say NICE Work with this update. for the first time, Activesync runs without issues for me, on Windows mail on Windows 8.1 and seems to run smoothly on Outlook 2015 to BIG thumbs up from me, keep up the good work Sendt fra Windows Mail Fra: Ludovic Marcotte Sendt: torsdag, 23. juli 2015 22:25 Til: users@sogo.nu The Inverse Team is pleased to announce the immediate availability of SOGo 2.3.1. This is a minor release of SOGo which focuses on improved stability over previous versions. What is SOGo SOGo is a free and modern scalable groupware server. It offers shared calendars, address books and emails through your favorite Web browser or by using a native client such as Mozilla Thunderbird and Lightning, Apple Calendar and Address Book (Mac OS X and iOS) and Microsoft Outlook. S SOGo is standard-compliant and supports CalDAV, CardDAV and reuses existing IMAP, SMTP and database servers - making the solution easy to deploy and interoperable with many applications. SOGo features: Scalable architecture suitable for deployments from dozen to many thousand users Rich Web-based interface that shares the look and feel, the features and the data of Mozilla Thunderbird and Lightning Improved integration with Mozilla Thunderbird and Lightning by using the SOGo Connector and the SOGo Integrator Native compatibility for Microsoft Outlook 2003, 2007, 2010 and 2013 Two-way synchronization support with any Microsoft ActiveSync-capable device (Apple iOS, Android, Windows Phone, BlackBerry 10) or Outlook 2013 Excellent native integration with Apple software (Mac OS X and iOS) and Android-based devices and many more! SOGo and our connectors are completely free. Changes from the previous release Enhancements improved EAS speed, especially when fetching big attachments now always enforce the organizer's default identity in appointments improved the handling of default calendar categories/colors (#3200) added support for DeletesAsMoves over EAS added create-folder subcommand to sogo-tool to create contact and calendar folders group mail addresses can be used as recipient in Outlook added 'ActiveSync' module constraints added Slovenian translation - thanks to Jens Riecken added Chinese (Taiwan) translation Bug fixes EAS's GetItemEstimate/ItemOperations now support fetching mails and empty folders fixed some rare cornercases in multidomain configurations properly escape folder after creation using EAS (#3237) fixed potential organizer highjacking when using EAS (#3131) properly support big characters in EAS and fix encoding QP EAS error for Outlook (#3082) properly encode id of DOM elements in Address Book module (#3239, #3245) fixed multi-domain support for sogo-tool backup/restore (#2600) fixed data ordering in events list of Calendar module (#3261) fixed data ordering in tasks list of Calendar module (#3267) Android EAS Lollipop fixes (#3268 and #3269) improved EAS email flagging handling (#3140) fixed computation of GlobalObjectId (#3235) fixed EAS conversation ID issues on BB10 (#3152) fixed CR/LF printing in event's description (#3228) optimized Calendar module in multidomain configurations See http://www.sogo.nu/bugs/changelog_page.php?project_id=1 for closed tickets and https://github.com/inverse-inc/sogo/commits/SOGo-2.3.1 for the complete change log. Getting SOGo SOGo is free software and is distributed under the GNU GPL. As such, you are free to download and try it by visiting the following page: http://www.sogo.nu/downloads/backend.html You can also download the sources by following the instructions on this page: http://www.sogo.nu/development/source_code.html Frontend clients such as Mozilla Thunderbird, Mozilla Lightning (Inverse Edition), SOGo Connector and SOGo Integrator extensions are available for download from: http://www.sogo.nu/downloads/frontends.html Documentation about the installation and configuration of SOGo, Thunderbird or the native Microsoft Outlook compatibility layer is available from: http://www.sogo.nu/downloads/documentation.html You can also try our online SOGo demo at: http://www.sogo.nu/tour/online_demo.html Upgrading to v2.3.1 No special measure needs to be taken when upgrading. How can I help ? SOGo is a collaborative effort in order to create the best Free and Open Source groupware solution. There are multiple ways you can contribute to the project: Documentation reviews, enhancements and translations Write test cases - if you know Python, join in! Feature requests or by sharing your ideas (see the roadmap) Participate to the discussion in mailing lists Patches for bugs or enhancements (http://www.sogo.nu/bugs) Provide new translations (http://sogo.nu/english/support/faq/article/how-to-translate-sogo-in-another-language-2.html) Feel free to send us your questions. You can also post them to the SOGo mailing list: http://sogo.nu/lists/ Getting Support For any questions, do not
Re: [SOGo] ANN: SOGo v2.3.1
users-requ...@sogo.nu wrote on 23.07.2015 22:25:28: Upgrading to v2.3.1 No special measure needs to be taken when upgrading. What about the database update script? Is that no longer needed? I did not yet upgrade to 2.3.0 but still run 2.2.17a. Kai-Uwe Rommel kai-uwe.rom...@ars.de Telefon+Mobil +49 89 32468-120 Veranstaltungshinweis: ARS Konferenz ARScon ? Strategien von morgen am 15.10.2015 in der Allianz Arena Muenchen http://www.ars.de/konferenz ARS Computer und Consulting GmbH, http://www.ars.de Ridlerstrasse 37, 80339 Muenchen, Deutschland Individuelle Softwareentwicklung, Beratung und Projekte IBM Software, IBM Lizenzmanagement IT-Infrastrukturservices Handelsregister Muenchen, HRB 101829, USt-ID: DE 155 068 909 Geschaeftsfuehrer: Michael Arbesmeier, Kai-Uwe Rommel, Roland Schock, Joachim Gucker -- users@sogo.nu https://inverse.ca/sogo/lists
