[SOGo] BTS activities for Friday, July 21 2023

2023-07-21 Thread SOGo reporter 
Title: BTS activities for Friday, July 21 2023





  
BTS Activities

  Home page: https://bugs.sogo.nu
  Project: SOGo
  For the period covering: Friday, July 21 2023

  
  
idlast updatestatus (resolution)categorysummary
	
	
	  
	
5759
	2023-07-22 00:17:02
	updated (open)
	Backend Calendar
	Notifications are not processed / not received to the ios calendar
	
	  
	
5831
	2023-07-21 09:18:22
	updated (open)
	Web Calendar
	Shared calendar: changing oder deleting items not working

RE: [SOGo] SOGo no longer talking to mysql

2023-07-21 Thread qhivert 
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    
  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 mailto:users@sogo.nu> > 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

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 the param *MySQL4DebugEnabled = YES*
in your sogo.conf? If not could you add it

RE: [SOGo] SOGo no longer talking to mysql

2023-07-21 Thread qhivert 
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 mailto:users@sogo.nu> > 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    
  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

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 
 *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

Re: [SOGo] undefined symbol: TNEFCheckForSignature

2023-07-21 Thread Kenren Taisho 
Hello Quentin,
Thank you, I have applied the updated ytnef rpm you attached and will
monitor the results.
Will report the findings later.

Kind regards

On Thu, Jul 20, 2023 at 10:39 PM qhivert  wrote:

> Forget the attachment ><
>
>
>
> *From:* users-requ...@sogo.nu  *On Behalf Of *
> qhivert
> *Sent:* jeudi 20 juillet 2023 16:38
> *To:* users@sogo.nu
> *Subject:* RE: [SOGo] undefined symbol: TNEFCheckForSignature
>
>
>
> Hello again Kenren,
> I’ve built another package of ytnef attached to his mail.
> Can you test it?
>
>
>
> First stop the service sogod then remove only the old ytnef without its
> dependencies (or it will remove all sogo):
>
> *rpm -e –nodeps ytnef*
>
> Then install the package I give you:
>
> *yum install ytnef-2.1.2-1.el9.x86_64.rpm*
>
> Restart sogod then.
>
>
>
> Regards,
>
> Quentin
>
>
>
>
>
> *From:* users-requ...@sogo.nu  *On Behalf Of *Kenren
> Taisho
> *Sent:* jeudi 20 juillet 2023 09:18
> *To:* users@sogo.nu
> *Subject:* Re: [SOGo] undefined symbol: TNEFCheckForSignature
>
>
>
> Hi Quentin,
>
> Thanks for the reply, I am running on AlmaLinux 9.2.
>
>
>
>
>
> Kind regards
>
>
>
> On Thu, Jul 20, 2023 at 2:35 PM qhivert  wrote:
>
> Hello Kenren,
>
> What OS do you use for SOGo? Maybe there was a problem while building this
> ytnef package.
>
> Quentin
>
>
>
> *From:* users-requ...@sogo.nu  *On Behalf Of *Kenren
> Taisho
> *Sent:* mercredi 19 juillet 2023 09:04
> *To:* users@sogo.nu
> *Subject:* [SOGo] undefined symbol: TNEFCheckForSignature
>
>
>
> Dear all,
>
>
> I am testing IOS client and found a subfolder not syncing or empty using
> EAS.
> The error that I am getting in the sogo.log is:
> ---
> /usr/sbin/sogod: symbol lookup error:
> /usr/lib64/GNUstep/SOGo/Mailer.SOGo/Mailer: undefined symbol:
> TNEFCheckForSignature
> /usr/sbin/sogod: symbol lookup error:
> /usr/lib64/GNUstep/SOGo/Mailer.SOGo/Mailer: undefined symbol:
> TNEFCheckForSignature
> ---
>
> and in apache.log
>
> ---
> AH00898: Error reading from remote server returned by
> /Microsoft-Server-ActiveSync
> [proxy_http:error] [pid 577548:tid 577610] (20014)Internal error (specific
> information not available): [client xx.xx.xx.xx:25524] AH01102: error
> reading status line from remote server 127.0.0.1:2
> 
> ---
>
> I am using the updated ytnef package from the sogo repository:
> Yerase TNEF Exporter v2.1.2
>
>
>
>
>
> Any idea where to look and how to fix this?
>
>
>
> Thanks in advance
>
>