[SOGo] BTS activities for Tuesday, February 19 2019

2019-02-19 Thread SOGo reporter 
Title: BTS activities for Tuesday, February 19 2019





  
BTS Activities

  Home page: http://www.sogo.nu/bugs
  Project: SOGo
  For the period covering: Tuesday, February 19 2019

  
  
idlast updatestatus (resolution)categorysummary
	
	
	  
	
4641
	2019-02-19 13:22:53
	updated (open)
	Backend Calendar
	Error during sync between Outlook 2016/CalDavSynchronizer 3.40 and SOGo 4.05
	
	  
	
4683
	2019-02-19 17:10:46
	updated (open)
	i18n
	Swedish language missing "JunkFolderName" in translations
	
	  
	
4684
	2019-02-19 22:52:48
	updated (open)
	sogo-tool
	sogo-tool on FreeBSD 12.0 always triggers MySQL error "Got an error reading communication packets"
	
	  
	
1187
	2019-02-19 11:14:14
	updated (open)
	Web Address Book
	NFR: upload photo from the web interface
	
	  
	
4661
	2019-02-19 13:21:46
	updated (open)
	Web Address Book
	Contact: When adding new group to connect the groupname ist replaced by "[object Object]"
	
	  
	
4679
	2019-02-19 11:14:14
	updated (open)
	Web Address Book
	No permite colocar la foto a un contacto
	
	  
	
4582
	2019-02-19 13:32:03
	updated (open)
	Web Mail
	Signed and encrypted messages sent from Outlook can't be opened
	
	  
	
4596
	2019-02-19 13:23:32
	updated (open)
	Web Mail
	Report Junk/NoJunk icons: add confirmation action, please.
	
	  
	
4680
	2019-02-19 11:09:12
	updated (open)
	Web Mail
	Solo permite adjuntar archivos a un correo electornico
	
	  
	
4682
	2019-02-19 00:40:51
	updated (open)
	Web Mail
	New funcionality
	
	  
	
4488
	2019-02-19 14:02:54
	updated (open)
	with SOGo
	TB fails to update an existing contact via CardDAV
	
	  
	
4619
	2019-02-19 15:34:39
	feedback (reopened)
	Web Mail
	Text entered into a message being forwarded disappers
	
	  
	
3685
	2019-02-19 13:44:21
	resolved (fixed)
	Backend General
	Feature request: support place holder in LDAP base dn, bind dn
	
	  
	
4460
	2019-02-19 14:53:43
	resolved (fixed)
	Web Mail
	Sent folder: sent messages cannot be replied to their BCC email addresses
	
	  
	
4450
	2019-02-19 14:03:34
	closed (not a bug)
	Backend Address Book
	SoGo Integrator and Connector breaks the personal adressbook and collected adresses / you cant send E-Mails
	
	  
	
4664
	2019-02-19 13:17:36
	closed (fixed)
	GUI
	Odd behaviour of failed login brute force detection
	
	  
	
4403
	2019-02-19 14:00:27
	closed (not a bug)
	Web Calendar
	Multiplebookings not working as epxected
	
	  
	
4653
	2019-02-19 13:32:58
	closed (not a bug)
	Web Calendar
	sharing with groups does not exist
	
	  
	
4507
	2019-02-19 11:24:05
	closed (not a bug)
	Web Mail
	all emails disapparead (cyrus folder renamed with a DOT appended)
	
	  
	
4467
	2019-02-19 11:35:13
	closed (not a bug)
	with SOGo
	Cannot install (dpkg error)
	
	  
	
  
  


-- users@sogo.nuhttps://inverse.ca/sogo/lists

Re: [SOGo] Unable to get access to SOGo for unknown reason.

2019-02-19 Thread Andrey Cherepanov 

19.02.2019 22:09, Dmytro Lysytsyn (dmytro.lysyt...@gmail.com) пишет:

Hello there!
Hope you're doing well.
I'm trying to setup SOGo for the first time. And now I'm stuck with no 
visible reasons for it.

Would somebody please show me the right way?


Symptoms are: when I'm trying to log on to SOGo under any username 
('sogoadm' for example) using 'https://kntest3.ldvtest.org.ua/SOGo' 
link, this is happened:
1. it redirects me to '/SOGo/', where  is that 
what I'm trying to log on with. And it still shows me SOGo 
white-and-green login page.


