[SOGo] Adding contacs fails

2024-04-15 Thread Richard
Hi,
I'm trying to enable users to be able to save new contacts into their
address books. But when clicking on save, the form for filling out the
contact data disappears but the contact is never shown. The server shows
these errors for that time stamp:

Apr 15 15:09:01 sogod [620575]: <0x0x560e14c461e0[SOGoCache]> an error
> occurred when caching value for key '/Users/user/Contacts/personal':
> "SERVER HAS FAILED AND IS\
>  DISABLED UNTIL TIMED RETRY"
> Apr 15 15:09:01 sogod [620575]: [ERROR] <0x0x560e14f21560[GCSFolder]>
>  could not open storage channel!
> Apr 15 15:09:01 sogod [620575]: 127.0.0.1 "POST
> /SOGo/so/user/Contacts/personal/view HTTP/1.1" 200 209/46 0.024 - - 0 - 13
> Apr 15 15:09:04 sogod [620575]: <0x0x560e14c461e0[SOGoCache]> an error
> occurred when caching value for key 'session:azs7xxx': "SERVER HAS
> FAILED AND IS DISABLE\
> D UNTIL TIMED RETRY"
> Apr 15 15:09:04 sogod [620575]: <0x0x560e14c461e0[SOGoCache]> an error
> occurred when caching value for key 'user+dn': "SERVER HAS FAILED AND IS
> DISABLED UNTIL TIMED \
> RETRY"
> Apr 15 15:09:04 sogod [620575]: <0x0x560e14c461e0[SOGoCache]> an error
> occurred when caching value for key 'user+attributes': "SERVER HAS FAILED
> AND IS DISABLED UNTI\
> L TIMED RETRY"
> Apr 15 15:09:04 sogod [620575]: <0x0x560e14c461e0[SOGoCache]> an error
> occurred when caching value for key 'user+attributes': "SERVER HAS FAILED
> AND IS DISABLED UNTI\
> L TIMED RETRY"
> Apr 15 15:09:04 sogod [620575]: <0x0x560e14c461e0[SOGoCache]> an error
> occurred when caching value for key 'u...@domain.de+attributes': "SERVER
> HAS FAILED\
>  AND IS DISABLED UNTIL TIMED RETRY"
> Apr 15 15:09:04 sogod [620575]: <0x0x560e14c461e0[SOGoCache]> an error
> occurred when caching value for key 'session:azs7xxx': "SERVER HAS
> FAILED AND IS DISABLE\
> D UNTIL TIMED RETRY"
> Apr 15 15:09:04 sogod [620575]: <0x0x560e14c461e0[SOGoCache]> an error
> occurred when caching value for key 'user+defaults': "SERVER HAS FAILED AND
> IS DISABLED UNTIL \
> TIMED RETRY"
> Apr 15 15:09:04 sogod [620575]: <0x0x560e14c461e0[SOGoCache]> an error
> occurred when caching value for key 'session:azs7xxx': "SERVER HAS
> FAILED AND IS DISABLE\
> D UNTIL TIMED RETRY"
> Apr 15 15:09:04 sogod [620575]: 127.0.0.1 "POST
> /SOGo/so/user/Contacts/users/view HTTP/1.1" 200 66/46 0.048 - - 0 - 13


This is the database config for sogo:

> SOGoProfileURL = "postgresql://
> sogo:password@127.0.0.1:5432/sogo/sogo_user_profile";
> OCSFolderInfoURL = "postgresql://
> sogo:password@127.0.0.1:5432/sogo/sogo_folder_info";
> OCSSessionsFolderURL = "postgresql://
> sogo:password@127.0.0.1:5432/sogo/sogo_sessions_folder";
> OCSEMailAlarmsFolderURL = "postgresql://
> sogo:password@127.0.0.1:5432/sogo/sogo_alarms_folder";


So what exactly is going wrong?


[SOGo] Migrating database backend

2024-04-07 Thread Richard
Hi,
I'd like to move the sogo database backend from mysql over to postgresql,
as sogo is the last application in our systems still using mysql and we
don't want to run two different database servers. Now in the past it was
recommended to use sogo-tool backup/sogo-tool restore for that job. Is this
still the current recommendation?

Also, what exactly is being copied over? We'd like to prevent any quirks to
be copied over that may have accumulated over the many years - we
originally started out with Sogo 2.x or something like that - that may not
cause issues now but could potentially cause some in the future.

Best,
Richard


[SOGo] Migrating database backend

2024-04-05 Thread Richard
Hi,
I'd like to move the sogo database backend from mysql over to postgresql,
as sogo is the last application in our systems still using mysql and we
don't want to run two different database servers. Now in the past it was
recommended to use sogo-tool backup/sogo-tool restore for that job. Is this
still the current recommendation?

Also, what exactly is being copied over? We'd like to prevent any quirks to
be copied over that may have accumulated over the many years - we
originally started out with Sogo 2.x or something like that - that may not
cause issues now but could potentially cause some in the future.

Best,
Richard


Re: [SOGo] SOGo no longer talking to mysql

2023-07-25 Thread Richard Rosner
Good news, I finally was able to get SOGo back up and running (and using 
/etc/sogo/sogo.conf, like any sane progarm would do).


But be honest people, who on earth should be able to have guessed that 
"~sogo/" refers to "/var/lib/sogo/"? I already thought I was crazy 
searching /usr for a .GNUstepDefaults, but this is actually peak 
insanity. ~ usually is read as /home/username. I think this needs to be 
clarified in the unmodified sogo.conf, or at least create a possibility 
to have sogo say where it actually reads the configuration from. I 
checked /var/lib/sogo/GNUstep/Defaults/ and can tell you SOGo did not 
read from .GNUstepDefaults as it basically didn't contain any config. It 
either read from .GNUstepDefaults.bck from 2013 or sogod.plist from 
2015. And it does not help in the slightest when sogo-tool reads from 
/etc/sogo/sogo.conf, while it's not even read by sogod.



Thanks anyways to all that came up with ways to find out what's going 
wrong with the setup. I'm still not really sure how strace would 
indicate that the mysql user in sogo.conf is being used when sogod 
clearly must have gotten its config from somewhere else, but that's 
something people can think about that know more about how sogo actually 
operates.


Richard

Am 25.07.2023 um 08:35 schrieb Markus Winkler (m...@irmawi.de):

Hi Richard,

On Mon, 24 Jul 2023 at 01:40:52PM +0200, Richard Rosner wrote:


My biggest problem with the old installation was (which was set up
before I became admin and I can't tell if it has been upgraded somehow
from SOGo 2.x, which we where using before 5.x, or if it was a fresh
install) that when I took over, the whole config was commented out and
everything was set to their default values. I have no idea how it even
worked in the first place, already because the default database is
postgresql, which isn't even installed on the system. And when I tried
to edit things like page title or availability of forwarding, they
simply didn't get applied. So I hoped with reinstalling I could solve
the issue. I even did an apt purge to remove everything from that old
installation (so only the mysql database survived), but obviously the
problem seems to be somewhere it did survive.


On Mon, 24 Jul 2023 at 03:27:49PM +0200, Richard Rosner wrote:


The old installation was SOGo (up until 5.8.0) on Debian 11 from the 
official Nightly Repo. I now switched to Debians own packages after 
upgrading to Debian 12, so it's still SOGo 5.8.0. But as the problem 
was present during the whole 5.x cycle (at least since we switched 
from 2.x, maybe in 2018 or so) and I switched to the Debian packages 
just now, it must be a problem independent of the package source. 



just another idea regarding this strange behaviour:


Within /usr/share/doc/sogo/README.Debian

"The SOGo debian package differs from upstream in placing the
configuration file in /etc/sogo/sogo.conf instead of using the GNUstep
user defaults that are placed under the home directory of the user
used to run SOGo. This file is parsed as GNUstep defaults in the
"sogod" domain, which means you must not specify the sogod domain in
the configuration file (there shouldn't be a "sogod = {" in
/etc/sogo/sogo.conf)."


Within a non-Debian sogo.conf there's this hint:

* ~sogo/GNUstep/Defaults/.GNUstepDefaults has precedence over this 
file, *
* make sure to move it away to avoid unwanted parameter 
overrides.   *



