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
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
> > 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]:
> 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 =
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 =
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
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
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
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
