[SOGo] BTS activities for Tuesday, June 04 2019

2019-06-04 Thread SOGo reporter 
Title: BTS activities for Tuesday, June 04 2019





  
BTS Activities

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

  
  
idlast updatestatus (resolution)categorysummary
	
	
	  
	
4719
	2019-06-04 09:50:37
	updated (open)
	Backend Calendar
	Certain Emoticons cause calendar events to not be accessbile
	
	  
	
4736
	2019-06-04 10:00:34
	updated (open)
	with SOGo
	Switching to text only modus
	
	  
	
4757
	2019-06-04 15:03:28
	assigned (reopened)
	Backend Mail
	Getting this all time on log
	
	  
	
  
  


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

Re: [SOGo] Unable to connect to Dovecot IMAP (UnexpectedEndOfStream)

2019-06-04 Thread Riccardo Bicelli 
Same here on CentOS updating to yesterday nightly.
Had to rollback,

Il giorno mar 4 giu 2019 alle ore 16:07 Alexander Koch 
ha scritto:
>
> > > Hi all,
> > >
> > > I'm trying to use Sogo (4.0.7-1 from Debian Buster) to connect to a
> > > Dovecot (2.3.4.1 from Debian Buster) instance running on another host
> > > via IMAP (port 143, TLS).
> > >
> > > I'm getting the following error ('sogo.log', all debug options on):
> > >
> > >> sogod [4426]: <0x0x55b28a41dde0[NGImap4Client]> TLS started successfully.
> > >> sogod [4426]: <0x0x55b28a41dde0[NGImap4Client]> ERROR(-[NGImap4Client 
> > >> _processUnknownCommandParserException:]): catched non-IMAP4 parsing 
> > >> exception UnexpectedEndOfStream: the parsed stream ended unexpectedly
> > >> sogod [4426]: [ERROR] <0x0x55b28a777e30[NGImap4ConnectionManager]> IMAP4 
> > >> login failed:
> > >>host=mail.example.net, user=u...@example.net, pwd=yes
> > >>url=imaps://user%40example@mail.example.net/?tls=YES
> > >>base=(null)
> > >>base-class=(null))
> > >>= <0x0x55b28a41dde0[NGImap4Client]: login=u...@example.net(pwd) 
> > >> socket=>
> > >> sogod [4426]: [ERROR] <0x55b28a7ea850[SOGoMailAccount]:0> Could not 
> > >> connect IMAP4
> > >> sogod [4426]: |SOGo| request took 0.522964 seconds to execute
> > >
> > >
> > > On the Dovecot side it looks just like a successful login but no IMAP
> > > commands being sent by the client:
> > >
> > >> dovecot: imap-login: Login: user=, method=PLAIN, 
> > >> rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, mpid=8371, TLS, 
> > >> session=
> > >> dovecot: imap-login: Login: user=, method=PLAIN, 
> > >> rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, mpid=8373, TLS, 
> > >> session=
> > >> dovecot: imap(u...@example.net)<8371>: Connection 
> > >> closed (No commands sent) in=0 out=379 deleted=0 expunged=0 trashed=0 
> > >> hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0
> > >> dovecot: imap(u...@example.net)<8373>: Connection 
> > >> closed (No commands sent) in=0 out=379 deleted=0 expunged=0 trashed=0 
> > >> hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0
> > >
> > >
> > > Any idea what could be wrong? I'm using the following IMAP server
> > > string in sogo.conf:
> > >
> > >SOGoIMAPServer = "imap://mail.example.net:143/?tls=YES";
> >
> > have you tried using imaps://... instead of imap:// ?
>
> If I substitude 'imap' by 'imaps' and keep '?tls=YES' then very bad
> things seem to happen:
>
> The web interface does shows a blank (white) page and I see the
> following in sogo.log:
>
> > sogod [7856]: [WARN] <0x0x5612ca44e230[WOWatchDogChild]> pid 7857 has been 
> > hanging in the same request for 1 minutes
>
>
> Kind regards,
>
> Alex
> --
> users@sogo.nu
> https://inverse.ca/sogo/lists
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Unable to connect to Dovecot IMAP (UnexpectedEndOfStream)