--> Maybe you still have a mixture of old Debian and non-Debian and/or 
2.x vs. 5.x configuration files somewhere? Could you have a look at 
/var/lib/sogo/GNUstep/Defaults/ if there are files which could provide 
SOGo defaults even if you delete /etc/sogo/sogo.conf. Or somewhere 
else, perhaps grepping for some relevant content shows a hit?



And just to be sure: in /etc/passwd is there an entry for the sogo 
user like this one?:


sogo:x:999:999:SOGo daemon:/var/lib/sogo:/usr/sbin/nologin

The home directory would be the interesting part.

Regards,
Markus



Re: [SOGo] SOGo no longer talking to mysql

2023-07-24 Thread Richard Rosner
It doesn't change. Now the big question is: what is it that sogo is 
loading? Because there's no other sogo.conf anywhere in the whole 
system, except of the expected files like /etc/default/sogo.


Richard Rosner

Studierendenschaft der RWTH Aachen University
Fachschaft Materialwissenschaft und Werkstofftechnik
Intzestraße 1
52072 Aachen
Tel.: +49 241 80-95781
rros...@fsmuw.rwth-aachen.de
www.fsmuw.rwth-aachen.de <https://www.fsmuw.rwth-aachen.de>
Am 21.07.2023 um 15:22 schrieb qhivert (qhiv...@alinto.eu):


Well, I’m out of idea ☹
Maybe test to change the username of SOGoProfileURL and look at the 
log to see if the name has changed as well, just to be sure the 
correct sogo.conf file is used. You could also send to my address only 
qhiv...@alinto.eu your sogo.conf file (censor your password) so I can 
see if anything shocks me.


*From:*users-requ...@sogo.nu  *On Behalf Of 
*Richard Rosner

*Sent:* vendredi 21 juillet 2023 13:27
*To:* qhivert (qhiv...@alinto.eu) 
*Subject:* Re: [SOGo] SOGo no longer talking to mysql

Hi Quentin,

thanks for this, but username is just sogo, password only consists of 
latin alphabet letters (no special letters like ê, ę or others), 
numbers and simple special characters like - or _, nothing that's not 
ASCII. Is there anything else that can/must be done? E.g. in mysql you 
have to denote usernames, passwords or host names in quotes. It's 
nothing sogo seems to need as it did work previously, but is there 
something similar I could try?


Richard

Am 21.07.2023 um 12:21 schrieb qhivert (qhiv...@alinto.eu):

Hello again Richard,

Just in case, in your sogo.conf the username and password must be
“url” encoded if you have any special characters ->
https://www.w3schools.com/tags/ref_urlencode.ASP

*From:*users-requ...@sogo.nu 
<mailto:users-requ...@sogo.nu> *On Behalf Of *Richard Rosner
*Sent:* vendredi 21 juillet 2023 09:44
*To:* Kenren Taisho (toushin.tai...@gmail.com) 
<mailto:users@sogo.nu>
*Subject:* Re: [SOGo] SOGo no longer talking to mysql

 Hi Kenren,

skip-name-resolve is alraedy commented out.

Richard

Am 21.07.2023 um 02:13 schrieb Kenren Taisho
(toushin.tai...@gmail.com):

Hi Richard,

ERROR: could not open MySQL4 connection to database
'sogo': Access denied for user 'sogo'@'localhost' (using
password: YES)

Could you check if skip-name-resolve is enabled in your MySQL
config? And if is, remove it, restart MySQL, and see if SOGo
is communicating again with MySQL.

Kind regards

On Fri, Jul 21, 2023 at 12:03 AM Richard Rosner
 wrote:

Hi Quentin,

I didn't only not change the password, I even made double
sure the user still had all permissions for the database
in question. And like I said, I did try username and
password manually, which did work.

I enabled MySQL4DebugEnabled, but outout doesn't seem to
have changed:

