[Kolab-devel] Cyrus didn't answer on port 993, SSL missing_

[Thomas Spuhler]

On Saturday, May 11, 2013 10:51:03 AM Jeroen van Meeuwen (Kolab Systems) wrote:
> On 2013-05-11 13:32, Richard wrote:
> > Hi Ruediger,
> > 
> > Op zaterdag 11 mei 2013 13:52:38 schreef Ruediger Goetz:
> >> Hello
> >> 
> >> Thanks for your help. I followed
> >> http://docs.kolab.org/de-DE/Kolab_Groupware/3.0/html-single/Community_In
> >> sta llation_Guide/index.html where nothing about kolab-prep-setup is
> >> found.
> > 
> > That is because Community_Installation_Guide is a general guide.
> > kolab-prep-
> > setup is especially created to support kolab on openSUSE.  It makes
> > changes
> > openSUSE related, that are needed before Kolab is installed on
> > openSUSE.
> 
> Is anyone interested in making the upstream setup-kolab be able to make
> such platform specific changes, for as far as they are platform specific
> (generating a CA / self-signed cert is not platform specific), if not
> simply integrating in to upstream documentation, the recommended
> additional steps that need to be taken for the use of openSUSE as a
> platform?
> 
> Kind regards,
> 
> Jeroen van Meeuwen

Jeroen:
It may be easier when the distribution add the specifics.
I would appreciate if you, or somebody else from kolab could help on some of the issues.
I think also of cleaning up some of the packages such as the /etc/roundcube/main.inc.php
where we have some none-existent plugins and some are called twice.

Doing the automatic start of dirsrv at instance.sevice

We the packagers in return help on finding bugs to compensate for kolab's help.

For example, I can provide the above file that has been cleaned.

-- 
Best regards
Thomas Spuhler
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20130511/1d9a04ef/attachment.sig>