2. If I try to login again (now with 
'https://kntest3.ldvtest.org.ua/SOGo/sogoadm' URL) it redirects me 
again. New URL is 'https://kntest3.ldvtest.org.ua/SOGo/so/sogoadm'.
3. If I'll still try to login it will silently redirect me on what 
last page again and again, i.g. URL will now always 
'https://kntest3.ldvtest.org.ua/SOGo/so/sogoadm' and nothing more 
happenes.




From mail from Julian Kippels at 21.09.2018 in users@sogo.nu:

Hi again,

I found the problem. It wasn't anything in the /etc/sogo/sogo.conf at
all. The problem was with the Apache configuration. When I comment out
this line


RequestHeader set "x-webobjects-server-url""https://%{HTTP_HOST}e;
env=HTTP_HOST


from /etc/httpd/conf.d/SOGo.conf everything works as it should.

Julian


See also fix in package:

http://git.altlinux.org/people/cas/packages/sogo.git?p=sogo.git;a=commit;h=6003f42429088b092ace1944d8d9b92fc48a7507

--
Andrey Cherepanov
c...@altlinux.org

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

[SOGo] Unable to get access to SOGo for unknown reason.

2019-02-19 Thread Dmytro Lysytsyn 

Hello there!
Hope you're doing well.
I'm trying to setup SOGo for the first time. And now I'm stuck with no 
visible reasons for it.

Would somebody please show me the right way?


Symptoms are: when I'm trying to log on to SOGo under any username 
('sogoadm' for example) using 'https://kntest3.ldvtest.org.ua/SOGo' 
link, this is happened:
1. it redirects me to '/SOGo/', where  is that what 
I'm trying to log on with. And it still shows me SOGo white-and-green 
login page.


2. If I try to login again (now with 
'https://kntest3.ldvtest.org.ua/SOGo/sogoadm' URL) it redirects me 
again. New URL is 'https://kntest3.ldvtest.org.ua/SOGo/so/sogoadm'.
3. If I'll still try to login it will silently redirect me on what last 
page again and again, i.g. URL will now always 
'https://kntest3.ldvtest.org.ua/SOGo/so/sogoadm' and nothing more happenes.


I tried number of configuration settings but all the same. Tried 
different logins too.

Server (every package is up to date):

OS: Ubuntu 18.04;

SOGo: 4.0.5.20190219-1 (same was on 4.0.5.20190218);
DB: PostgreSQL 10+190;
LDAP: slapd 2.4.45+dfsg-1ubuntu1.1 + Fusion Directory 
1.0.19-1ubuntu0.18.04.1;

web: Apache2 2.4.29-1ubuntu4.5.