Jul 20 17:41:15 sogod [79585]:
<0x0x7f8a1a4b7340[WOWatchDogChild]> watchdog request
timeout set to 10 minutes
Jul 20 17:41:15 sogod [79585]:
<0x0x55ce03e91c70[WOWatchDog]> preparing 3 children
Jul 20 17:41:15 sogod [79585]:
<0x0x55ce03e91c70[WOWatchDog]> child spawned with pid
79586
Jul 20 17:41:15 sogod [79585]:
<0x0x55ce03e91c70[WOWatchDog]> child spawned with pid
79587
Jul 20 17:41:15 sogod [79585]:
<0x0x55ce03e91c70[WOWatchDog]> child spawned with pid
79588
2023-07-20 17:41:16.020 sogod[79588:79588] ERROR:
could not open MySQL4 connection to database 'sogo':
Access denied for user 'sogo'@'localhost' (using
password: YES)
Jul 20 17:41:16 sogod [79588]: [ERROR]
<0x0x55ce03f47520[GCSChannelManager]> could not open
channel  for
mysql://localhost/sogo/sogo_user_profile
Jul 20 17:41:16 sogod [79588]: [WARN]
<0x0x55ce03f47520[GCSChannelManager]> will prevent
opening of this channel 5 seconds after 2023-07-20
17:41:15 +0200
2023-07-20 17:41:16.026 sogod[79587:79587] ERROR:
could not open MySQL4 connection to database 'sogo':
Access denied for user 'sogo'@'localhost' (using
password: YES)
Jul 20 17:41:16 sogod [79587]: [ERROR]
<0x0x55ce03e5a8c0[GCSChannelManager]> could not open
channel  for
mysql://localhost/sogo/sogo_user_profile
Jul 20 17:41:16 sogod [79587]: [WARN]
<0x0x55ce03e5a8c0[

Re: [SOGo] SOGo no longer talking to mysql

2023-07-21 Thread Richard Rosner

Hi Quentin,

thanks for this, but username is just sogo, password only consists of 
latin alphabet letters (no special letters like ê, ę or others), numbers 
and simple special characters like - or _, nothing that's not ASCII. Is 
there anything else that can/must be done? E.g. in mysql you have to 
denote usernames, passwords or host names in quotes. It's nothing sogo 
seems to need as it did work previously, but is there something similar 
I could try?


Richard

Am 21.07.2023 um 12:21 schrieb qhivert (qhiv...@alinto.eu):


Hello again Richard,

Just in case, in your sogo.conf the username and password must be 
“url” encoded if you have any special characters -> 
https://www.w3schools.com/tags/ref_urlencode.ASP


*From:*users-requ...@sogo.nu  *On Behalf Of 
*Richard Rosner

*Sent:* vendredi 21 juillet 2023 09:44
*To:* Kenren Taisho (toushin.tai...@gmail.com) 
*Subject:* Re: [SOGo] SOGo no longer talking to mysql

 Hi Kenren,

skip-name-resolve is alraedy commented out.

Richard

Am 21.07.2023 um 02:13 schrieb Kenren Taisho (toushin.tai...@gmail.com):

Hi Richard,

ERROR: could not open MySQL4 connection to database 'sogo':
Access denied for user 'sogo'@'localhost' (using password: YES)

Could you check if skip-name-resolve is enabled in your MySQL
config? And if is, remove it, restart MySQL, and see if SOGo is
communicating again with MySQL.

Kind regards

On Fri, Jul 21, 2023 at 12:03 AM Richard Rosner  wrote:

Hi Quentin,

I didn't only not change the password, I even made double sure
the user still had all permissions for the database in
question. And like I said, I did try username and password
manually, which did work.

I enabled MySQL4DebugEnabled, but outout doesn't seem to have
changed:

Jul 20 17:41:15 sogod [79585]:
<0x0x7f8a1a4b7340[WOWatchDogChild]> watchdog request
timeout set to 10 minutes
Jul 20 17:41:15 sogod [79585]:
<0x0x55ce03e91c70[WOWatchDog]> preparing 3 children
Jul 20 17:41:15 sogod [79585]:
<0x0x55ce03e91c70[WOWatchDog]> child spawned with pid 79586
Jul 20 17:41:15 sogod [79585]:
<0x0x55ce03e91c70[WOWatchDog]> child spawned with pid 79587
Jul 20 17:41:15 sogod [79585]:
<0x0x55ce03e91c70[WOWatchDog]> child spawned with pid 79588
2023-07-20 17:41:16.020 sogod[79588:79588] ERROR: could
not open MySQL4 connection to database 'sogo': Access
denied for user 'sogo'@'localhost' (using password: YES)
Jul 20 17:41:16 sogod [79588]: [ERROR]
<0x0x55ce03f47520[GCSChannelManager]> could not open
channel  for
mysql://localhost/sogo/sogo_user_profile
Jul 20 17:41:16 sogod [79588]: [WARN]
<0x0x55ce03f47520[GCSChannelManager]>   will prevent
opening of this channel 5 seconds after 2023-07-20
17:41:15 +0200
2023-07-20 17:41:16.026 sogod[79587:79587] ERROR: could
not open MySQL4 connection to database 'sogo': Access
denied for user 'sogo'@'localhost' (using password: YES)
Jul 20 17:41:16 sogod [79587]: [ERROR]
<0x0x55ce03e5a8c0[GCSChannelManager]> could not open
channel  for
mysql://localhost/sogo/sogo_user_profile
Jul 20 17:41:16 sogod [79587]: [WARN]
<0x0x55ce03e5a8c0[GCSChannelManager]>   will prevent
opening of this channel 5 seconds after 2023-07-20
17:41:15 +0200
2023-07-20 17:41:16.034 sogod[79586:79586] ERROR: could
not open MySQL4 connection to database 'sogo': Access
denied for user 'sogo'@'localhost' (using password: YES)
Jul 20 17:41:16 sogod [79586]: [ERROR]
<0x0x55ce03e56270[GCSChannelManager]> could not open
channel  for
mysql://localhost/sogo/sogo_user_profile
Jul 20 17:41:16 sogod [79586]: [WARN]
<0x0x55ce03e56270[GCSChannelManager]>   will prevent
opening of this channel 5 seconds after 2023-07-20
17:41:15 +0200
Jul 20 17:41:16 sogod [79588]:
<0x0x55ce04083130[WOHttpAdaptor]> notified the watchdog
that we are ready
Jul 20 17:41:16 sogod [79587]:
<0x0x55ce040840a0[WOHttpAdaptor]> notified the watchdog
that we are ready
Jul 20 17:41:16 sogod [79586]:
<0x0x55ce04087de0[WOHttpAdaptor]> notified the watchdog
that we are ready

Richard

    Am 20.07.2023 um 17:08 schrieb qhivert (qhiv...@alinto.eu):

Hello Richard,
Strange indeed. I assume you didn’t change the sogo.conf
nor the password between?
Is this the log with t

Re: [SOGo] SOGo no longer talking to mysql

2023-07-21 Thread Richard Rosner

 Hi Kenren,

skip-name-resolve is alraedy commented out.

Richard

Am 21.07.2023 um 02:13 schrieb Kenren Taisho (toushin.tai...@gmail.com):

Hi Richard,

ERROR: could not open MySQL4 connection to database 'sogo': Access
denied for user 'sogo'@'localhost' (using password: YES)


Could you check if skip-name-resolve is enabled in your MySQL config? 
And if is, remove it, restart MySQL, and see if SOGo is communicating 
again with MySQL.


Kind regards



On Fri, Jul 21, 2023 at 12:03 AM Richard Rosner  wrote:

Hi Quentin,

I didn't only not change the password, I even made double sure the
user still had all permissions for the database in question. And
like I said, I did try username and password manually, which did work.

I enabled MySQL4DebugEnabled, but outout doesn't seem to have changed:


Jul 20 17:41:15 sogod [79585]:
<0x0x7f8a1a4b7340[WOWatchDogChild]> watchdog request timeout
set to 10 minutes
Jul 20 17:41:15 sogod [79585]: <0x0x55ce03e91c70[WOWatchDog]>
preparing 3 children
Jul 20 17:41:15 sogod [79585]: <0x0x55ce03e91c70[WOWatchDog]>
child spawned with pid 79586
Jul 20 17:41:15 sogod [79585]: <0x0x55ce03e91c70[WOWatchDog]>
child spawned with pid 79587
Jul 20 17:41:15 sogod [79585]: <0x0x55ce03e91c70[WOWatchDog]>
child spawned with pid 79588
2023-07-20 17:41:16.020 sogod[79588:79588] ERROR: could not
open MySQL4 connection to database 'sogo': Access denied for
user 'sogo'@'localhost' (using password: YES)
Jul 20 17:41:16 sogod [79588]: [ERROR]
<0x0x55ce03f47520[GCSChannelManager]> could not open channel
 for
mysql://localhost/sogo/sogo_user_profile
Jul 20 17:41:16 sogod [79588]: [WARN]
<0x0x55ce03f47520[GCSChannelManager]>   will prevent opening
of this channel 5 seconds after 2023-07-20 17:41:15 +0200
2023-07-20 17:41:16.026 sogod[79587:79587] ERROR: could not
open MySQL4 connection to database 'sogo': Access denied for
user 'sogo'@'localhost' (using password: YES)
Jul 20 17:41:16 sogod [79587]: [ERROR]
<0x0x55ce03e5a8c0[GCSChannelManager]> could not open channel
 for
mysql://localhost/sogo/sogo_user_profile
Jul 20 17:41:16 sogod [79587]: [WARN]
<0x0x55ce03e5a8c0[GCSChannelManager]>   will prevent opening
of this channel 5 seconds after 2023-07-20 17:41:15 +0200
2023-07-20 17:41:16.034 sogod[79586:79586] ERROR: could not
open MySQL4 connection to database 'sogo': Access denied for
user 'sogo'@'localhost' (using password: YES)
Jul 20 17:41:16 sogod [79586]: [ERROR]
<0x0x55ce03e56270[GCSChannelManager]> could not open channel
 for
mysql://localhost/sogo/sogo_user_profile
Jul 20 17:41:16 sogod [79586]: [WARN]
<0x0x55ce03e56270[GCSChannelManager]>   will prevent opening
of this channel 5 seconds after 2023-07-20 17:41:15 +0200
Jul 20 17:41:16 sogod [79588]:
<0x0x55ce04083130[WOHttpAdaptor]> notified the watchdog that
we are ready
Jul 20 17:41:16 sogod [79587]:
<0x0x55ce040840a0[WOHttpAdaptor]> notified the watchdog that
we are ready
Jul 20 17:41:16 sogod [79586]:
<0x0x55ce04087de0[WOHttpAdaptor]> notified the watchdog that
we are ready


Richard


Am 20.07.2023 um 17:08 schrieb qhivert (qhiv...@alinto.eu):


Hello Richard,
Strange indeed. I assume you didn’t change the sogo.conf nor the
password between?
Is this the log with the param *MySQL4DebugEnabled = YES* in your
sogo.conf? If not could you add it and show us the logs?

Regards,
Quentin

*From:*users-requ...@sogo.nu 
<mailto:users-requ...@sogo.nu> *On Behalf Of *Richard Rosner
*Sent:* jeudi 20 juillet 2023 16:23
*To:* users@sogo.nu
*Subject:* [SOGo] SOGo no longer talking to mysql

Hi,

I had to reinstall SOGo because for some strange reason it just
refused to accept any changes to the config. Now for some reason
it can't connect to mysql anymore. In the sogo.conf I have e.g.
>> SOGoProfileURL =
"mysql://sogo:/password/@127.0.0.1:3306/sogo/sogo_user_profile
<http://127.0.0.1:3306/sogo/sogo_user_profile>"; << and I have
verified that mariadb is actually listening to 127.0.0.1:3306
<http://127.0.0.1:3306>. But when I restart SOGo to activate the
config, I get

Jul 20 15:53:10 sogod [73521]:
<0x0x7fb00f4b7340[WOWatchDogChild]> watchdog request timeout
set to 10 minutes
Jul 20 15:53:10 sogod [73521]: <0x0x55bdab397b90[WOWatchDog]>
preparing 3 children
Jul 20 15:53:10 sogod [73521]: <0x0x55bdab397b90[WOWatchDog]>
child spawned with pid 

Re: [SOGo] SOGo no longer talking to mysql

2023-07-20 Thread Richard Rosner

Hi Quentin,

I didn't only not change the password, I even made double sure the user 
still had all permissions for the database in question. And like I said, 
I did try username and password manually, which did work.


I enabled MySQL4DebugEnabled, but outout doesn't seem to have changed:


   Jul 20 17:41:15 sogod [79585]: <0x0x7f8a1a4b7340[WOWatchDogChild]>
   watchdog request timeout set to 10 minutes
   Jul 20 17:41:15 sogod [79585]: <0x0x55ce03e91c70[WOWatchDog]>
   preparing 3 children
   Jul 20 17:41:15 sogod [79585]: <0x0x55ce03e91c70[WOWatchDog]> child
   spawned with pid 79586
   Jul 20 17:41:15 sogod [79585]: <0x0x55ce03e91c70[WOWatchDog]> child
   spawned with pid 79587
   Jul 20 17:41:15 sogod [79585]: <0x0x55ce03e91c70[WOWatchDog]> child
   spawned with pid 79588
   2023-07-20 17:41:16.020 sogod[79588:79588] ERROR: could not open
   MySQL4 connection to database 'sogo': Access denied for user
   'sogo'@'localhost' (using password: YES)
   Jul 20 17:41:16 sogod [79588]: [ERROR]
   <0x0x55ce03f47520[GCSChannelManager]> could not open channel
for
   mysql://localhost/sogo/sogo_user_profile
   Jul 20 17:41:16 sogod [79588]: [WARN]
   <0x0x55ce03f47520[GCSChannelManager]>   will prevent opening of this
   channel 5 seconds after 2023-07-20 17:41:15 +0200
   2023-07-20 17:41:16.026 sogod[79587:79587] ERROR: could not open
   MySQL4 connection to database 'sogo': Access denied for user
   'sogo'@'localhost' (using password: YES)
   Jul 20 17:41:16 sogod [79587]: [ERROR]
   <0x0x55ce03e5a8c0[GCSChannelManager]> could not open channel
for
   mysql://localhost/sogo/sogo_user_profile
   Jul 20 17:41:16 sogod [79587]: [WARN]
   <0x0x55ce03e5a8c0[GCSChannelManager]>   will prevent opening of this
   channel 5 seconds after 2023-07-20 17:41:15 +0200
   2023-07-20 17:41:16.034 sogod[79586:79586] ERROR: could not open
   MySQL4 connection to database 'sogo': Access denied for user
   'sogo'@'localhost' (using password: YES)
   Jul 20 17:41:16 sogod [79586]: [ERROR]
   <0x0x55ce03e56270[GCSChannelManager]> could not open channel
for
   mysql://localhost/sogo/sogo_user_profile
   Jul 20 17:41:16 sogod [79586]: [WARN]
   <0x0x55ce03e56270[GCSChannelManager]>   will prevent opening of this
   channel 5 seconds after 2023-07-20 17:41:15 +0200
   Jul 20 17:41:16 sogod [79588]: <0x0x55ce04083130[WOHttpAdaptor]>
   notified the watchdog that we are ready
   Jul 20 17:41:16 sogod [79587]: <0x0x55ce040840a0[WOHttpAdaptor]>
   notified the watchdog that we are ready
   Jul 20 17:41:16 sogod [79586]: <0x0x55ce04087de0[WOHttpAdaptor]>
   notified the watchdog that we are ready


Richard


Am 20.07.2023 um 17:08 schrieb qhivert (qhiv...@alinto.eu):


Hello Richard,
Strange indeed. I assume you didn’t change the sogo.conf nor the 
password between?
Is this the log with the param *MySQL4DebugEnabled = YES* in your 
sogo.conf? If not could you add it and show us the logs?


Regards,
Quentin

*From:*users-requ...@sogo.nu  *On Behalf Of 
*Richard Rosner

*Sent:* jeudi 20 juillet 2023 16:23
*To:* users@sogo.nu
*Subject:* [SOGo] SOGo no longer talking to mysql

Hi,

I had to reinstall SOGo because for some strange reason it just 
refused to accept any changes to the config. Now for some reason it 
can't connect to mysql anymore. In the sogo.conf I have e.g. >> 
SOGoProfileURL = 
"mysql://sogo:/password/@127.0.0.1:3306/sogo/sogo_user_profile"; << 
and I have verified that mariadb is actually listening to 
127.0.0.1:3306. But when I restart SOGo to activate the config, I get


Jul 20 15:53:10 sogod [73521]: <0x0x7fb00f4b7340[WOWatchDogChild]>
watchdog request timeout set to 10 minutes
Jul 20 15:53:10 sogod [73521]: <0x0x55bdab397b90[WOWatchDog]>
preparing 3 children
Jul 20 15:53:10 sogod [73521]: <0x0x55bdab397b90[WOWatchDog]>
child spawned with pid 73522
Jul 20 15:53:10 sogod [73521]: <0x0x55bdab397b90[WOWatchDog]>
child spawned with pid 73523
Jul 20 15:53:10 sogod [73521]: <0x0x55bdab397b90[WOWatchDog]>
child spawned with pid 73524
2023-07-20 15:53:10.948 sogod[73523:73523] ERROR: could not open
MySQL4 connection to database 'sogo': Access denied for user
'sogo'@'localhost' (using password: YES)
Jul 20 15:53:10 sogod [73523]: [ERROR]
<0x0x55bdab3912c0[GCSChannelManager]> could not open channel
 for
mysql://localhost/sogo/sogo_user_profile
Jul 20 15:53:10 sogod [73523]: [WARN]
<0x0x55bdab3912c0[GCSChannelManager]>   will prevent opening of
this channel 5 seconds after 2023-07-20 15:53:10 +0200
2023-07-20 15:53:10.948 sogod[73524:73524] ERROR: could not open
MySQL4 connection to database 'sogo': Access denied for user
'sogo'@'localhost' (using password: YES)
2023-07-20 15:53:10.948 sogod[73522:73522] ERROR: could not open
MySQL4 connection to database 'sogo': Access den

[SOGo] SOGo no longer talking to mysql

2023-07-20 Thread Richard Rosner

Hi,

I had to reinstall SOGo because for some strange reason it just refused 
to accept any changes to the config. Now for some reason it can't 
connect to mysql anymore. In the sogo.conf I have e.g. >> SOGoProfileURL 
= "mysql://sogo:/password/@127.0.0.1:3306/sogo/sogo_user_profile"; << 
and I have verified that mariadb is actually listening to 
127.0.0.1:3306. But when I restart SOGo to activate the config, I get



   Jul 20 15:53:10 sogod [73521]: <0x0x7fb00f4b7340[WOWatchDogChild]>
   watchdog request timeout set to 10 minutes
   Jul 20 15:53:10 sogod [73521]: <0x0x55bdab397b90[WOWatchDog]>
   preparing 3 children
   Jul 20 15:53:10 sogod [73521]: <0x0x55bdab397b90[WOWatchDog]> child
   spawned with pid 73522
   Jul 20 15:53:10 sogod [73521]: <0x0x55bdab397b90[WOWatchDog]> child
   spawned with pid 73523
   Jul 20 15:53:10 sogod [73521]: <0x0x55bdab397b90[WOWatchDog]> child
   spawned with pid 73524
   2023-07-20 15:53:10.948 sogod[73523:73523] ERROR: could not open
   MySQL4 connection to database 'sogo': Access denied for user
   'sogo'@'localhost' (using password: YES)
   Jul 20 15:53:10 sogod [73523]: [ERROR]
   <0x0x55bdab3912c0[GCSChannelManager]> could not open channel
for
   mysql://localhost/sogo/sogo_user_profile
   Jul 20 15:53:10 sogod [73523]: [WARN]
   <0x0x55bdab3912c0[GCSChannelManager]>   will prevent opening of this
   channel 5 seconds after 2023-07-20 15:53:10 +0200
   2023-07-20 15:53:10.948 sogod[73524:73524] ERROR: could not open
   MySQL4 connection to database 'sogo': Access denied for user
   'sogo'@'localhost' (using password: YES)
   2023-07-20 15:53:10.948 sogod[73522:73522] ERROR: could not open
   MySQL4 connection to database 'sogo': Access denied for user
   'sogo'@'localhost' (using password: YES)
   Jul 20 15:53:10 sogod [73522]: [ERROR]
   <0x0x55bdab390df0[GCSChannelManager]> could not open channel
for
   mysql://localhost/sogo/sogo_user_profile
   Jul 20 15:53:10 sogod [73524]: [ERROR]
   <0x0x55bdab373020[GCSChannelManager]> could not open channel
for
   mysql://localhost/sogo/sogo_user_profile
   Jul 20 15:53:10 sogod [73522]: [WARN]
   <0x0x55bdab390df0[GCSChannelManager]>   will prevent opening of this
   channel 5 seconds after 2023-07-20 15:53:10 +0200
   Jul 20 15:53:10 sogod [73524]: [WARN]
   <0x0x55bdab373020[GCSChannelManager]>   will prevent opening of this
   channel 5 seconds after 2023-07-20 15:53:10 +0200
   Jul 20 15:53:11 sogod [73522]: <0x0x55bdab1b0510[WOHttpAdaptor]>
   notified the watchdog that we are ready
   Jul 20 15:53:11 sogod [73523]: <0x0x55bdab589fc0[WOHttpAdaptor]>
   notified the watchdog that we are ready
   Jul 20 15:53:11 sogod [73524]: <0x0x55bdab589050[WOHttpAdaptor]>
   notified the watchdog that we are ready

So of course I tried logging in manually to mysql, but this succedes 
without any complaints. Now what's the problem with it? I'm using 
mariadb-server 10.11.3.


smime.p7s
Description: S/MIME Cryptographic Signature


Re: [SOGo] Broken Calendar in SOGo 5.8

2022-12-12 Thread Richard Rosner

Hi Sebastien,

I have never been able to create bug reports there. When I'm logged in, 
there's a flag next to my user name saying "viewer", which is probably 
the reason for that. I don't know how to change that and last time I 
tried to contact the admin mail address it didn't work (I think I got 
the response that it's not available).



Best

Richard

Am 12.12.2022 um 09:25 schrieb smizr...@alinto.eu (smizr...@alinto.eu):

Hi Richard,

You can open a ticket on bugs.sogo.nu and provide the following 
informations :
The SQL request just before getting the SQL Exception. You can have 
SQL request in logs using MySQL4DebugEnabled = YES; in sogo.conf.
The SQL dump structure of your database (without data) would be also 
helpful.


Sebastien

Le Jeudi, Décembre 08, 2022 15:27 CET, "\"Richard Rosner\"" 
(rros...@fsmuw.rwth-aachen.de)  a écrit:

Hello,
it seems SOGo 5.8 has broken the calendar (interestingly only for 
some users), seemingly with a database update. At least some users 
aren't able to create new entries and the log shows errors with


Dec 08 15:03:29 sogod [2803825]: <0x0x5617477a0510[GCSFolder]>
ERROR(-[GCSFolder
writeContent:fromComponent:container:toName:baseVersion:]): cannot\
insert content : 
NAME:ExecutionFailed REASON:Unknown column 'c_description' in
'field list'

and older reports in mailing lists suggest the last time that was a 
problem back in 2.x it was a problem with the databse scheme. Yet 
there is no database update script in /usr/share/doc/sogo/, the 
newest one is sql-update-5.5.1_to_5.6.0.sh. But that one was for the 
bug of not being able to log in back then. So how do I fix it?

​​
Best regards
Richard




smime.p7s
Description: S/MIME Cryptographic Signature


[SOGo] Broken Calendar in SOGo 5.8

2022-12-08 Thread &quot;Richard Rosner"

Hello,
it seems SOGo 5.8 has broken the calendar (interestingly only for some users), 
seemingly with a database update. At least some users aren't able to create new 
entries and the log shows errors withDec 08 15:03:29 sogod [2803825]: 
<0x0x5617477a0510[GCSFolder]> ERROR(-[GCSFolder 
writeContent:fromComponent:container:toName:baseVersion:]): cannot\
insert content :  NAME:ExecutionFailed 
REASON:Unknown column 'c_description' in 'field list'and older reports in 
mailing lists suggest the last time that was a problem back in 2.x it was a 
problem with the databse scheme. Yet there is no database update script in 
/usr/share/doc/sogo/, the newest one is sql-update-5.5.1_to_5.6.0.sh. But that 
one was for the bug of not being able to log in back then. So how do I fix it?
​​
Best regards
Richard


smime.p7s
Description: S/MIME cryptographic signature


Re: [SOGo] Bug in character display in S/MIME encrypted mails

2022-09-16 Thread &quot;Richard Rosner"

With OpenSSL 3.x I get

Error decrypting CMS structure
400755B1327F:error:1C800064:Provider routines:ossl_cipher_unpadblock:bad 
decrypt:../providers/implementations/ciphers/ciphercommon_block.c:129:
If I swap cms for smime it changes to

Error decrypting PKCS#7 structure
rest of the error stays the same. For all I know it has to do with some kinde 
of deprecated stuff in OpenSSL 3.x so you'd need to add something to the comand 
to enable legacy stuff.

Using OpenSSL 1.1.1n however doesn't change much:
Error decrypting CMS structure
139958493545792:error:06065064:digital envelope 
routines:EVP_DecryptFinal_ex:bad decrypt:../crypto/evp/evp_enc.c:610:
The private key file is a PEM RSA key. Already checked that the reason can't be 
the wrong kind of line breaks (those Windows line breaks) inside the key file, 
since that was mentioned to be a possible reason. But the key file is as it's 
supposed to be.

Regards
Richard
-- 
Richard Rosner
Beauftragter für Vernetzung

Studierendenschaft der RWTH Aachen University
Fachschaft Materialwissenschaft und Werkstofftechnik
Intzestraße 1
52072 Aachen
Tel.: +49 241 80-95781
rros...@fsmuw.rwth-aachen.de
www.fsmuw.rwth-aachen.de

Am Freitag, 16. September 2022 19:51 CEST, schrieb "\"Frank Schmirler\"" 
(s...@schmirler.de) :
 Hi Richard,

the basic openssl command to decrypt an S/MIME message would be something like

openssl cms -decrypt -in EMLFILE -inkey PRIVATEKEYFILE

Which error do you get when trying to decrypt your message with openssl?

Regards,
Frank

Am Mittwoch, 14. September 2022 14:24 CEST, schrieb "\"Richard Rosner\"" 
(rros...@fsmuw.rwth-aachen.de) :
> Hello together,
> it seems I've found a bug when displaying an S/MIME encrypted mail. It seems 
> like characters aren't interpreted as UTF-8. At least some german "Umlaute" 
> don't display correctly. In Thunderbird, on the other hand, that same mail is 
> displayed correctly. Sadly, I haven't found a way to view the unencrypted 
> mail source code to verify if the text is indicated as UTF-8. Both OpenSSL 
> 1.x and 3.x are just throwing errors when trying to decrypt the eml file and 
> I don't know of any method to use either Thunderbird or SOGo to save the mail 
> as an unecrypted eml file. If anybody knows how I could better help to find 
> the bug, let me know.
>
> Using SOGo 5.7.1.20220912-1 on 64-bit Debian 10, straight from the 
> packages.sogo.nu repo.
>
> Best Regards
> Richard
> -- 
> Richard Rosner
 


smime.p7s
Description: S/MIME cryptographic signature


[SOGo] Bug in character display in S/MIME encrypted mails

2022-09-14 Thread &quot;Richard Rosner"

Hello together,
it seems I've found a bug when displaying an S/MIME encrypted mail. It seems 
like characters aren't interpreted as UTF-8. At least some german "Umlaute" 
don't display correctly. In Thunderbird, on the other hand, that same mail is 
displayed correctly. Sadly, I haven't found a way to view the unencrypted mail 
source code to verify if the text is indicated as UTF-8. Both OpenSSL 1.x and 
3.x are just throwing errors when trying to decrypt the eml file and I don't 
know of any method to use either Thunderbird or SOGo to save the mail as an 
unecrypted eml file. If anybody knows how I could better help to find the bug, 
let me know.

Using SOGo 5.7.1.20220912-1 on 64-bit Debian 10, straight from the 
packages.sogo.nu repo.

Best Regards
Richard
-- 
Richard Rosner


smime.p7s
Description: S/MIME cryptographic signature


[SOGo] Setting Up a Calendar in SOGo

2015-06-29 Thread Richard Doc Kinne
Hey Folks:

I have been working at trying to set up a SOGo service on an Ubuntu server
using mysql as an authentication method for some time now. It has been very
slow going.

I have managed (with some great help from this list) to get mail working
via the web interface. There was some documentation on that. What I've not
found is any reasonable documentation when it came to setting up calendars.
Can any one point me to something?

I suspect, just like setting up various tables for the mail in mySQL, I
have to do something similar for the calendar, but I've not been able to
pin down the specifics.
-- 
Richard Doc Kinne, [KQR]
Astronomical Technologist
American Association of Variable Star Observers
-
Please support the AAVSO and its mission --
Join or donate today: http://www.aavso.org/apps/donate
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Re: Calendar events not showing up

2015-06-16 Thread Richard Doc Kinne
,a.c_enddate
 
 
 FROM sogostefan00102393d4c_quick a, sogostefan00102393d4c b WHERE
  ((c_component = 'vevent') AND ((c_startdate IS NULL) OR
  (c_startdate = 1436137199)) AND ((c_cycleenddate IS NULL) OR
  (c_cycleenddate = 1433113200)) AND (c_iscycle = 1)) AND a.c_name =
  b.c_name AND (c_deleted != 1 OR c_deleted IS NULL)':
  MySQL4Exception: 0x7f7dc0e415a0 NAME:ExecutionFailed
  REASON:Unknown column 'a.c_description' in 'field list' Jun 16
  17:20:32 sogod [6172]: [ERROR]
  0xC0CBBAD0[SOGoAppointmentFolder]:7821-54296100-3-53063600
  (-[SOGoAppointmentFolder
 
 fetchFields:from:to:title:component:additionalFilters:includeProtectedInformation:]):
 
 
 fetch failed!
  Jun 16 17:20:32 sogod [6172]: 137.222.92.18 POST
 
 /SOGo/so/stefan/Calendar/eventsblocks?sd=20150601ed=20150705view=monthview
 
 
 HTTP/1.1 200 288/0 0.012 - - 0
 
  Any idea how to fix this?
 
  Thanks in advance, Stefan
 
 --
 users@sogo.nu
 https://inverse.ca/sogo/lists




-- 
Richard Doc Kinne, [KQR]
Astronomical Technologist
American Association of Variable Star Observers
-
Please support the AAVSO and its mission --
Join or donate today: http://www.aavso.org/apps/donate
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

[SOGo] Calendar Entries Not Showing Up on Calendar

2015-06-09 Thread Richard Doc Kinne
Hi Folks:

I'm working on setting up a SOGo server. Originally I had problems with
email. Many thanks to Christian Mack for putting me on the right path. Now,
amazingly, through the web interface, I have mail working.

Now I'm working on the calendar, which somehow, is proving more
problematic.

Up to this time we've been using a small CalDAV server with iCal, so in
this setup, I'm basically trying to start from scratch (which I thought
would be easier than trying to interface with a running email system).

