Hi All,
Ive done some work on the mandrake rpms for kolab. and nearly have them ready
to release to the world. Just wanted to ask if i should bundle in the
configuration for amavis-new and clamav so that someone installing kolab
would have a working mailserver with spam and antivirus scanning out of the
box.
and if i should replace /etc/sysconfig/saslauthd as it needs modification.
my thinking was this the way kolab runs it keeps the config files
in /etc/kolab and runs some macros over them on service start. and if
theres changes put the new config in place. i should just add a template for
the saslauthd file
i still need to switch over the ftp deamon from proftpd to vsftpd and tidy up
some config files but right now after making one chnage to the kolab.schema
file enabling ldap for sasl authentication and
running /usr/sbin/kolab_bootstrap -b the kolab server works
i dont know if the ftp deamon is really necessary as it is only used for
legacy clients. but i should do it so kolab is feature complete.
So why will gnome users want kolab. well at the least it provides an easy way
to configure cyrus-imapd and get a working setup with ldap authentication
and kde users will be able to easily setup kontact to run with it.
Dennis
Show replies by date