Here is SOGo's logfile with debug turned on:
--- 8< 
---
Feb 19 19:42:19 sogod [2411]: |SOGo| starting method 'POST' on uri 
'/SOGo/connect'
Feb 19 19:42:19 sogod [2411]: <0x0x55dfe8718ec0[NGLdapConnection]> Using 
ldap_initialize for LDAP URL: ldap://127.0.0.1:389
Feb 19 19:42:19 sogod [2411]: SOGoRootPage successful login from 
'194.187.110.158' for user 'sogoadm' - expire = -1  grace = -1
2019-02-19 19:42:19.108 sogod[2411:2411] Creating NGLdapConnection 
instance for bindDN 
'uid=sogoconnect,ou=people,dc=kntest3,dc=ldvtest,dc=org,dc=ua'
Feb 19 19:42:19 sogod [2411]: <0x0x55dfe863c050[NGLdapConnection]> Using 
ldap_initialize for LDAP URL: ldap://127.0.0.1:389
2019-02-19 19:42:19.112 sogod[2411:2411] -[NGLdapConnection 
_searchAtBaseDN:qualifier:attributes:scope:]: search at base 
'ou=people,dc=kntest3,dc=ldvtest,dc=org,dc=ua' filter 
'(|(uid=sogoadm)(mail=sogoadm))' for attrs '*'
2019-02-19 19:42:19.120 sogod[2411:2411] PostgreSQL72 connection 
established: <0x0x55dfe86b2b70[PGConnection]: connection=0x0x55dfe8865080>
2019-02-19 19:42:19.120 sogod[2411:2411] PostgreSQL72 channel 
0x0x55dfe87603d0 opened (connection=<0x0x55dfe86b2b70[PGConnection]: 
connection=0x0x55dfe8865080>)
2019-02-19 19:42:19.126 sogod[2411:2411] PostgreSQL72 connection 
established: <0x0x55dfe8792b70[PGConnection]: connection=0x0x55dfe8864c20>
2019-02-19 19:42:19.126 sogod[2411:2411] PostgreSQL72 channel 
0x0x55dfe8814740 opened (connection=<0x0x55dfe8792b70[PGConnection]: 
connection=0x0x55dfe8864c20>)
2019-02-19 19:42:19.126 sogod[2411:2411] PG0x0x55dfe8814740 SQL: BEGIN 
TRANSACTION
2019-02-19 19:42:19.126 sogod[2411:2411] PG0x0x55dfe8814740 SQL: SELECT 
t1.c_creationdate, t1.c_id, t1.c_lastseen, t1.c_value FROM 
sogo_sessions_folder t1 WHERE t1.c_id='bbr5Kbvmmro81wGgKNP0sA=='
2019-02-19 19:42:19.128 sogod[2411:2411] PG0x0x55dfe8814740 SQL: 
ROLLBACK TRANSACTION
2019-02-19 19:42:19.129 sogod[2411:2411] PG0x0x55dfe87603d0 SQL: BEGIN 
TRANSACTION
2019-02-19 19:42:19.129 sogod[2411:2411] PG0x0x55dfe87603d0 SQL: INSERT 
INTO sogo_sessions_folder (c_lastseen, c_creationdate, c_value, c_id) 
VALUES (1550601739, 1550601739, 
'knkGNdkUTkLAvndhdndKmaPQQ7AIHJJAmGoUFsHi89EyZfCRgWJG+MbQCcpzbL/9Pecx9e+GeLiuZg9HmxQDq0vVLrDaUw9+CZuAJhHFqCELDBpSfHounkPO1k43fZ4pXqg+N1ppJqX4NT6Xg7xeLNWyGSKXsJqKZmnVX7PVkYQln5Gk38bXQInDV7dl4HzdEjRtmDjjeJQRvaDGfs0Yfw==', 
'bbr5Kbvmmro81wGgKNP0sA==')
2019-02-19 19:42:19.130 sogod[2411:2411] PG0x0x55dfe87603d0 SQL: COMMIT 
TRANSACTION
Feb 19 19:42:19 sogod [2411]: |SOGo| request took 0.027147 seconds to 
execute
Feb 19 19:42:19 sogod [2411]: 194.187.110.158 "POST /SOGo/connect 
HTTP/1.1" 200 2/86 0.032 - - 12K
Feb 19 19:42:20 sogod [2411]: |SOGo| starting method 'GET' on uri 
'/SOGo/so/sogoadm'
Feb 19 19:42:20 sogod [2411]: <0x0x55dfe8657190[NGLdapConnection]> Using 
ldap_initialize for LDAP URL: ldap://127.0.0.1:389
2019-02-19 19:42:20.187 sogod[2411:2411] Creating NGLdapConnection 
instance for bindDN 
'uid=sogoconnect,ou=people,dc=kntest3,dc=ldvtest,dc=org,dc=ua'
Feb 19 19:42:20 sogod [2411]: <0x0x55dfe8693f60[NGLdapConnection]> Using 
ldap_initialize for LDAP URL: ldap://127.0.0.1:389
2019-02-19 19:42:20.191 sogod[2411:2411] -[NGLdapConnection 
_searchAtBaseDN:qualifier:attributes:scope:]: search at base 
'ou=people,dc=kntest3,dc=ldvtest,dc=org,dc=ua' filter 
'(|(uid=sogoadm)(mail=sogoadm))' for attrs '*'
Feb 19 19:42:20 sogod [2411]: <0x0x55dfe8816130[NGLdapConnection]> Using 
ldap_initialize for LDAP URL: ldap://127.0.0.1:389
2019-02-19 19:42:20.193 sogod[2411:2411] Creating NGLdapConnection 
instance for bindDN 
'uid=sogoconnect,ou=people,dc=kntest3,dc=ldvtest,dc=org,dc=ua'
Feb 19 19:42:20 sogod [2411]: <0x0x55dfe875e070[NGLdapConnection]> Using