I am able to log into SOGo from the web and bring up the calendar
interface. There is nothing on it since this is a blank slate. I have my
own calendar. I punch up New Event and fill everything out. I push save
and exit and it certainly exits, but nothing comes out on the calendar.

When going to the calendar the sogo.log file seems to just explode, so I'm
not sure where to start looking. The configuration documentation I have
doesn't seem to mention much about the calendar that I can see save using
it as a login module and simply describing what its privilages are:

SOGoLoginModule = Calendar;

  SOGoCalendarDefaultRoles = (
PublicDAndTViewer,
ConfidentialDAndTViewer
  );

I'm not quite sure where to start looking, and I don't want to spam the
list with large log files.

Any pointers?  Thanks so much!

-- 
Richard Doc Kinne, [KQR]
Astronomical Technologist
American Association of Variable Star Observers
-
Please support the AAVSO and its mission --
Join or donate today: http://www.aavso.org/apps/donate
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

[SOGo] Ubuntu Sogo Mysql Authentication Setup Problem.

2015-05-29 Thread Richard Doc Kinne
Hi Folks:

I am trying to set up Sogo on an Ubuntu 14.04 server using mysql as the
authenticator.

I have gotten to a point where the website interface is working, but no one
can log in. The interface says “Wrong username or password.” I’m not sure
what I’m missing.

