Discussion:
Calendar and contacts not showing up in Kontact
Johannes Ranke
2017-02-10 09:30:52 UTC
Permalink
Hi,

I am migrating an existing kolab installation to a different virtual server and
have done a fresh install of Kolab 16 on Debian jessie.

Setting it up worked fine and I have created a regular Kolab user. The command

kolab lm

lists all the folders I could dream of, including ***@domain.org and
***@domain.org.

However, I can not get kontact on the client side to use calendar and contact
from the new server.

When I configure a kolab groupware account for the new server, I only see the
email folders (Inbox, Archives, ...). Korganizer and kaddressbook have no
entries for the new account.

I have tried with kontact 4.14.1 from Debian jessie, kontact 5.x from Ubuntu
16.10 and current kontact from KDE neon, so the problem appears to be on the
server side.

Any hints?

Johannes

P.S.: Maybe it is relevant that in addition to the new server
kolab.domain.org, my old kolab 3.4 installation is still running on
{www,smtp,imap,mail}.domain.org. Is it possible that this old installation
gets in the way, i.e. kontact tries to talk that old installation, although I
specify the new server kolab.domain.org?
Johannes Ranke
2017-02-10 10:01:36 UTC
Permalink
Hi again,

Possibly, these folders are being suppressed by guam. According to its
documentation, it suppresses groupware folders for clients that do not
advertise themselves with a "user agent" string containing the substring
"/Kolab".

https://kolabsys.com/about/guam/troubleshooting.html

I have not found out how to check the user agent string for the various
versions of kontact I have tried. I would think that current versions such as
shipped with KDE neon should be compatible with kolab 16. I will try to check.

Johannes
Post by Johannes Ranke
Hi,
I am migrating an existing kolab installation to a different virtual server
and have done a fresh install of Kolab 16 on Debian jessie.
Setting it up worked fine and I have created a regular Kolab user. The command
kolab lm
However, I can not get kontact on the client side to use calendar and
contact from the new server.
When I configure a kolab groupware account for the new server, I only see
the email folders (Inbox, Archives, ...). Korganizer and kaddressbook have
no entries for the new account.
I have tried with kontact 4.14.1 from Debian jessie, kontact 5.x from Ubuntu
16.10 and current kontact from KDE neon, so the problem appears to be on
the server side.
Any hints?
Johannes
P.S.: Maybe it is relevant that in addition to the new server
kolab.domain.org, my old kolab 3.4 installation is still running on
{www,smtp,imap,mail}.domain.org. Is it possible that this old installation
gets in the way, i.e. kontact tries to talk that old installation, although
I specify the new server kolab.domain.org?
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users
--
PD Dr. Johannes Ranke
Wissenschaftlicher Berater

Kronacher Str. 12
79639 Grenzach-Wyhlen
Germany
+49 7624 8099027
http://jrwb.de
USt-IdNr.: DE292883940
Johannes Ranke
2017-02-10 12:01:50 UTC
Permalink
OK, it seems to me that guam is responsible indeed. I have reported this here:

https://git.kolab.org/T2241

I hope I did not overlook anything. Cheers,

Johannes
Post by Johannes Ranke
Hi again,
Possibly, these folders are being suppressed by guam. According to its
documentation, it suppresses groupware folders for clients that do not
advertise themselves with a "user agent" string containing the substring
"/Kolab".
https://kolabsys.com/about/guam/troubleshooting.html
I have not found out how to check the user agent string for the various
versions of kontact I have tried. I would think that current versions such
as shipped with KDE neon should be compatible with kolab 16. I will try to
check.
Johannes
Post by Johannes Ranke
Hi,
I am migrating an existing kolab installation to a different virtual server
and have done a fresh install of Kolab 16 on Debian jessie.
Setting it up worked fine and I have created a regular Kolab user. The command
kolab lm
However, I can not get kontact on the client side to use calendar and
contact from the new server.
When I configure a kolab groupware account for the new server, I only see
the email folders (Inbox, Archives, ...). Korganizer and kaddressbook have
no entries for the new account.
I have tried with kontact 4.14.1 from Debian jessie, kontact 5.x from
Ubuntu 16.10 and current kontact from KDE neon, so the problem appears to
be on the server side.
Any hints?
Johannes
P.S.: Maybe it is relevant that in addition to the new server
kolab.domain.org, my old kolab 3.4 installation is still running on
{www,smtp,imap,mail}.domain.org. Is it possible that this old installation
gets in the way, i.e. kontact tries to talk that old installation, although
I specify the new server kolab.domain.org?
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users
--
PD Dr. Johannes Ranke
Wissenschaftlicher Berater