Re: [SOGo] A calendar got created about 500 times for one user and can't be deleted

2019-02-19 Thread goetz.reini...@filmakademie.de 


> Am 18.02.2019 um 15:24 schrieb Christian Mack 
> (christian.m...@uni-konstanz.de) :
> 
> Hello
> 
> Am 18.02.19 um 13:19 schrieb Götz Reinicke (goetz.reini...@filmakademie.de):
>> Hi,
>> 
>> may be someone has an idea or explanation, why a calendar was created about 
>> 500 times for an user. She told me, she added one instance by mistake and 
>> deleted the calendar. But it did not disappear, instead it got „magically“ 
>> created more than 500 times over the last couple of days.
>> 
>> And she can’t delete the calendars.
>> 
> 
> Are there any special characters in the calendars name?
> Do you see those 500 entries/calendars also in the backup with sogo-tool?
> Did she get additional privileges for that calendar from the owner?
> 

Hi Christian,

no, there are no special characters in the name and she is the owner of the 
calendar, had created it in the first place in SOGo not in icloud.

The entries are in the backup.

e.g. always with different Calendar/

"/Users/USERSID/Calendar/054F1B71-9E28-4CA5-9ACB-8027D595CE51" = {
acl = {
};
displayname = "Anderswo Unterwegs";
records = (
);
};


/Götz

smime.p7s
Description: S/MIME cryptographic signature

Re: [SOGo] Web Access => Request Failed

2019-02-19 Thread Christian Mack 
Hello

It was fixed 5 days ago in sources, so not sure if there are already
packages for FreeBSD available.


Kind regards,
Christian Mack

Am 19.02.19 um 14:31 schrieb Tomek Kaźmierczak (tom.k...@gmail.com):
> ok, i installed again sope3 but problem is still, in FreeBSD ports the
> sope3 version is: *sope3_3.2.10_5*
> https://www.freshports.org/devel/sope3/
> 
> in which version this bug was fixed?
> 
> wt., 19 lut 2019 o 13:54 Christian Mack  napisał(a):
> 
>> Hello
>>
>> That is a known issue in SOPE.
>> See Bug
>> https://sogo.nu/bugs/view.php?id=4659
>>
>>
>> Kind regards,
>> Christian Mack
>>
>> Am 19.02.19 um 12:59 schrieb Tomek Kaźmierczak (tom.k...@gmail.com):
>>> Hi,
>>>
>>> use SOGo (with iRedMail) on FreeBSD, sogo version 3.2.10_6 and use Nginx
>>>
>>> after last update i have trouble with see message, when log in on the web
>>> interface.
>>> Other method works fine (Outlook and Phone), Calendar and Contacts too...
>>>
>>> but when i Log In via web interface i see all catalogue (i can change
>>> them), i can send message but when i click on message there is only red
>>> Message od black box: Request Failed
>>>
>>> I enable debug in sogo.conf and this is message from log:
>>>
>>> Feb 19 12:20:58 sogod [19038]: |SOGo| starting method 'POST' on uri
>>> '/SOGo/so/u...@domain.org/Mail/0/folderINBOX/expunge'
>>> Feb 19 12:20:58 sogod [43417]: |SOGo| starting method 'GET' on uri
>>> '/SOGo/so/u...@domain.org/Mail/view'
>>> Feb 19 12:20:59 sogod [43417]: |SOGo| request took 0.493925 seconds to
>>> execute
>>> Feb 19 12:20:59 sogod [43417]: 192.168.20.129 "GET /SOGo/so/
>>> u...@domain.org/Mail/view HTTP/1.0" 200 20074/0 0.513 75727 73% -
>>> Feb 19 12:20:59 sogod [19038]: |SOGo| request took 0.742857 seconds to
>>> execute
>>>
>>> *Feb 19 12:20:59 sogod [19038]: [ERROR]
>> <0x0x80a2ecbe8[WOHttpTransaction]>
>>> client disconnected during delivery of response for
>>> >> uri=/SOGo/so/u...@domain.org/Mail/0/folderINBOX/expunge
>>>  app=SOGo rqKey=so
>>> rqPath=u...@domain.org/Mail/0/folderINBOX/expunge
>>> > (len=58): the
>> socket
>>> was shutdown*
>>>
>>> Feb 19 12:20:59 sogod [19038]: 192.168.20.129 "POST /SOGo/so/
>>> u...@domain.org/Mail/0/folderINBOX/expunge HTTP/1.0" 200 58/0 0.755 - -
>> -
>>> Feb 19 12:20:59 sogod [19038]: |SOGo| starting method 'GET' on uri
>>> '/SOGo/so/u...@domain.org/Calendar/alarmslist?browserTime=1550575258'
>>> Feb 19 12:20:59 sogod [43417]: |SOGo| starting method 'GET' on uri
>>> '/SOGo/so/u...@domain.org/Mail/0/view'
>>> Feb 19 12:20:59 sogod [19038]: |SOGo| request took 0.021657 seconds to
>>> execute
>>>
>>