2019-06-04 Thread Alexander Koch 
> > Hi all,
> > 
> > I'm trying to use Sogo (4.0.7-1 from Debian Buster) to connect to a
> > Dovecot (2.3.4.1 from Debian Buster) instance running on another host
> > via IMAP (port 143, TLS).
> > 
> > I'm getting the following error ('sogo.log', all debug options on):
> >   
> >> sogod [4426]: <0x0x55b28a41dde0[NGImap4Client]> TLS started successfully.
> >> sogod [4426]: <0x0x55b28a41dde0[NGImap4Client]> ERROR(-[NGImap4Client 
> >> _processUnknownCommandParserException:]): catched non-IMAP4 parsing 
> >> exception UnexpectedEndOfStream: the parsed stream ended unexpectedly
> >> sogod [4426]: [ERROR] <0x0x55b28a777e30[NGImap4ConnectionManager]> IMAP4 
> >> login failed:
> >>host=mail.example.net, user=u...@example.net, pwd=yes
> >>url=imaps://user%40example@mail.example.net/?tls=YES
> >>base=(null)
> >>base-class=(null))
> >>= <0x0x55b28a41dde0[NGImap4Client]: login=u...@example.net(pwd) 
> >> socket=>
> >> sogod [4426]: [ERROR] <0x55b28a7ea850[SOGoMailAccount]:0> Could not 
> >> connect IMAP4
> >> sogod [4426]: |SOGo| request took 0.522964 seconds to execute  
> > 
> > 
> > On the Dovecot side it looks just like a successful login but no IMAP
> > commands being sent by the client:
> >   
> >> dovecot: imap-login: Login: user=, method=PLAIN, 
> >> rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, mpid=8371, TLS, 
> >> session=
> >> dovecot: imap-login: Login: user=, method=PLAIN, 
> >> rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, mpid=8373, TLS, 
> >> session=
> >> dovecot: imap(u...@example.net)<8371>: Connection closed 
> >> (No commands sent) in=0 out=379 deleted=0 expunged=0 trashed=0 hdr_count=0 
> >> hdr_bytes=0 body_count=0 body_bytes=0
> >> dovecot: imap(u...@example.net)<8373>: Connection closed 
> >> (No commands sent) in=0 out=379 deleted=0 expunged=0 trashed=0 hdr_count=0 
> >> hdr_bytes=0 body_count=0 body_bytes=0  
> > 
> > 
> > Any idea what could be wrong? I'm using the following IMAP server
> > string in sogo.conf:
> > 
> >SOGoIMAPServer = "imap://mail.example.net:143/?tls=YES";  
> 
> have you tried using imaps://... instead of imap:// ?

If I substitude 'imap' by 'imaps' and keep '?tls=YES' then very bad
things seem to happen:

The web interface does shows a blank (white) page and I see the
following in sogo.log:

> sogod [7856]: [WARN] <0x0x5612ca44e230[WOWatchDogChild]> pid 7857 has been 
> hanging in the same request for 1 minutes


Kind regards,

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

Re: [SOGo] Unable to connect to Dovecot IMAP (UnexpectedEndOfStream)

2019-06-04 Thread Alexander Koch 
> if this IMAP server is also listening on port 993 - could you try the 
> following:
> 
> SOGoIMAPServer = imaps://mail.example.net;
> 
> Just to see if there's any difference.

Originally I had not opened TCP/993 but I gave it a shot just now,
using

  SOGoIMAPServer = "imaps://mail.example.net";

It throws another Exception in addition to the ones I already mentioned:

> 14:52:25.602 sogod[7748:7748] ERROR(-[NSException(NGMiscellaneous) 
> initWithFormat:]): missing format!
> 14:52:25 sogod [7748]: <0x0x55d6e821a2b0[NGImap4Client]> 
> ERROR(-[NGImap4Client _processUnknownCommandParserException:]): catched 
> non-IMAP4 parsing exception UnexpectedEndOfStream: the parsed stream ended 
> unexpectedly
> 14:52:25 sogod [7748]: [ERROR] <0x0x55d6e82f21c0[NGImap4ConnectionManager]> 
> IMAP4 login failed:
>   host=mail.example.net, user=u...@example.net, pwd=yes
>   url=imaps://user%40example@mail.example.net/
>   base=(null)
>   base-class=(null))
>   = <0x0x55d6e821a2b0[NGImap4Client]: login=u...@example.net(pwd) 
> socket= address=<0x0x55d6e8535a20[NGInternetSocketAddress]: host=web.example.net 
> port=60150> connectedTo=<0x0x55d6e821a560[NGInternetSocketAddress]: 
> host=mail.example.net port=993>>>
> 14:52:25 sogod [7748]: [ERROR] <0x55d6e7f04d90[SOGoMailAccount]:0> Could not 
> connect IMAP4