The log says: May 29 19:27:20 sogod [25088]: [ERROR]
0x0x7fd85fdd05a8[SOGoUserManager] No authentication sources defined -
nobody will be able to login. Check your defaults.

It does seem to be connecting to the database, as far as I can tell. The
tables seem to be there.

I’m missing something basic, but after several days I can’t figure out
what. Any thoughts?

Thanks so much!
—
Doc Kinne
American Assoc. of Variable Star Observers


My sogo.conf is here:
{
   /* Database configuration (mysql:// or postgresql://) */
  SOGoProfileURL = mysql://sogo:password@localhost
:3306/sogo/sogo_user_profile;
  OCSFolderInfoURL = mysql://sogo:password@localhost
:3306/sogo/sogo_folder_info;
  OCSSessionsFolderURL = mysql://sogo:password@localhost
:3306/sogo/sogo_sessions_folder;

  /* Mail */
  SOGoDraftsFolderName = Drafts;
  SOGoSentFolderName = Sent;
  SOGoTrashFolderName = Trash;
  SOGoIMAPServer = localhost;
  SOGoSieveServer = sieve://127.0.0.1:4190;
  SOGoSMTPServer = 127.0.0.1;
  SOGoMailDomain = aavso.org;
  SOGoMailingMechanism = smtp;
  SOGoForceExternalLoginWithEmail = NO;
  SOGoMailSpoolPath = /var/spool/sogo;
  SOGoMailMessageCheck = every_5_minutes;
  NGImap4ConnectionStringSeparator = /;

  /* Notifications */
  SOGoAppointmentSendEMailNotifications = YES;
  SOGoACLsSendEMailNotifications = YES;
  SOGoFoldersSendEMailNotifications = YES;

  /* Authentication */
  SOGoPasswordChangeEnabled = YES;

  /* LDAP authentication example */
  //SOGoUserSources = (
  //  {
  type = sql;
  userPasswordAlgorithm = md5;
  viewURL = mysql://sogo:SOGOSaveUs!@50.198.80.204:3306/sogo/sogo_users
;
  //CNFieldName = cn;
  //UIDFieldName = uid;
  //IDFieldName = uid; // first field of the DN for direct binds
  //bindFields = (uid, mail); // array of fields to use for indirect
binds
  //baseDN = ou=users,dc=acme,dc=com;
  //bindDN = uid=sogo,ou=users,dc=acme,dc=com;
  //bindPassword = qwerty;
  canAuthenticate = YES;
  displayName = SOGo Users;
  //hostname = ldap://127.0.0.1:389;
  id = users;
  isAddressBook = YES;
  //  }
  //);



  /* SQL authentication example */
  /*  These database columns MUST be present in the view/table:
   *c_uid - will be used for authentication -  it's the username or
usern...@domain.tld)
   *c_name - which can be identical to c_uid -  will be used to
uniquely identify entries
   *c_password - password of the user, plain-text, md5 or sha encoded
for now
   *c_cn - the user's common name - such as John Doe
   *mail - the user's mail address
   *  See the installation guide for more details
   */
  //SOGoUserSources =
  //  (
  //{
  //  type = sql;
  //  id = directory;
  //  viewURL = mysql://sogo:sogo@127.0.0.1:5432/sogo/sogo_view;
  //  canAuthenticate = YES;
  //  isAddressBook = YES;
  //  userPasswordAlgorithm = md5;
  //}
  //  );

  /* Web Interface */
  SOGoPageTitle = SOGo;
  SOGoVacationEnabled = YES;
  SOGoForwardEnabled = YES;
  //SOGoSieveScriptsEnabled = YES;
  //SOGoMailAuxiliaryUserAccountsEnabled = YES;
  //SOGoTrustProxyAuthentication = NO;

  /* General */
  WOWorkersCount = 3;
  SOGoTrustProxyAuthentication = YES;
  SOGoLanguage = English;
  SOGoTimeZone = America/Montreal;
  SOGoCalendarDefaultRoles = (
PublicDAndTViewer,
ConfidentialDAndTViewer
  );
  SOGoSuperUsernames = (sogo, sogo1, sogo2, admin); // This is an array -
keep the parens!
  SxVMemLimit = 384;
  WOPidFile = /var/run/sogo/sogo.pid;
  SOGoMemcachedHost = /var/run/memcached.sock;

  /* Debug */
  SOGoDebugRequests = YES;
  SoDebugBaseURL = YES;
  ImapDebugEnabled = YES;
  LDAPDebugEnabled = YES;
  PGDebugEnabled = YES;
  MySQL4DebugEnabled = YES;
  SOGoUIxDebugEnabled = YES;
  //WODontZipResponse = YES;
  WOLogFile = /var/log/sogo/sogo.log;
}