-- 
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] Web Access => Request Failed

2019-02-19 Thread tom.k...@gmail.com 
ok, i installed again sope3 but problem is still, in FreeBSD ports the
sope3 version is: *sope3_3.2.10_5*
https://www.freshports.org/devel/sope3/

in which version this bug was fixed?

wt., 19 lut 2019 o 13:54 Christian Mack  napisał(a):

> Hello
>
> That is a known issue in SOPE.
> See Bug
> https://sogo.nu/bugs/view.php?id=4659
>
>
> Kind regards,
> Christian Mack
>
> Am 19.02.19 um 12:59 schrieb Tomek Kaźmierczak (tom.k...@gmail.com):
> > Hi,
> >
> > use SOGo (with iRedMail) on FreeBSD, sogo version 3.2.10_6 and use Nginx
> >
> > after last update i have trouble with see message, when log in on the web
> > interface.
> > Other method works fine (Outlook and Phone), Calendar and Contacts too...
> >
> > but when i Log In via web interface i see all catalogue (i can change
> > them), i can send message but when i click on message there is only red
> > Message od black box: Request Failed
> >
> > I enable debug in sogo.conf and this is message from log:
> >
> > Feb 19 12:20:58 sogod [19038]: |SOGo| starting method 'POST' on uri
> > '/SOGo/so/u...@domain.org/Mail/0/folderINBOX/expunge'
> > Feb 19 12:20:58 sogod [43417]: |SOGo| starting method 'GET' on uri
> > '/SOGo/so/u...@domain.org/Mail/view'
> > Feb 19 12:20:59 sogod [43417]: |SOGo| request took 0.493925 seconds to
> > execute
> > Feb 19 12:20:59 sogod [43417]: 192.168.20.129 "GET /SOGo/so/
> > u...@domain.org/Mail/view HTTP/1.0" 200 20074/0 0.513 75727 73% -
> > Feb 19 12:20:59 sogod [19038]: |SOGo| request took 0.742857 seconds to
> > execute
> >
> > *Feb 19 12:20:59 sogod [19038]: [ERROR]
> <0x0x80a2ecbe8[WOHttpTransaction]>
> > client disconnected during delivery of response for
> >  > uri=/SOGo/so/u...@domain.org/Mail/0/folderINBOX/expunge
> >  app=SOGo rqKey=so
> > rqPath=u...@domain.org/Mail/0/folderINBOX/expunge
> > > (len=58): the
> socket
> > was shutdown*
> >
> > Feb 19 12:20:59 sogod [19038]: 192.168.20.129 "POST /SOGo/so/
> > u...@domain.org/Mail/0/folderINBOX/expunge HTTP/1.0" 200 58/0 0.755 - -
> -
> > Feb 19 12:20:59 sogod [19038]: |SOGo| starting method 'GET' on uri
> > '/SOGo/so/u...@domain.org/Calendar/alarmslist?browserTime=1550575258'
> > Feb 19 12:20:59 sogod [43417]: |SOGo| starting method 'GET' on uri
> > '/SOGo/so/u...@domain.org/Mail/0/view'
> > Feb 19 12:20:59 sogod [19038]: |SOGo| request took 0.021657 seconds to
> > execute
> >
>
>
> --
> Christian Mack
> Universität Konstanz
> Kommunikations-, Informations-, Medienzentrum (KIM)
> Abteilung Basisdienste
> 78457 Konstanz
> +49 7531 88-4416
>
>
-- 
users@sogo.nu
https://inverse.ca/sogo/lists