On the other side (Dovecot) it doesn't seem to make a difference.

I also tried

  SOGoIMAPServer = "imaps://mail.example.net:993/";

just to make sure the port number is not mandatory (guessing from the
colon in the new exception message). No luck either.


Kind regards,

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

Re: [SOGo] Unable to connect to Dovecot IMAP (UnexpectedEndOfStream)

2019-06-04 Thread Markus Winkler 

Hi Alexander,

On Tue, 04 Jun 2019 at 12:35:48PM +0200, Alexander Koch wrote:

Dovecot (2.3.4.1 from Debian Buster) instance running on another host
via IMAP (port 143, TLS).


if this IMAP server is also listening on port 993 - could you try the 
following:


SOGoIMAPServer = imaps://mail.example.net;

Just to see if there's any difference.

Regards,
Markus

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

Re: [SOGo] Unable to connect to Dovecot IMAP (UnexpectedEndOfStream)

2019-06-04 Thread Daniel Le Bray 

hello,

Le 04/06/2019 à 12:35, Alexander Koch (m...@alexanderkoch.net) a écrit :

Hi all,

I'm trying to use Sogo (4.0.7-1 from Debian Buster) to connect to a
Dovecot (2.3.4.1 from Debian Buster) instance running on another host
via IMAP (port 143, TLS).

I'm getting the following error ('sogo.log', all debug options on):


sogod [4426]: <0x0x55b28a41dde0[NGImap4Client]> TLS started successfully.
sogod [4426]: <0x0x55b28a41dde0[NGImap4Client]> ERROR(-[NGImap4Client 
_processUnknownCommandParserException:]): catched non-IMAP4 parsing exception 
UnexpectedEndOfStream: the parsed stream ended unexpectedly
sogod [4426]: [ERROR] <0x0x55b28a777e30[NGImap4ConnectionManager]> IMAP4 login 
failed:
   host=mail.example.net, user=u...@example.net, pwd=yes
   url=imaps://user%40example@mail.example.net/?tls=YES
   base=(null)
   base-class=(null))
   = <0x0x55b28a41dde0[NGImap4Client]: login=u...@example.net(pwd) 
socket=>
sogod [4426]: [ERROR] <0x55b28a7ea850[SOGoMailAccount]:0> Could not connect 
IMAP4
sogod [4426]: |SOGo| request took 0.522964 seconds to execute



On the Dovecot side it looks just like a successful login but no IMAP
commands being sent by the client:


dovecot: imap-login: Login: user=, method=PLAIN, 
rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, mpid=8371, TLS, session=
dovecot: imap-login: Login: user=, method=PLAIN, 
rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, mpid=8373, TLS, session=
dovecot: imap(u...@example.net)<8371>: Connection closed (No 
commands sent) in=0 out=379 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 
body_count=0 body_bytes=0
dovecot: imap(u...@example.net)<8373>: Connection closed (No 
commands sent) in=0 out=379 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 
body_count=0 body_bytes=0



Any idea what could be wrong? I'm using the following IMAP server
string in sogo.conf:

   SOGoIMAPServer = "imap://mail.example.net:143/?tls=YES";


have you tried using imaps://... instead of imap:// ?



Thanks in advance,

Alex



--
Daniel Le Bray :: CRI :: Pôle Systèmes et Réseaux
daniel.le-b...@univ-lehavre.fr :: +33 (0)2 32 74 42 94
Universite Le Havre Normandie
25 rue Philippe Lebon, BP1123, 76063 Le Havre Cedex, France
==
J'accepte les emails VSRE (http://vsre.info/index_fr.html)



smime.p7s
Description: Signature cryptographique S/MIME

[SOGo] Unable to connect to Dovecot IMAP (UnexpectedEndOfStream)

2019-06-04 Thread Alexander Koch 
Hi all,

I'm trying to use Sogo (4.0.7-1 from Debian Buster) to connect to a
Dovecot (2.3.4.1 from Debian Buster) instance running on another host
via IMAP (port 143, TLS).

I'm getting the following error ('sogo.log', all debug options on):