My mysql tables are here:

+--+
| Tables_in_sogo   |
+--+
| sogo_folder_info |
| sogo_sessions_folder |
| sogo_user_profile|
| sogo_users   |
+--+
4 rows in set (0.00 sec)

mysql describe sogo_folder_info;
+--+-+--+-+-++
| Field| Type| Null | Key | Default |
Extra  |
+--+-+--+-+-++
| c_folder_id  | bigint(20) unsigned | NO   | UNI | NULL|
auto_increment |
| c_path   | varchar(255)| NO   | PRI | NULL
||
| c_path1  | varchar(255)| NO   | | NULL
||
| c_path2  | varchar(255)| YES  | | NULL
||
| c_path3  | varchar(255)| 

Re: [SOGo] SOGo and CAS

2015-01-28 Thread Bruno Richard

thanks Jean-Philippe for your answer.
I tried but the browser always said that the page is not correctly 
redirected...


ans I always had the same message in the cas log :
 Response Code did not match any of the acceptable response codes. Code 
returned was 403

and bad credentials...

any clue ?
thanks in advance
Bruno

On 26/01/2015 09:35, Jean-Philippe Ghibaudo wrote:

Hi,

I guess you just need to request the REMOTE_USER header.
Where you have all your RequestHeader set, try add :

