[Kroupware] random thoughts
Andreas Jellinghaus
kroupware@mail.kde.org
23 Nov 2002 20:31:30 +1300
Hi everyone,
here are some random thoughts looking at the kolab code.
I wonder about all these strange paths in the source?
Still I hope they are meant to be only temporary - stuff
like /var/postfix or /kolab.
But I admit i like /etc/postfix/aliases - usualy the first thing
I change on a debian system even if it is against FHS (or LSB?).
But in a LDAP powered mailsystem its unnecessary.
/var/postfix/log should be /var/log/postfix, that for sure.
/var/openldap ? *pain* debian changed all necessary paths I guess.
pid files should be in /var/run !
/kolab/bin ? /kolab/var ?
there is kolab-0.9.tar.gz and kolab-0.95.tar.gz which looks
significantly smaller. Both tar.gz files contain other tar.gz files.
Please put kolab as source in the cvs, not as tar.gz. Unlike openldap
it's new code, not imported one.
Ah, size differenz is this: the old has web.tar.gz and admin/,
the new version has only admin.tar.gz.
sockets such as the lmtp socket by cyrus should be in /var/run, too.
also i wonder: is the -a option to lmtp necessary or not? I couldn#t
figure out what it exactly does. Maybe you know?
i don't exactly understand why a mailserver might flush the ip tables.
Still there is a script to do that in kolab.
why is both configured: an lmtp socket for cyrus, and a master.cf using
the deliver command. my choice is lmtp, so the deliver is obsolete.
restricting the ftp ports to localhost: i have no idea, but i guess
proftpd can do that itself ? or using hosts.allow/deny ? a firewall
rule is certainly possible, but maybe like using big artillery to shoot
small birds?
code to create a certificate might be better than providing
certificates? We don't want people to use the provided ones,
not even for testing (i shudder everytime i see a ssl server configured
for the "Snakeoil" company).
Sure, none of this is essential or important, but fixing
it still might be nice.
Regards, Andreas