Stuart Naylor | 21 Aug 13:45 2014

CentOS 6 3.3 Public key for wallace-0.7.1-3.el6.kolab_3.3.noarch.rpm is not installed

warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID f0e9176e: NOKEY

 

 

Public key for wallace-0.7.1-3.el6.kolab_3.3.noarch.rpm is not installed

 

 

Did a

 

yum install kolab --nogpgcheck

 

Will tell you how I get on.

 

 

_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
Peter ILLETSCHKO | 21 Aug 09:39 2014
Picon

installation problem 3.3 on Ubuntu 14.04: "Release.key" missing

Hello Kolab MailList,

I tried to install the new 3.3 Release on Ubuntu 14.04.

And I was stopped at the second step:

wget http://obs.kolabsys.com/repositories/Kolab:/3.3/Ubuntu_14.04/Release.key

...failed because the file is missing.

Thanks,
Peter
Marco Betschart | 20 Aug 14:36 2014
Picon

Kolab install broken on CentOS

Dear Kolab Community!

I currently try to install Kolab on a CentOS box using the following manual:

Unfortunately installing fails since a GPG key could not be found:
Downloading Packages:
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID b4f6d430:
NOKEY
Retrieving key from
.key

Any ideas how to solve this issue?

Thanks
   Marco

Mit sonnigen Grüssen
  Marco


MANDELKIND think it!



_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
Troy Carpenter | 19 Aug 18:50 2014

Quarantine Management System

Has anyone integrated an email quarantine management system with Kolab?  Most of the open source ones I’ve found are either not up to date, or expect to handle everything email related.  What I’m looking for is something that can handle the quarantined items after Kolab has decided to quarantine.  At the least, it should provide a list of the items and allow them to be released.  At best, be a per-user system that notifies users of quarantine items, allows them to individually manage and release items, and manage white and black lists.

 

 

_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
Rick | 19 Aug 13:13 2014

disable redirecting via sieve-filter

I have users redirecting corporate emails to personal inboxes. Leaving no record on the server. 

What is the best way to go about disabling this feature. 

Thanks. Rick
_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
Thomas Baumann | 18 Aug 11:07 2014
Picon

Re: setup-kolab ldap fails in centos7: Failed to issue method call: No such file or directory

# ldapsearch -b 'dc=tiri,dc=lan' -D 'cn=Directory Manager' -w xxx 'objectclass=*'

does work well.

2014-08-18 10:59 GMT+02:00 Thomas Baumann <tom <at> tiri.li>:
Here you are - I cannot see which program is missing.
Best regards,
Thomas.