> sogod [4426]: <0x0x55b28a41dde0[NGImap4Client]> TLS started successfully.
> sogod [4426]: <0x0x55b28a41dde0[NGImap4Client]> ERROR(-[NGImap4Client 
> _processUnknownCommandParserException:]): catched non-IMAP4 parsing exception 
> UnexpectedEndOfStream: the parsed stream ended unexpectedly
> sogod [4426]: [ERROR] <0x0x55b28a777e30[NGImap4ConnectionManager]> IMAP4 
> login failed:
>   host=mail.example.net, user=u...@example.net, pwd=yes
>   url=imaps://user%40example@mail.example.net/?tls=YES
>   base=(null)
>   base-class=(null))
>   = <0x0x55b28a41dde0[NGImap4Client]: login=u...@example.net(pwd) 
> socket=>
> sogod [4426]: [ERROR] <0x55b28a7ea850[SOGoMailAccount]:0> Could not connect 
> IMAP4
> sogod [4426]: |SOGo| request took 0.522964 seconds to execute


On the Dovecot side it looks just like a successful login but no IMAP
commands being sent by the client:

> dovecot: imap-login: Login: user=, method=PLAIN, 
> rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, mpid=8371, TLS, 
> session=
> dovecot: imap-login: Login: user=, method=PLAIN, 
> rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, mpid=8373, TLS, 
> session=
> dovecot: imap(u...@example.net)<8371>: Connection closed 
> (No commands sent) in=0 out=379 deleted=0 expunged=0 trashed=0 hdr_count=0 
> hdr_bytes=0 body_count=0 body_bytes=0
> dovecot: imap(u...@example.net)<8373>: Connection closed 
> (No commands sent) in=0 out=379 deleted=0 expunged=0 trashed=0 hdr_count=0 
> hdr_bytes=0 body_count=0 body_bytes=0


Any idea what could be wrong? I'm using the following IMAP server
string in sogo.conf:

  SOGoIMAPServer = "imap://mail.example.net:143/?tls=YES";



Thanks in advance,

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

Re: [SOGo] Anyway to work around Chinese Character in sogo.conf

2019-06-04 Thread Odhiambo Washington 
One question though - does your MTA read these characters in the
configuration?

On Tue, 4 Jun 2019 at 12:44, Odhiambo Washington  wrote:

> Maybe you need to go over the documentation again, because sometimes these
> are covered.
> My guess is that SOGo doesn't support internationalization within
> sogo.conf.
>
>
> On Fri, 31 May 2019 at 06:25, luckydog xf  wrote:
>
>> Does anyone have any idea?
>>
>> Thanks, guys.
>>
>> On Wed, May 29, 2019 at 11:58 AM luckydog xf 
>> wrote:
>>
>>> # sogo.conf
>>>
>>> {
>>> ..
>>>   baseDN = "OU=IT服务部,OU=董事会,OU=互太高专,OU=互太纺织印染集团,DC=ms,DC=com"
>>>
>>>  .
>>> }
>>>
>>> SOGo cannot startup with an error,
>>>
>>> Parsing '/etc/sogo/sogo.conf' - bad char '\U670d' at 3993
>>>
>>> Any way to work arount this error?
>>>
>>> Is it a must to use Non-Ascii code in sogo.conf?
>>>
>>> Thanks,
>>>
>>> --
>> users@sogo.nu
>> https://inverse.ca/sogo/lists
>>
>
>
> --
> Best regards,
> Odhiambo WASHINGTON,
> Nairobi,KE
> +254 7 3200 0004/+254 7 2274 3223
> "Oh, the cruft.", grep ^[^#] :-)
>


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Anyway to work around Chinese Character in sogo.conf

2019-06-04 Thread Odhiambo Washington 
Maybe you need to go over the documentation again, because sometimes these
are covered.
My guess is that SOGo doesn't support internationalization within sogo.conf.


On Fri, 31 May 2019 at 06:25, luckydog xf  wrote:

> Does anyone have any idea?
>
> Thanks, guys.
>
> On Wed, May 29, 2019 at 11:58 AM luckydog xf  wrote:
>
>> # sogo.conf
>>
>> {
>> ..
>>   baseDN = "OU=IT服务部,OU=董事会,OU=互太高专,OU=互太纺织印染集团,DC=ms,DC=com"
>>
>>  .
>> }
>>
>> SOGo cannot startup with an error,
>>
>> Parsing '/etc/sogo/sogo.conf' - bad char '\U670d' at 3993
>>
>> Any way to work arount this error?
>>
>> Is it a must to use Non-Ascii code in sogo.conf?
>>
>> Thanks,
>>
>> --
> users@sogo.nu
> https://inverse.ca/sogo/lists
>


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
-- 
users@sogo.nu
https://inverse.ca/sogo/lists