[SOGo] BTS activities for Sunday, March 05 2023

2023-03-05 Thread SOGo reporter
Title: BTS activities for Sunday, March 05 2023





  
BTS Activities

  Home page: https://bugs.sogo.nu
  Project: SOGo
  For the period covering: Sunday, March 05 2023

  
  
idlast updatestatus (resolution)categorysummary
	
	
	  
	
5666
	2023-03-05 14:16:46
	resolved (fixed)
	Packaging (Debian)
	Installation on Ubuntu focal/20.04 fails
	
	  
	
  
  




Re: [SOGo] Login SOGo and IMAP login must be the same?

2023-03-05 Thread grog_
Hi, can you share your solution with us?

Thanks,
Luigi

Il dom 5 mar 2023, 23:57 HEBI K  ha scritto:

> I solved my problems
> Thanks
>
> Samuel Wolf  schrieb am So., 5. März 2023, 16:42:
>
>> Hi,
>>
>> I testing SOGo first time and on thing is not clear to me:
>> SOGo login for example via LDAP and IMAP server login must be the same?
>>
>> Or is it possible to authenticate against LDAP and use complete
>> different logins for the IMAP server?
>>
>> Thanks.
>>
>> Samuel
>>
>


Re: [SOGo] Login SOGo and IMAP login must be the same?

2023-03-05 Thread HEBI K
I solved my problems
Thanks

Samuel Wolf  schrieb am So., 5. März 2023, 16:42:

> Hi,
>
> I testing SOGo first time and on thing is not clear to me:
> SOGo login for example via LDAP and IMAP server login must be the same?
>
> Or is it possible to authenticate against LDAP and use complete
> different logins for the IMAP server?
>
> Thanks.
>
> Samuel
>


Re: [SOGo] Login SOGo and IMAP login must be the same?

2023-03-05 Thread Odhiambo Washington
SOGo is just a fronted. You IMAP server determines how you authenticate.

On Sun, Mar 5, 2023, 19:02 Samuel Wolf  wrote:

> Hi,
>
> I testing SOGo first time and on thing is not clear to me:
> SOGo login for example via LDAP and IMAP server login must be the same?
>
> Or is it possible to authenticate against LDAP and use complete
> different logins for the IMAP server?
>
> Thanks.
>
> Samuel
>


[SOGo] Creating Sieve Filter with sogo-tool

2023-03-05 Thread Steve
Hi, 

I've succesfully created a sieve filter using

sudo -u sogo sogo-tool user-preferences set defaults m...@example.com -p 
/etc/sogo/sieve.cred SOGoSieveFilters '{"SOGoSieveFilters": 
[{"active":true,"actions":[{"argument":"SASL Login 
Failures","method":"fileinto"}],"name":"SASL Login 
Failures","rules":[{"field":"subject","operator":"contains","value":"SASL Login 
Failure"}],"match":"all"}]}' 

However on the majority of occassions the sogo-tool process hangs. When it does 
complete I see this in Terminal:

2023-03-05 11:46:39.886 sogo-tool[760185:760185] 
   query has no 
results.
2023-03-05 11:46:39.886 sogo-tool[760185:760185] 
 SQL: COMMIT;
2023-03-05 11:46:39.889 sogo-tool[760185:760185] 
   query has no 
results.
C[0x559581b7c5a0]: 5 logout
S[0x559581ebedf0]: * BYE Logging out

When it hangs, it doesn't get to the logout step and I only see this and have 
to ctrl-c to end the process:

2023-03-05 11:46:39.886 sogo-tool[760185:760185] 
   query has no 
results.
2023-03-05 11:46:39.886 sogo-tool[760185:760185] 
 SQL: COMMIT;
2023-03-05 11:46:39.889 sogo-tool[760185:760185] 
   query has no 
results.

Interestingly it does create/update the sieve filter for the user in the 
logo_user_profile table of the logo database. 

Any ideas on how this can be rectified would be gratefully appreciated.

Thanks, Steve.

[SOGo] Login SOGo and IMAP login must be the same?

2023-03-05 Thread Samuel Wolf
Hi,

I testing SOGo first time and on thing is not clear to me:
SOGo login for example via LDAP and IMAP server login must be the same?

Or is it possible to authenticate against LDAP and use complete
different logins for the IMAP server?

Thanks.

Samuel


Re: [SOGo] Sogo Calendar events deleted

2023-03-05 Thread HYVERNAT Philippe

Le 14/02/2023 à 09:01, Odhiambo Washington (odhia...@gmail.com) a écrit :



On Tue, Feb 14, 2023 at 9:50 AM HYVERNAT Philippe  wrote:

In complement, we have many error like this :

I follow recommendations from the list to solve this issue but
never works.


 sogod [89977]: <0x0x804808158[SOGoCache]> an error occurred when
caching value for key '/Users/u...@mydomein.com/Calendar/personal
': "SERVER HAS FAILED
AND IS DISABLED UNTIL TIMED RETRY"


For starters, may I please request you to try and adhere to the 
following guideline when communicating on mailing lists:

1. https://support.google.com/a/users/answer/9283192#better-conversations
I am mostly interested in replying inline and NOT top-posting. Thank 
you very much.


Now, looking at your captured error, it would appear that you have a 
problem with caching and that problem lies with memcached, because 
that is where caching is done.
On FreeBSD which I believe you are familiar with, you can do one of 
two things:
1. Log all queries to memcached. You do this by adding -vvv (the 
number of v's depend on the verbosity you want) to memcached_flags in 
rc.conf and restarting memcached.

    I'd also try and give Memcached a little more RAM to use with -m 128


In /etc/rc.conf :

memcached_enable="YES"
memcached_flags="-vvv -m 128"


2. Capture these queries in it's own file by adding a specific logging 
config to /etc/syslog.conf:


!memcached
*.* /var/log/memcached.log #please touch this file!
Then restart syslogd with: kill -HUP `cat /var/run/syslog.pid`

From there, for every entry about caching in sogo.log, check for a 
corresponding entry in memcached.log.

Hopefully, you will nail the problem by deducing a solution.


Here's the entry memcached :

Kicking LRU crawler off for LRU 244
Kicking LRU crawler off for LRU 245
Kicking LRU crawler off for LRU 246
Kicking LRU crawler off for LRU 247
Kicking LRU crawler off for LRU 248
Kicking LRU crawler off for LRU 249
Kicking LRU crawler off for LRU 250
Kicking LRU crawler off for LRU 251
Kicking LRU crawler off for LRU 252
Kicking LRU crawler off for LRU 253
Kicking LRU crawler off for LRU 254
Kicking LRU crawler off for LRU 255
Nothing left to crawl for 1
Nothing left to crawl for 2
Nothing left to crawl for 3
Nothing left to crawl for 4
Nothing left to crawl for 5

 to 255

With the sogocache error

 <0x0x804ae81a8[SOGoCache]> an error occurred when caching value for 
key '/Users/u...@mydomain.com/Calendar/personal': "SERVER HAS FAILED AND 
IS DISABLED UNTIL TIMED RETRY"






Sorry for the lecture. I just did not want to make assumptions that 
you know what I wanted you to do :)


--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)