# setup-kolab -d 9 ldap
...
Confirm Kolab Service password:
2014-08-18 10:56:51,078 pykolab.setup INFO Writing out configuration to kolab.conf
2014-08-18 10:56:51,102 pykolab.setup INFO Inserting service users into LDAP.
2014-08-18 10:56:51,102 pykolab.auth DEBUG [2441]: Called for domain None
2014-08-18 10:56:51,102 pykolab.auth DEBUG [2441]: Using section tiri.lan and domain tiri.lan
2014-08-18 10:56:51,102 pykolab.auth DEBUG [2441]: Using section tiri.lan and domain tiri.lan
2014-08-18 10:56:51,102 pykolab.auth DEBUG [2441]: Connecting to Authentication backend for domain tiri.lan
2014-08-18 10:56:51,102 pykolab.auth DEBUG [2441]: Section kolab has auth_mechanism: 'ldap'
2014-08-18 10:56:51,103 pykolab.auth DEBUG [2441]: Starting LDAP...
2014-08-18 10:56:51,238 pykolab.auth DEBUG [2441]: Connecting to LDAP...
2014-08-18 10:56:51,239 pykolab.auth DEBUG [2441]: Attempting to use LDAP URI ldap://localhost:389
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.set_option
((17, 3), {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.set_option
((17, 3), {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.simple_bind
(('cn=Directory Manager', 'uCdKlKBXbS3Fyjy', None, None), {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((1, 1, -1, 0, 0, 0), {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.add_ext
(('uid=cyrus-admin,ou=Special Users,dc=tiri,dc=lan',
  [('surname', 'Administrator'),
   ('uid', 'cyrus-admin'),
   ('objectclass',
    ['top', 'person', 'inetorgperson', 'organizationalperson']),
   ('userPassword', 'OKdKoOvG0mMcvEB'),
   ('givenname', 'Cyrus'),
   ('cn', 'Cyrus Administrator')],
  None,
  None),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((2, 1, -1, 0, 0, 0), {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.add_ext
(('uid=kolab-service,ou=Special Users,dc=tiri,dc=lan',
  [('nslookthroughlimit', '-1'),
   ('surname', 'Service'),
   ('uid', 'kolab-service'),
   ('objectclass',
    ['top', 'person', 'inetorgperson', 'organizationalperson']),
   ('userPassword', 'xxxx'),
   ('nstimelimit', '-1'),
   ('nssizelimit', '-1'),
   ('nsidletimeout', '-1'),
   ('givenname', 'Kolab'),
   ('cn', 'Kolab Service')],
  None,
  None),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((3, 1, -1, 0, 0, 0), {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.add_ext
(('ou=Resources,dc=tiri,dc=lan',
  [('objectclass', ['top', 'organizationalunit']), ('ou', 'Resources')],
  None,
  None),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((4, 1, -1, 0, 0, 0), {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.add_ext
(('ou=Shared Folders,dc=tiri,dc=lan',
  [('objectclass', ['top', 'organizationalunit']), ('ou', 'Shared Folders')],
  None,
  None),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((5, 1, -1, 0, 0, 0), {})
2014-08-18 10:56:51,343 pykolab.setup INFO Writing out cn=kolab,cn=config
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.add_ext
(('cn=kolab,cn=config',
  [('objectclass', ['top', 'extensibleobject']), ('cn', 'kolab')],
  None,
  None),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((6, 1, -1, 0, 0, 0), {})
2014-08-18 10:56:51,350 pykolab.auth DEBUG [2441]: Setting entry attribute 'aci' to '(targetattr = "*") (version 3.0;acl "Kolab Services";allow (read,compare,search)(userdn = "ldap:///uid=kolab-service,ou=Special Users,dc=tiri,dc=lan");)' for 'cn=kolab,cn=config'
2014-08-18 10:56:51,350 pykolab.auth DEBUG [2441]: Entry ID: 'cn=kolab,cn=config'
2014-08-18 10:56:51,350 pykolab.auth DEBUG [2441]: Entry DN: 'cn=kolab,cn=config'
2014-08-18 10:56:51,351 pykolab.auth DEBUG [2441]: ldap search: ('cn=kolab,cn=config', 0, filterstr='(objectclass=*)', attrlist=[ 'dn' ] + ['*']
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.search_ext
(('cn=kolab,cn=config',
  0,
  '(objectclass=*)',
  ['dn', '*'],
  0,
  None,
  None,
  -1,
  0),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((7, 1, -1, 0, 0, 0), {})
2014-08-18 10:56:51,352 pykolab.auth DEBUG [2441]: Entry ID: 'cn=kolab,cn=config'
2014-08-18 10:56:51,352 pykolab.auth DEBUG [2441]: Entry DN: 'cn=kolab,cn=config'
2014-08-18 10:56:51,352 pykolab.auth DEBUG [2441]: ldap search: ('cn=kolab,cn=config', 0, filterstr='(objectclass=*)', attrlist=[ 'dn' ] + ['aci']
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.search_ext
(('cn=kolab,cn=config',
  0,
  '(objectclass=*)',
  ['dn', 'aci'],
  0,
  None,
  None,
  -1,
  0),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((8, 1, -1, 0, 0, 0), {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.modify_ext
(('cn=kolab,cn=config',
  [(0,
    'aci',
    '(targetattr = "*") (version 3.0;acl "Kolab Services";allow (read,compare,search)(userdn = "ldap:///uid=kolab-service,ou=Special Users,dc=tiri,dc=lan");)')],
  None,
  None),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((9, 1, -1, 0, 0, 0), {})
2014-08-18 10:56:51,360 pykolab.setup INFO Adding domain tiri.lan to list of domains for this deployment
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.add_ext
(('associateddomain=tiri.lan,cn=kolab,cn=config',
  [('objectclass', ['top', 'domainrelatedobject']),
   ('associateddomain',
    ['tiri.lan', 'build7.tiri.lan', 'localhost', 'localhost.localdomain']),
   ('aci',
    '(targetattr = "*") (version 3.0;acl "Read Access for tiri.lan Users";allow (read,compare,search)(userdn = "ldap:///dc=tiri,dc=lan??sub?(objectclass=*)");)')],
  None,
  None),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((10, 1, -1, 0, 0, 0), {})
2014-08-18 10:56:51,367 pykolab.setup INFO Disabling anonymous binds
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.modify_ext
(('cn=config', [(2, 'nsslapd-allow-anonymous-access', 'off')], None, None), {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((11, 1, -1, 0, 0, 0), {})
2014-08-18 10:56:51,379 pykolab.setup INFO Enabling attribute uniqueness plugin
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.modify_ext
(('cn=attribute uniqueness,cn=plugins,cn=config',
  [(2, 'nsslapd-pluginEnabled', 'on')],
  None,
  None),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((12, 1, -1, 0, 0, 0), {})
2014-08-18 10:56:51,384 pykolab.setup INFO Enabling referential integrity plugin
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.modify_ext
(('cn=referential integrity postoperation,cn=plugins,cn=config',
  [(2, 'nsslapd-pluginEnabled', 'on')],
  None,
  None),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((13, 1, -1, 0, 0, 0), {})
2014-08-18 10:56:51,390 pykolab.setup INFO Enabling and configuring account policy plugin
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.modify_ext
(('cn=Account Policy Plugin,cn=plugins,cn=config',
  [(2, 'nsslapd-pluginEnabled', 'on'),
   (0,
    'nsslapd-pluginarg0',
    'cn=config,cn=Account Policy Plugin,cn=plugins,cn=config')],
  None,
  None),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((14, 1, -1, 0, 0, 0), {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.modify_ext
(('cn=config,cn=Account Policy Plugin,cn=plugins,cn=config',
  [(2, 'alwaysrecordlogin', 'yes'),
   (0, 'stateattrname', 'lastLoginTime'),
   (0, 'altstateattrname', 'createTimestamp')],
  None,
  None),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((15, 1, -1, 0, 0, 0), {})
2014-08-18 10:56:51,474 pykolab.setup INFO Adding the kolab-admin role
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.add_ext
(('cn=kolab-admin,dc=tiri,dc=lan',
  [('objectClass',
    ['top',
     'ldapsubentry',
     'nsroledefinition',
     'nssimpleroledefinition',
     'nsmanagedroledefinition']),
   ('description', 'Kolab Administrator'),
   ('cn', 'kolab-admin')],
  None,
  None),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((16, 1, -1, 0, 0, 0), {})
2014-08-18 10:56:51,485 pykolab.setup INFO Setting access control to dc=tiri,dc=lan
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.modify_ext
(('dc=tiri,dc=lan',
  [(2,
    'aci',
    ['(targetattr = "carLicense || description || displayName || facsimileTelephoneNumber || homePhone || homePostalAddress || initials || jpegPhoto || l || labeledURI || mobile || o || pager || photo || postOfficeBox || postalAddress || postalCode || preferredDeliveryMethod || preferredLanguage || registeredAddress || roomNumber || secretary || seeAlso || st || street || telephoneNumber || telexNumber || title || userCertificate || userPassword || userSMIMECertificate || x500UniqueIdentifier || kolabDelegate || kolabInvitationPolicy || kolabAllowSMTPSender") (version 3.0; acl "Enable self write for common attributes"; allow (read,compare,search,write)(userdn = "ldap:///self");)',
     '(targetattr = "*") (version 3.0;acl "Directory Administrators Group";allow (all)(groupdn = "ldap:///cn=Directory Administrators,dc=tiri,dc=lan" or roledn = "ldap:///cn=kolab-admin,dc=tiri,dc=lan");)',
     '(targetattr="*")(version 3.0; acl "Configuration Administrators Group"; allow (all) groupdn="ldap:///cn=Configuration Administrators,ou=Groups,ou=TopologyManagement,o=NetscapeRoot";)',
     '(targetattr="*")(version 3.0; acl "Configuration Administrator"; allow (all) userdn="ldap:///uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot";)',
     '(targetattr = "*")(version 3.0; acl "SIE Group"; allow (all) groupdn = "ldap:///cn=slapd-build7,cn=389 Directory Server,cn=Server Group,cn=build7.tiri.lan,ou=tiri.lan,o=NetscapeRoot";)',
     '(targetattr != "userPassword") (version 3.0;acl "Search Access";allow (read,compare,search)(userdn = "ldap:///all");)'])],
  None,
  None),
 {})
*** <ldap.ldapobject.ReconnectLDAPObject instance at 0x28f3a28> ldap://localhost:389 - ReconnectLDAPObject.result4
((17, 1, -1, 0, 0, 0), {})

Failed to issue method call: No such file or directory




2014-08-18 10:24 GMT+02:00 Torsten Grote <torsten <at> kolab.org>:

On Monday 18 August 2014 10:01:37 Thomas Baumann wrote:
> Failed to issue method call: No such file or directory

Could you run setup kolab with -d 9 to find out what program can not be found?

Kind Regards,
Torsten

--
Torsten Grote
Kolab.org Community Manager

e: torsten <at> kolab.org
w: https://Kolab.org

pgp: 0x2175A534A4F2EFA3
_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users





_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
Thomas Baumann | 18 Aug 10:01 2014
Picon

setup-kolab ldap fails in centos7: Failed to issue method call: No such file or directory

Hello all,

when running "setup-kolab ldap" everything seems to work right, but then stops
with "Failed to issue method call: No such file or directory".

Here is the output.
How to investigate the problem?

# setup-kolab ldap

Please supply a password for the LDAP administrator user 'admin', used to login
to the graphical console of 389 Directory server.

Administrator password [xx]:
Confirm Administrator password:

Please supply a password for the LDAP Directory Manager user, which is the
administrator user you will be using to at least initially log in to the Web
Admin, and that Kolab uses to perform administrative tasks.

Directory Manager password [xx]:
Confirm Directory Manager password:

Please choose the system user and group the service should use to run under.
These should be existing, unprivileged, local system POSIX accounts with no
shell.

User [nobody]:
Group [nobody]:

This setup procedure plans to set up Kolab Groupware for the following domain
name space. This domain name is obtained from the reverse DNS entry on your
network interface. Please confirm this is the appropriate domain name space.

example.lan [Y/n]: y

The standard root dn we composed for you follows. Please confirm this is the root
dn you wish to use.

dc=example,dc=lan [Y/n]: y

Setup is now going to set up the 389 Directory Server. This may take a little
while (during which period there is no output and no progress indication).

ln -s '/usr/lib/systemd/system/dirsrv.target' '/etc/systemd/system/multi-user.target.wants/dirsrv.target'

Please supply a Cyrus Administrator password. This password is used by Kolab to
execute administrative tasks in Cyrus IMAP. You may also need the password
yourself to troubleshoot Cyrus IMAP and/or perform other administrative tasks
against Cyrus IMAP directly.

Cyrus Administrator password [xx]:
Confirm Cyrus Administrator password:

Please supply a Kolab Service account password. This account is used by various
services such as Postfix, and Roundcube, as anonymous binds to the LDAP server
will not be allowed.

Kolab Service password [xx]:
Confirm Kolab Service password:
Failed to issue method call: No such file or directory



Best regards,
Thomas.

_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
Tom Reijnders | 17 Aug 17:59 2014
Picon

Kolab on OpenSuSE 13.1 installation problem

I am trying to get Kolab 3.2 on OpenSuSE 13.1 and this is not a real 
smooth process.

I'll write up what I did when I succeed completely.

For now I have the following issue, I can't get roundcubemail to 
authenticate properly. It has to do with the saslauthd configurations as 
I find this in the /var/log/mail:

imap[29813]: SASL cannot connect to saslauthd server: No such file or 
directory

I managed to get testsaslauthd on this machine, and tried to run, and it 
fails:

#./testsaslauthd -u test -p test
0: NO "authentication failed"
#

However, after having figured out the proper unix socket:

#./testsaslauthd -u test -p test -f /var/run/saslauthd/mux
0: OK "Success."
#

So how do I configure cyrus to use /var/run/saslauthd/mux

Regards,

Tom

--

-- 
--

Tom Reijnders
TOR Informatica
Chopinlaan 27
5242HM Rosmalen
Tel: 073 5226191
Fax: 073 5226196
Jan Hofmann | 16 Aug 22:29 2014
Picon

How to whitelist a domain?

Hi all,

My kolab server is working really fine, until I wanted to register to a battle.net account today. It seems
that spam assassin is rejecting the mail directly. :(

How can I whitelist Domains and Mailadresses in Kolab?

Regards, Jan

Attachment (smime.p7s): application/pkcs7-signature, 5600 bytes
_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
dsp3 | 16 Aug 15:52 2014

Chwala upload file size

Does Kolab/Chwala have a default max upload file size or does this 
depend on php.ini? There is no option in kolab_files.inc.php and 
changing settings in php.ini doesn't produce desired results.

--

-- 
http://www.dsp3.org
info <at> dsp3.org
GPG Key: ACF0A7E6
Karol Krasňan | 16 Aug 10:27 2014
Picon

Kolab 3.2 on Debian 7.5 installation problem

Hello,
I am trying install Kolab 3.2 on Debian 7.5, but installation failed on cyrus-imapd package.
I proceeded steps according installation guide, for Debian Wheeze (http://docs.kolab.org/installation-guide/debian.html). And after aptitude install kolab starts it fails with this error:

Unpacking cyrus-imapd (from .../cyrus-imapd_2.5~dev2014011701-0~kolab1_i386.deb) ...
Processing triggers for man-db ...
Setting up cyrus-imapd (2.5~dev2014011701-0~kolab1) ...
Creating/updating cyrus user account...
The user `cyrus' is already a member of `sasl'.
The user `cyrus' is already a member of `ssl-cert'.
Creating/updating cyrus control directories in /var/lib/imap...
Creating/updating partition spool /var/spool/imap...
Trying to optimize Cyrus partitions, edit /etc/default/cyrus-imapd to disable...
Setting attributes to -S -j for  /var/lib/imap...
Setting attributes to -S -j for  /var/spool/imap...
dpkg: error processing cyrus-imapd (--configure):
 subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
 cyrus-imapd

I tried find some solution, but without success.

Thank you very much for help.
Karol
_______________________________________________
users mailing list
users <at> lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users

Gmane