RequestHeader set x-webobjects-remote-user %{REMOTE_USER}e

Jean-Philippe

Le 21/01/2015 14:18, Bruno Richard a écrit :

Hi All,

I'm new to SOGo. I try to install it on debian jessie.
I want to authenticate users using CAS.
I had inserted in the cas keystore the cert of the apache that is in 
front of SOGo.
However, I have a cas error when I try to log in and the mailbox 
appears empty.


The cas error :
2015-01-21 10:49:25,735 DEBUG 
[org.jasig.cas.ticket.registry.DefaultTicketRegistry] - Ticket 
[TGT-1-bmLPtKJbhpV5hDBdjhKsrESdgsbxSu002oIQVDmBoSITqwnJbf-cas.mydomain.fr] 
found in registry.
2015-01-21 10:49:25,742 DEBUG 
[org.jasig.cas.web.flow.CasFlowExecutionKeyFactory] - Removing flow 
execution '[Ended execution of 'login']' from repository
2015-01-21 10:49:25,742 DEBUG 
[org.jasig.cas.web.flow.CasFlowExecutionKeyFactory] - Removing flow 
execution '[Ended execution of 'login']' from repository
2015-01-21 10:49:25,959 DEBUG 
[org.jasig.cas.web.support.CasArgumentExtractor] - Extractor 
generated service for: https://webmail.mydomain.fr/SOGo/so/index
2015-01-21 10:49:25,962 DEBUG 
[org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler] 
- Attempting to resolve credentials for [callbackUrl: 
https://webmail.mydomain.fr/SOGo/casProxy]
2015-01-21 10:49:26,261 DEBUG [org.jasig.cas.util.HttpClient] - 
Response Code did not match any of the acceptable response codes. 
Code returned was 403
2015-01-21 10:49:26,262 INFO 
[org.jasig.cas.authentication.AuthenticationManagerImpl] - 
AuthenticationHandler: 
org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler 
failed to authenticate the user which provided the following 
credentials: [callbackUrl: https://webmail.mydomain.fr/SOGo/casProxy]
2015-01-21 10:49:26,263 DEBUG 
[org.jasig.cas.ticket.registry.DefaultTicketRegistry] - Attempting to 
retrieve ticket [ST-1-hyppJtF9qvogghaPr9Yg-cas.mydomain.fr]
2015-01-21 10:49:26,263 DEBUG 
[org.jasig.cas.ticket.registry.DefaultTicketRegistry] - Ticket 
[ST-1-hyppJtF9qvogjhaZr9Yg-cas.mydomain.fr] found in registry.
2015-01-21 10:49:26,264 ERROR 
[org.jasig.cas.web.ServiceValidateController] - TicketException 
generating ticket for: [callbackUrl: 
https://webmail.mydomain.fr/SOGo/casProxy]
org.jasig.cas.ticket.TicketCreationException: 
error.authentication.credentials.bad
at 
org.jasig.cas.CentralAuthenticationServiceImpl.delegateTicketGrantingTicket_aroundBody6(CentralAuthenticationServiceImpl.java:300)
at 
org.jasig.cas.CentralAuthenticationServiceImpl.delegateTicketGrantingTicket_aroundBody7$advice(CentralAuthenticationServiceImpl.java:44)
at 
org.jasig.cas.CentralAuthenticationServiceImpl.delegateTicketGrantingTicket(CentralAuthenticationServiceImpl.java:1)

[...]

Please help ! what can I do or test ?
thanks in advance
Bruno

Some points of my configuration :
/etc/sogo/sogo.conf
[...]
  SOGoAuthenticationType = cas;
  SOGoCASServiceURL = https://cas.mydomain.fr/cas;;
  WOWorkersCount = 10;
[...]

/etc/apache/conf-enabled/SOGo.conf
[...]
ProxyPass /SOGo/casProxy http://localhost/cgi-bin/cas-proxy-validate.py
Proxy http://localhost/cgi-bin/cas-proxy-validate.py
  Order deny,allow
  Allow from all
/Proxy

ProxyPass /SOGo http://127.0.0.1:2/SOGo retry=0

Proxy http://127.0.0.1:2/SOGo
  RequestHeader set x-webobjects-server-port 443
  RequestHeader set x-webobjects-server-name webmail.mydomain.fr
  RequestHeader set x-webobjects-server-url 
https://webmail.mydomain.fr;

  RequestHeader set x-webobjects-server-protocol HTTP/1.0

  AddDefaultCharset UTF-8

  Order allow,deny
  Allow from all
/Proxy
[...]










smime.p7s
Description: S/MIME Cryptographic Signature


[SOGo] SOGo and CAS

2015-01-21 Thread Bruno Richard

Hi All,

I'm new to SOGo. I try to install it on debian jessie.
I want to authenticate users using CAS.
I had inserted in the cas keystore the cert of the apache that is in 
front of SOGo.
However, I have a cas error when I try to log in and the mailbox appears 
empty.


The cas error :
2015-01-21 10:49:25,735 DEBUG 
[org.jasig.cas.ticket.registry.DefaultTicketRegistry] - Ticket 
[TGT-1-bmLPtKJbhpV5hDBdjhKsrESdgsbxSu002oIQVDmBoSITqwnJbf-cas.mydomain.fr] 
found in registry.
2015-01-21 10:49:25,742 DEBUG 
[org.jasig.cas.web.flow.CasFlowExecutionKeyFactory] - Removing flow 
execution '[Ended execution of 'login']' from repository
2015-01-21 10:49:25,742 DEBUG 
[org.jasig.cas.web.flow.CasFlowExecutionKeyFactory] - Removing flow 
execution '[Ended execution of 'login']' from repository
2015-01-21 10:49:25,959 DEBUG 
[org.jasig.cas.web.support.CasArgumentExtractor] - Extractor generated 
service for: https://webmail.mydomain.fr/SOGo/so/index
2015-01-21 10:49:25,962 DEBUG 
[org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler] 
- Attempting to resolve credentials for [callbackUrl: 
https://webmail.mydomain.fr/SOGo/casProxy]
2015-01-21 10:49:26,261 DEBUG [org.jasig.cas.util.HttpClient] - Response 
Code did not match any of the acceptable response codes. Code returned 
was 403
2015-01-21 10:49:26,262 INFO 
[org.jasig.cas.authentication.AuthenticationManagerImpl] - 
AuthenticationHandler: 
org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler 
failed to authenticate the user which provided the following 
credentials: [callbackUrl: https://webmail.mydomain.fr/SOGo/casProxy]
2015-01-21 10:49:26,263 DEBUG 
[org.jasig.cas.ticket.registry.DefaultTicketRegistry] - Attempting to 
retrieve ticket [ST-1-hyppJtF9qvogghaPr9Yg-cas.mydomain.fr]
2015-01-21 10:49:26,263 DEBUG 
[org.jasig.cas.ticket.registry.DefaultTicketRegistry] - Ticket 
[ST-1-hyppJtF9qvogjhaZr9Yg-cas.mydomain.fr] found in registry.
2015-01-21 10:49:26,264 ERROR 
[org.jasig.cas.web.ServiceValidateController] - TicketException 
generating ticket for: [callbackUrl: 
https://webmail.mydomain.fr/SOGo/casProxy]
org.jasig.cas.ticket.TicketCreationException: 
error.authentication.credentials.bad
at 
org.jasig.cas.CentralAuthenticationServiceImpl.delegateTicketGrantingTicket_aroundBody6(CentralAuthenticationServiceImpl.java:300)
at 
org.jasig.cas.CentralAuthenticationServiceImpl.delegateTicketGrantingTicket_aroundBody7$advice(CentralAuthenticationServiceImpl.java:44)
at 
org.jasig.cas.CentralAuthenticationServiceImpl.delegateTicketGrantingTicket(CentralAuthenticationServiceImpl.java:1)

[...]

Please help ! what can I do or test ?
thanks in advance
Bruno

Some points of my configuration :
/etc/sogo/sogo.conf
[...]
  SOGoAuthenticationType = cas;
  SOGoCASServiceURL = https://cas.mydomain.fr/cas;;
  WOWorkersCount = 10;
[...]

/etc/apache/conf-enabled/SOGo.conf
[...]
ProxyPass /SOGo/casProxy http://localhost/cgi-bin/cas-proxy-validate.py
Proxy http://localhost/cgi-bin/cas-proxy-validate.py
  Order deny,allow
  Allow from all
/Proxy

ProxyPass /SOGo http://127.0.0.1:2/SOGo retry=0

Proxy http://127.0.0.1:2/SOGo
  RequestHeader set x-webobjects-server-port 443
  RequestHeader set x-webobjects-server-name webmail.mydomain.fr
  RequestHeader set x-webobjects-server-url https://webmail.mydomain.fr;
  RequestHeader set x-webobjects-server-protocol HTTP/1.0

  AddDefaultCharset UTF-8

  Order allow,deny
  Allow from all
/Proxy
[...]




smime.p7s
Description: S/MIME Cryptographic Signature


[SOGo] 0002489: Apple iCal - OS X 10.9 - Delegated Calendars Show Error

2014-02-17 Thread Richard Ferrara
Hi Guys,

Not getting much back from the bug report 
(http://www.sogo.nu/bugs/view.php?id=2489) so just throwing it out here.

Has anybody come across this?

Summary 0002489: Apple iCal - OS X 10.9 - Delegated Calendars Show Error
Description Hi,

Upon upgrading OS X to 10.9 and first opening iCal.app everything appeared 
normal (logged on user calendars shown with delegated calendars separate). Once 
iCal attempts to communicate with SOGo the following error repeats:

CalDAVAccountRefreshQueuableOperation
Steps To Reproduce  1. Have delegated calendars setup in OS X 10.8
2. Upgrade to OS X 10.9
3. Open iCal
Additional Information  The only way to circumvent this is to remove the 
account completely, setup advanced and populate all the detail.

This will however show all the delegated calendars under the logged on user (as 
if they were their own calendars).

If you at this point attempt to view delegated calendars the error above 
persists.

Please let me know if you require any additional debug information.

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] ANN: SOGo v2.1.0

2013-11-07 Thread Richard Ferrara
For anyone who is using an external reverse proxy it will break, by default it 
now listens on only 127.0.0.1

To fix use: defaults write sogod WOPort 2

On 08/11/2013, at 2:16 PM, Francis Lachapelle flachape...@inverse.ca wrote:

 The Inverse Team is pleased to announce the immediate availability of SOGo 
 2.1.0. 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 (OSX and iOS) and Microsoft Outlook.
 
 SOGo is standard-compliant and supports CalDAV, CardDAV, GroupDAV 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 and 2010
 Two-way synchronization support with any SyncML-capable devices (BlackBerry, 
 Palm, Windows CE, etc.) by using the Funambol SOGo Connector
 Excellent native integration with Apple software (OSX and iOS) and 
 Android-based devices
 and many more! SOGo and our connectors are completely free.
 
 
 Changes from the previous release
 
 Enhancements
 
 improved order of user rights in calendar module (#1431)
 increased height of alarm editor when email alarms are enabled
 added SMTP AUTH support for sogo-ealarms-notify
 added support for LDAP password change against AD/Samba4
 added Apache configuration for Apple autoconfiguration (#2248)
 the init scripts now start 3 sogod processes by default instead of 1
 SOGo now also sends a plain/text parts when sending HTML mails (#2217)
 SOGo now listens on 127.0.0.1:2 by default (instead of *:2)
 SOGo new uses the latest WebDAV sync response type (#1275)
 updated CKEditor to version 4.2.2 and added the tables-related modules (#2410)
 improved display of vEvents in messages
 Bug fixes
 
 fixed handling of an incomplete attachment filename (#2385)
 fixed Finnish mail reply/forward templates (#2401)
 fixed position of red line of current time (#2373)
 fixed crontab error (#2372)
 avoid using too many LDAP connections while looping through LDAP results
 don't encode HTML entities in mail subject of notification (#2402)
 fixed crash of Samba when sending an invitation (#2398)
 fixed selection of destination calendar when saving a task or an event (#2353)
 fixed display remote images preference for message in a popup (#2417)
 avoid crash when handling malformed or non-ASCII HTTP credentials (#2358)
 fixed crash in DAV free-busy lookups when using SQL addressbooks (#2418)
 disabled verbose logging of SMTP sessions by default
 fixed high CPU usage when there are no available child processes and added 
 logging when such a condition occurs
 fixed memory consumption issues when doing dav lookups with huge result set
 fixed S/MIME verification issues with certain OpenSSL versions
 worked around an issue with chunked encoding of CAS replies (#2408)
 fixed OpenChange corruption issue regarding predecessors change list (#2405)
 avoid unnecessary UTF-7 conversions (#2318)
 improved RTF parser to fix vCards (#2354)
 fixed definition of the COMPLETED attribute of vTODO (#2240)
 fixed DAV:resource-id property when sharing calendars (#2399)
 fixed reload of multiple external web calendars (#2221)
 fixed display of PDF files sent from Thunderbird (#2270)
 fixed TLS support for IMAP (#2386)
 fixed creation of web calendar when added using sogo-tool (#2007)
 avoid crash when parsing HTML tags of a message (#2434)
 fixed handling of LDAP groups with no email address (#1328)
 fixed encoding of messages with non-ASCII characters (#2459)
 fixed compilation with clang 3.2 (#2235)
 truncated long fields of quick records to avoid an SQL error (#2461)
 fixed IMAP ACLs (#2433)
 removed inline JavaScript when viewing HTML messages (#2468)
 New extensions for Mozilla Thunderbird 17 ESR and 24 have also been generated.
 
 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.1.0 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 

Re: [SOGo] Help

2013-10-29 Thread Richard Ferrara
This would be a good place to start looking.

http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf
http://wiki.sogo.nu

On 30/10/2013, at 12:52 AM, davo...@gmail.com wrote:

 i am totally new for SOGo and i need help how to configure sogo with existing
 active directory 2012 on CentOS server.
 
 Thank you
 -- 
 users@sogo.nu
 https://inverse.ca/sogo/lists

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Mac_OS_X/10.9 (13A603) CalendarAgent/174

2013-10-24 Thread Richard Ferrara
Nice, should it resolve the delegation issue as well as the unknown webclient?

On 25/10/2013, at 12:00 PM, Ludovic Marcotte lmarco...@inverse.ca wrote:

 On 2013-10-24 8:38 PM, sicr...@bigpond.net.au wrote:
 I assume 10.9 isn't supported yet as sogo logs show:
 I've just pushed a fix in SOPE - try the upcoming nightly builds and report 
 your findings.
 
 Thanks,
 
 -- 
 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

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

[SOGo] Mac_OS_X/10.9 (13A603) CalendarAgent/174

2013-10-24 Thread Richard Ferrara
Hi,

Are there any plans to support iCal in OS X Mavericks?
-- 
users@sogo.nu
https://inverse.ca/sogo/lists