Kronacher Str. 12
79639 Grenzach-Wyhlen
Germany
+49 7624 8099027
http://jrwb.de
USt-IdNr.: DE292883940
Johannes Ranke
2017-02-10 13:43:17 UTC
Permalink
As a workaround, I have found out how to disable the groupware folder
filtering:

--- sys.config.orig 2017-02-10 11:30:09.075115930 +0100
+++ sys.config 2017-02-10 14:38:23.877021226 +0100
@@ -20,9 +20,7 @@
{ port, 143 },
{ imap_server, imaps },
{
- rules, [
- { filter_groupware, [] }
- ]
+ rules, []
},
{
tls_config, [
@@ -37,9 +35,7 @@
{ implicit_tls, true },
{ imap_server, imaps },
{
- rules, [
- { filter_groupware, [] }
- ]
+ rules, []
},
{
tls_config, [

Apply this to /etc/guam/sys.config and do

service guam restart

and then all folders will show up in kontact!

Cheers,

Johannes
Post by Johannes Ranke
https://git.kolab.org/T2241
I hope I did not overlook anything. Cheers,
Johannes
Post by Johannes Ranke
Hi again,
Possibly, these folders are being suppressed by guam. According to its
documentation, it suppresses groupware folders for clients that do not
advertise themselves with a "user agent" string containing the substring
"/Kolab".
https://kolabsys.com/about/guam/troubleshooting.html
I have not found out how to check the user agent string for the various
versions of kontact I have tried. I would think that current versions such
as shipped with KDE neon should be compatible with kolab 16. I will try to
check.
Johannes
Post by Johannes Ranke
Hi,
I am migrating an existing kolab installation to a different virtual server
and have done a fresh install of Kolab 16 on Debian jessie.
Setting it up worked fine and I have created a regular Kolab user.
The
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
command
kolab lm
However, I can not get kontact on the client side to use calendar and
contact from the new server.
When I configure a kolab groupware account for the new server, I
only
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
see
the email folders (Inbox, Archives, ...). Korganizer and kaddressbook have
no entries for the new account.
I have tried with kontact 4.14.1 from Debian jessie, kontact 5.x from
Ubuntu 16.10 and current kontact from KDE neon, so the problem
appears
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
to
be on the server side.
Any hints?
Johannes
P.S.: Maybe it is relevant that in addition to the new server
kolab.domain.org, my old kolab 3.4 installation is still running on
{www,smtp,imap,mail}.domain.org. Is it possible that this old installation
gets in the way, i.e. kontact tries to talk that old installation, although
I specify the new server kolab.domain.org?
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users
--
PD Dr. Johannes Ranke
Wissenschaftlicher Berater

Kronacher Str. 12
79639 Grenzach-Wyhlen
Germany
+49 7624 8099027
http://jrwb.de
USt-IdNr.: DE292883940
m***@chrisfleming.org
2017-02-10 21:41:30 UTC
Permalink
Personally I've found that Guam isn't stable enough for production use
and have completely disabled it.

Cheers
Chris
Post by Johannes Ranke
As a workaround, I have found out how to disable the groupware folder
 
--- sys.config.orig 2017-02-10 11:30:09.075115930 +0100
+++ sys.config 2017-02-10 14:38:23.877021226 +0100
@@ -20,9 +20,7 @@
{ port, 143 },
{ imap_server, imaps },
{
- rules, [
- { filter_groupware, [] }
- ]
+ rules, []
},
{
tls_config, [
@@ -37,9 +35,7 @@
{ implicit_tls, true },
{ imap_server, imaps },
{
- rules, [
- { filter_groupware, [] }
- ]
+ rules, []
},
{
tls_config, [
 
Apply this to /etc/guam/sys.config and do
 
service guam restart
 
and then all folders will show up in kontact!
 
Cheers,
 
Johannes
 
 
Post by Johannes Ranke
OK, it seems to me that guam is responsible indeed. I have reported this
https://git.kolab.org/T2241
I hope I did not overlook anything. Cheers,
Johannes
Post by Johannes Ranke
Hi again,
Possibly, these folders are being suppressed by guam. According to its
documentation, it suppresses groupware folders for clients that do not
advertise themselves with a "user agent" string containing the
substring
Post by Johannes Ranke
Post by Johannes Ranke
"/Kolab".
https://kolabsys.com/about/guam/troubleshooting.html
I have not found out how to check the user agent string for the
various
Post by Johannes Ranke
Post by Johannes Ranke
versions of kontact I have tried. I would think that current versions
such
Post by Johannes Ranke
Post by Johannes Ranke
as shipped with KDE neon should be compatible with kolab 16. I will
try to
Post by Johannes Ranke
Post by Johannes Ranke
check.
Johannes
Post by Johannes Ranke
Hi,
I am migrating an existing kolab installation to a different virtual
server
and have done a fresh install of Kolab 16 on Debian jessie.
Setting it up worked fine and I have created a regular Kolab user.
The
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
command
kolab lm
lists all the folders I could dream of, including
and
However, I can not get kontact on the client side to use calendar
and
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
contact from the new server.
When I configure a kolab groupware account for the new server, I
only
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
see
the email folders (Inbox, Archives, ...). Korganizer and
kaddressbook
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
have
no entries for the new account.
I have tried with kontact 4.14.1 from Debian jessie, kontact 5.x
from
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
Ubuntu 16.10 and current kontact from KDE neon, so the problem
appears
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
to
be on the server side.
Any hints?
Johannes
P.S.: Maybe it is relevant that in addition to the new server
kolab.domain.org, my old kolab 3.4 installation is still running on
{www,smtp,imap,mail}.domain.org. Is it possible that this old
installation
gets in the way, i.e. kontact tries to talk that old installation,
although
I specify the new server kolab.domain.org?
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users
--
PD Dr. Johannes Ranke
Wissenschaftlicher Berater
 
Kronacher Str. 12
79639 Grenzach-Wyhlen
Germany
+49 7624 8099027
http://jrwb.de
USt-IdNr.: DE292883940
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users
Johannes Ranke
2017-02-11 08:51:29 UTC
Permalink
Interesting - how did you do that?

Johannes
Post by m***@chrisfleming.org
Personally I've found that Guam isn't stable enough for production use
and have completely disabled it.
Cheers
Chris
Post by Johannes Ranke
As a workaround, I have found out how to disable the groupware folder
--- sys.config.orig 2017-02-10 11:30:09.075115930 +0100
+++ sys.config 2017-02-10 14:38:23.877021226 +0100
@@ -20,9 +20,7 @@
{ port, 143 },
{ imap_server, imaps },
{
- rules, [
- { filter_groupware, [] }
- ]
+ rules, []
},
{
tls_config, [
@@ -37,9 +35,7 @@
{ implicit_tls, true },
{ imap_server, imaps },
{
- rules, [
- { filter_groupware, [] }
- ]
+ rules, []
},
{
tls_config, [
Apply this to /etc/guam/sys.config and do
service guam restart
and then all folders will show up in kontact!
Cheers,
Johannes
Post by Johannes Ranke
OK, it seems to me that guam is responsible indeed. I have reported this
https://git.kolab.org/T2241
I hope I did not overlook anything. Cheers,
Johannes
Post by Johannes Ranke
Hi again,
Possibly, these folders are being suppressed by guam. According to its
documentation, it suppresses groupware folders for clients that do not
advertise themselves with a "user agent" string containing the
substring
Post by Johannes Ranke
Post by Johannes Ranke
"/Kolab".
https://kolabsys.com/about/guam/troubleshooting.html
I have not found out how to check the user agent string for the
various
Post by Johannes Ranke
Post by Johannes Ranke
versions of kontact I have tried. I would think that current versions
such
Post by Johannes Ranke
Post by Johannes Ranke
as shipped with KDE neon should be compatible with kolab 16. I will
try to
Post by Johannes Ranke
Post by Johannes Ranke
check.
Johannes
Post by Johannes Ranke
Hi,
I am migrating an existing kolab installation to a different virtual
server
and have done a fresh install of Kolab 16 on Debian jessie.
Setting it up worked fine and I have created a regular Kolab user.
The
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
command
kolab lm
lists all the folders I could dream of, including
and
However, I can not get kontact on the client side to use calendar
and
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
contact from the new server.
When I configure a kolab groupware account for the new server, I
only
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
see
the email folders (Inbox, Archives, ...). Korganizer and
kaddressbook
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
have
no entries for the new account.
I have tried with kontact 4.14.1 from Debian jessie, kontact 5.x
from
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
Ubuntu 16.10 and current kontact from KDE neon, so the problem
appears
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
to
be on the server side.
Any hints?
Johannes
P.S.: Maybe it is relevant that in addition to the new server
kolab.domain.org, my old kolab 3.4 installation is still running on
{www,smtp,imap,mail}.domain.org. Is it possible that this old
installation
gets in the way, i.e. kontact tries to talk that old installation,
although
I specify the new server kolab.domain.org?
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users
--
PD Dr. Johannes Ranke
Wissenschaftlicher Berater
Kronacher Str. 12
79639 Grenzach-Wyhlen
Germany
+49 7624 8099027
http://jrwb.de
USt-IdNr.: DE292883940
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users
--
PD Dr. Johannes Ranke
Wissenschaftlicher Berater

Kronacher Str. 12
79639 Grenzach-Wyhlen
Germany
+49 7624 8099027
http://jrwb.de
USt-IdNr.: DE292883940
m***@chrisfleming.org
2017-02-11 09:53:14 UTC
Permalink
In /etc/cyrus.conf I set the imapd to listen on the standard ports:

SERVICES {
imap cmd="imapd" listen="imap" prefork=5
imaps cmd="imapd -s" listen="imaps" prefork=1

sieve cmd="timsieved" listen="sieve" prefork=0

ptloader cmd="ptloader" listen="/var/lib/imap/ptclient/ptsock" prefork=0

lmtpunix cmd="lmtpd" listen="/var/lib/imap/socket/lmtp" prefork=1

notify cmd="notifyd" listen="/var/lib/imap/socket/notify" proto="udp" prefork=1
}

I then stoped guam and restarted cyrus imapd:

systemctl stop guam
systemctl restart cyrus-imapd
systemctl disable guam

before this guam was crashing for me all the time, and I was having trouble with
some clients such as the gmail imap client on Android. I'll give it another run
possibly on an alternative port on the next kolab release.

Cheers
Chris
Post by Johannes Ranke
Interesting - how did you do that?
Johannes
Post by m***@chrisfleming.org
Personally I've found that Guam isn't stable enough for production use
and have completely disabled it.
Cheers
Chris
Post by Johannes Ranke
As a workaround, I have found out how to disable the groupware folder
--- sys.config.orig 2017-02-10 11:30:09.075115930 +0100
+++ sys.config 2017-02-10 14:38:23.877021226 +0100
@@ -20,9 +20,7 @@
{ port, 143 },
{ imap_server, imaps },
{
- rules, [
- { filter_groupware, [] }
- ]
+ rules, []
},
{
tls_config, [
@@ -37,9 +35,7 @@
{ implicit_tls, true },
{ imap_server, imaps },
{
- rules, [
- { filter_groupware, [] }
- ]
+ rules, []
},
{
tls_config, [
Apply this to /etc/guam/sys.config and do
service guam restart
and then all folders will show up in kontact!
Cheers,
Johannes
Post by Johannes Ranke
OK, it seems to me that guam is responsible indeed. I have reported this
https://git.kolab.org/T2241
I hope I did not overlook anything. Cheers,
Johannes
Post by Johannes Ranke
Hi again,
Possibly, these folders are being suppressed by guam. According to
its
documentation, it suppresses groupware folders for clients that do
not
advertise themselves with a "user agent" string containing the
substring
Post by Johannes Ranke
Post by Johannes Ranke
"/Kolab".
https://kolabsys.com/about/guam/troubleshooting.html
I have not found out how to check the user agent string for the
various
Post by Johannes Ranke
Post by Johannes Ranke
versions of kontact I have tried. I would think that current versions
such
Post by Johannes Ranke
Post by Johannes Ranke
as shipped with KDE neon should be compatible with kolab 16. I will
try to
Post by Johannes Ranke
Post by Johannes Ranke
check.
Johannes
Post by Johannes Ranke
Hi,
I am migrating an existing kolab installation to a different
virtual
server
and have done a fresh install of Kolab 16 on Debian jessie.
Setting it up worked fine and I have created a regular Kolab
user.
The
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
command
kolab lm
lists all the folders I could dream of, including
and
However, I can not get kontact on the client side to use calendar
and
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
contact from the new server.
When I configure a kolab groupware account for the new server, I
only
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
see
the email folders (Inbox, Archives, ...). Korganizer and
kaddressbook
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
have
no entries for the new account.
I have tried with kontact 4.14.1 from Debian jessie, kontact 5.x
from
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
Ubuntu 16.10 and current kontact from KDE neon, so the problem
appears
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
to
be on the server side.
Any hints?
Johannes
P.S.: Maybe it is relevant that in addition to the new server
kolab.domain.org, my old kolab 3.4 installation is still running
on
{www,smtp,imap,mail}.domain.org. Is it possible that this old
installation
gets in the way, i.e. kontact tries to talk that old
installation,
although
I specify the new server kolab.domain.org?
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users
--
PD Dr. Johannes Ranke
Wissenschaftlicher Berater
Kronacher Str. 12
79639 Grenzach-Wyhlen
Germany
+49 7624 8099027
http://jrwb.de
USt-IdNr.: DE292883940
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users
--
PD Dr. Johannes Ranke
Wissenschaftlicher Berater
Kronacher Str. 12
79639 Grenzach-Wyhlen
Germany
+49 7624 8099027
http://jrwb.de
USt-IdNr.: DE292883940
Johannes Ranke
2017-02-11 11:11:17 UTC
Permalink
Chris,

many thanks! This also solved the issue I had that my clients did not see the
certificate I configured in /etc/imapd.conf, because guam was sending the
original, self-signed certificate.

As a side not, replacing the path to the self-signed certificate specified in
/etc/guam/sys.config by my letsencrypt certificate made guam crash:

https://git.kolab.org/T2244

So I now disabled guam as described below (except that in kolab 16 there is
only imaps, no plain imap any more) and imaps is working nicely, without
clients having to accept a self-signed certificate.

Thanks again!

Johannes
Post by m***@chrisfleming.org
SERVICES {
imap cmd="imapd" listen="imap" prefork=5
imaps cmd="imapd -s" listen="imaps" prefork=1
sieve cmd="timsieved" listen="sieve"
prefork=0
ptloader cmd="ptloader" listen="/var/lib/imap/ptclient/ptsock"
prefork=0
lmtpunix cmd="lmtpd" listen="/var/lib/imap/socket/lmtp"
prefork=1
notify cmd="notifyd" listen="/var/lib/imap/socket/notify"
proto="udp" prefork=1 }
systemctl stop guam
systemctl restart cyrus-imapd
systemctl disable guam
before this guam was crashing for me all the time, and I was having trouble
with some clients such as the gmail imap client on Android. I'll give it
another run possibly on an alternative port on the next kolab release.
Cheers
Chris
Post by Johannes Ranke
Interesting - how did you do that?
Johannes
Post by m***@chrisfleming.org
Personally I've found that Guam isn't stable enough for production use
and have completely disabled it.
Cheers
Chris
Post by Johannes Ranke
As a workaround, I have found out how to disable the groupware folder
--- sys.config.orig 2017-02-10 11:30:09.075115930 +0100
+++ sys.config 2017-02-10 14:38:23.877021226 +0100
@@ -20,9 +20,7 @@
{ port, 143 },
{ imap_server, imaps },
{
- rules, [
- { filter_groupware, [] }
- ]
+ rules, []
},
{
tls_config, [
@@ -37,9 +35,7 @@
{ implicit_tls, true },
{ imap_server, imaps },
{
- rules, [
- { filter_groupware, [] }
- ]
+ rules, []
},
{
tls_config, [
Apply this to /etc/guam/sys.config and do
service guam restart
and then all folders will show up in kontact!
Cheers,
Johannes
Post by Johannes Ranke
OK, it seems to me that guam is responsible indeed. I have
reported
this
https://git.kolab.org/T2241
I hope I did not overlook anything. Cheers,
Johannes
Post by Johannes Ranke
Hi again,
Possibly, these folders are being suppressed by guam. According
to
its
documentation, it suppresses groupware folders for clients that
do
not
advertise themselves with a "user agent" string containing the
substring
Post by Johannes Ranke
Post by Johannes Ranke
"/Kolab".
https://kolabsys.com/about/guam/troubleshooting.html
I have not found out how to check the user agent string for the
various
Post by Johannes Ranke
Post by Johannes Ranke
versions of kontact I have tried. I would think that current
versions
such
Post by Johannes Ranke
Post by Johannes Ranke
as shipped with KDE neon should be compatible with kolab 16. I
will
try to
Post by Johannes Ranke
Post by Johannes Ranke
check.
Johannes
Post by Johannes Ranke
Hi,
I am migrating an existing kolab installation to a different
virtual
server
and have done a fresh install of Kolab 16 on Debian jessie.
Setting it up worked fine and I have created a regular Kolab
user.
The
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
command
kolab lm
lists all the folders I could dream of, including
and
However, I can not get kontact on the client side to use
calendar
and
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
contact from the new server.
When I configure a kolab groupware account for the new
server, I
only
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
see
the email folders (Inbox, Archives, ...). Korganizer and
kaddressbook
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
have
no entries for the new account.
I have tried with kontact 4.14.1 from Debian jessie, kontact
5.x
from
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
Ubuntu 16.10 and current kontact from KDE neon, so the
problem
appears
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
to
be on the server side.
Any hints?
Johannes
P.S.: Maybe it is relevant that in addition to the new server
kolab.domain.org, my old kolab 3.4 installation is still
running
on
{www,smtp,imap,mail}.domain.org. Is it possible that this old
installation
gets in the way, i.e. kontact tries to talk that old
installation,
although
I specify the new server kolab.domain.org?
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users
--
PD Dr. Johannes Ranke
Wissenschaftlicher Berater
Kronacher Str. 12
79639 Grenzach-Wyhlen
Germany
+49 7624 8099027
http://jrwb.de
USt-IdNr.: DE292883940
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users
--
PD Dr. Johannes Ranke
Wissenschaftlicher Berater

Kronacher Str. 12
79639 Grenzach-Wyhlen
Germany
+49 7624 8099027
http://jrwb.de
USt-IdNr.: DE292883940
m***@chrisfleming.org
2017-02-11 22:14:08 UTC
Permalink
Post by Johannes Ranke
Chris,
many thanks! This also solved the issue I had that my clients did not see the
certificate I configured in /etc/imapd.conf, because guam was sending the
original, self-signed certificate.
As a side not, replacing the path to the self-signed certificate specified in
https://git.kolab.org/T2244
So I now disabled guam as described below (except that in kolab 16 there is
only imaps, no plain imap any more) and imaps is working nicely, without
clients having to accept a self-signed certificate.
I did manage to configure guam to use the certificates. This worked for
some clients:

For reference the listener was set up as followes:

imaps, [
{ port, 993 },
{ implicit_tls, true },
{ imap_server, imaps },
{
rules, [
{ filter_groupware, [] }
]
},
{
tls_config, [
{ certfile, "/etc/letsencrypt/live/<host>/cert.pem"},
{ keyfile, "/etc/letsencrypt/live/<host>/privkey.pem"},
{ cacertfile, "/etc/letsencrypt/live/<host>/chain.pem"}
]
}
]

Cheers
Chris
Post by Johannes Ranke
Post by m***@chrisfleming.org
SERVICES {
imap cmd="imapd" listen="imap" prefork=5
imaps cmd="imapd -s" listen="imaps" prefork=1
sieve cmd="timsieved" listen="sieve"
prefork=0
ptloader cmd="ptloader" listen="/var/lib/imap/ptclient/ptsock"
prefork=0
lmtpunix cmd="lmtpd" listen="/var/lib/imap/socket/lmtp"
prefork=1
notify cmd="notifyd" listen="/var/lib/imap/socket/notify"
proto="udp" prefork=1 }
systemctl stop guam
systemctl restart cyrus-imapd
systemctl disable guam
before this guam was crashing for me all the time, and I was having trouble
with some clients such as the gmail imap client on Android. I'll give it
another run possibly on an alternative port on the next kolab release.
Cheers
Chris
Post by Johannes Ranke
Interesting - how did you do that?
Johannes
Post by m***@chrisfleming.org
Personally I've found that Guam isn't stable enough for production use
and have completely disabled it.
Cheers
Chris
Post by Johannes Ranke
As a workaround, I have found out how to disable the groupware folder
--- sys.config.orig 2017-02-10 11:30:09.075115930 +0100
+++ sys.config 2017-02-10 14:38:23.877021226 +0100
@@ -20,9 +20,7 @@
{ port, 143 },
{ imap_server, imaps },
{
- rules, [
- { filter_groupware, [] }
- ]
+ rules, []
},
{
tls_config, [
@@ -37,9 +35,7 @@
{ implicit_tls, true },
{ imap_server, imaps },
{
- rules, [
- { filter_groupware, [] }
- ]
+ rules, []
},
{
tls_config, [
Apply this to /etc/guam/sys.config and do
service guam restart
and then all folders will show up in kontact!
Cheers,
Johannes
Post by Johannes Ranke
OK, it seems to me that guam is responsible indeed. I have
reported
this
https://git.kolab.org/T2241
I hope I did not overlook anything. Cheers,
Johannes
Post by Johannes Ranke
Hi again,
Possibly, these folders are being suppressed by guam. According
to
its
documentation, it suppresses groupware folders for clients that
do
not
advertise themselves with a "user agent" string containing the
substring
Post by Johannes Ranke
Post by Johannes Ranke
"/Kolab".
https://kolabsys.com/about/guam/troubleshooting.html
I have not found out how to check the user agent string for the
various
Post by Johannes Ranke
Post by Johannes Ranke
versions of kontact I have tried. I would think that current
versions
such
Post by Johannes Ranke
Post by Johannes Ranke
as shipped with KDE neon should be compatible with kolab 16. I
will
try to
Post by Johannes Ranke
Post by Johannes Ranke
check.
Johannes
Post by Johannes Ranke
Hi,
I am migrating an existing kolab installation to a different
virtual
server
and have done a fresh install of Kolab 16 on Debian jessie.
Setting it up worked fine and I have created a regular Kolab
user.
The
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
command
kolab lm
lists all the folders I could dream of, including
and
However, I can not get kontact on the client side to use
calendar
and
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
contact from the new server.
When I configure a kolab groupware account for the new
server, I
only
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
see
the email folders (Inbox, Archives, ...). Korganizer and
kaddressbook
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
have
no entries for the new account.
I have tried with kontact 4.14.1 from Debian jessie, kontact
5.x
from
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
Ubuntu 16.10 and current kontact from KDE neon, so the
problem
appears
Post by Johannes Ranke
Post by Johannes Ranke
Post by Johannes Ranke
to
be on the server side.
Any hints?
Johannes
P.S.: Maybe it is relevant that in addition to the new server
kolab.domain.org, my old kolab 3.4 installation is still
running
on
{www,smtp,imap,mail}.domain.org. Is it possible that this old
installation
gets in the way, i.e. kontact tries to talk that old
installation,
although
I specify the new server kolab.domain.org?
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users
--
PD Dr. Johannes Ranke
Wissenschaftlicher Berater
Kronacher Str. 12
79639 Grenzach-Wyhlen
Germany
+49 7624 8099027
http://jrwb.de
USt-IdNr.: DE292883940
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users
--
PD Dr. Johannes Ranke
Wissenschaftlicher Berater
Kronacher Str. 12
79639 Grenzach-Wyhlen
Germany
+49 7624 8099027
http://jrwb.de
USt-IdNr.: DE292883940
Loading...