Kolab setup for production

hi all,

I'd like to ask those of you, who already have kolab in
production: is 
there anything to take care of after installing kolab
(setting up 
firewall- and ssh-rules, etc.) and before going
"live" with the new 
system? Are there any security considerations or suggestions
that one 
should follow?

Thanks in advance!

cheers,
Balazs

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Balazs asks a good question; I'll be very interested in the
answer for 
my system as well.
Also, what about spamassassin?  On my home system, it
appears to be 
filtering out my a.word.a.day mailing.  I even turned off
Amavis e-mail 
scanning on the services page and still am not getting this
innocuous 
mailing.  Before I roll this out in our business
environment, I really 
need to understand how to make sure the right stuff is
getting thru.
--Paul

Balazs Bezeczky wrote:
> hi all,
>
> I'd like to ask those of you, who already have kolab in
production: is 
> there anything to take care of after installing kolab
(setting up 
> firewall- and ssh-rules, etc.) and before going
"live" with the new 
> system? Are there any security considerations or
suggestions that one 
> should follow?
>
> Thanks in advance!
>
> cheers,
> Balazs
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users
>
>   

-- 
Paul Douglas Franklin
Computer Manager, Union Gospel Mission of Yakima,
Washington
Husband of Danette
Father of 12

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Try to backup and restore all and parts of your server.


On 6/18/07, Balazs Bezeczky <e9825128student.tuwien.ac.at> wrote:
> hi all,
>
> I'd like to ask those of you, who already have kolab in
production: is
> there anything to take care of after installing kolab
(setting up
> firewall- and ssh-rules, etc.) and before going
"live" with the new
> system? Are there any security considerations or
suggestions that one
> should follow?
>
> Thanks in advance!
>
> cheers,
> Balazs
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users
>


-- 
--
Alain Spineux
aspineux gmail com
May the sources be with you

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Balazs Bezeczky <e9825128student.tuwien.ac.at>
writes:

> hi all,
>
> I'd like to ask those of you, who already have kolab in
production: is 
> there anything to take care of after installing kolab
(setting up 
> firewall- and ssh-rules, etc.) and before going
"live" with the new 
> system? Are there any security considerations or
suggestions that one 
> should follow?
>
> Thanks in advance!

This is a complex question that really depends on the
environment you
use Kolab for. For small sized system I'd consider the
security of the
server good enough. Some parts can be modified over the
webadmin
frontend. You should turn off IMAP services that you do not
need for
example.

If you have systems with several hundred users you should
probably
take care to secure the server to a higher degree. You could
for
example split the services of the server like a dedicated
LDAP server
or a seperate spam box. 

Cheers,

Gunnar

-- 
____ http://www.pardus.de
_________________ http://gunnarwrobel.de _

    >> Mail at ease - Rent a kolab groupware server at
prdus <<

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Paul Douglas Franklin <pdfyugm.org> writes:

> Balazs asks a good question; I'll be very interested in
the answer for 
> my system as well.
> Also, what about spamassassin?  On my home system, it
appears to be 
> filtering out my a.word.a.day mailing.  I even turned
off Amavis e-mail 
> scanning on the services page and still am not getting
this innocuous 
> mailing.  Before I roll this out in our business
environment, I really 
> need to understand how to make sure the right stuff is
getting thru.
> --Paul

Spamassassin is a *VERY* configurable system. And you'll
always need
to be on guard concerning changes. If you have false
positives you'll
definitely need to check what causes the high scores. The
scores
should usually be available in the email headers.

Cheers,

Gunnar

-- 
____ http://www.pardus.de
_________________ http://gunnarwrobel.de _

    >> Mail at ease - Rent a kolab groupware server at
prdus <<

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users