Transitioning mail servers

[Ger Apeldoorn]

As kolab is so self-contained, wouldnt it be possible to copy the 
entire /kolab directory and the /etc/init.d/kolab script?

Just a thought, but I'm curious..

Ger.

Op dinsdag 26 september 2006 04:28, schreef Bradley Alexander:
> I have been running Kolab for the last four years on a Toshiba Tecra
> 8100 with 256 MB of RAM. I don't know whether its getting long in the
> tooth, or whether there is a hardware problem, but the machine seems to
> be letting a large amount of spam through to my inbox...In addition, the
> load average goes crazy when a lot of mail comes through (10-20) and the
> machine is rendered unusable until it clears.
>
> I have another box I can use, my part time video processing box, dual
> PIII/966 with 2GB of RAM.
>
> My question is what is the best way to transition email to the new
> server? Set Kolab up on the second box, then transfer the entire mail
> store over? is here a way to automate this and have a smooth transition
> from one server to the other?
>
> Also, are there future plans to make the Debian package a little more
> Debian-friendly? For instance to get rid of the rpms and use deb
> packages? Is there a reason to use rpms rather than debs?
>
> Thanks,
> --b
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
ARGOSS: your partner for atmospheric, marine & coastal information
P O Box 61
8325ZH Vollenhove The Netherlands
tel +31-527-242299 fax +31-527-242016
Web http://www.argoss.nl

Confidentiality Notice & Disclaimer
The contents of this e-mail and any attachments are intended only for the
use of the e-mail addressee(s) shown. If you are not that person, or one of
those persons, you are not allowed to take any action based upon it or to
copy it, forward, distribute or disclose the contents of it and you should
please delete it from your system.

ARGOSS Holding BV and its subsidiaries do not accept any liability for any
errors or omissions in the context of this e-mail or its attachments which
arise as a result of Internet transmission, nor accept liability for
statements which are those of the author and not clearly made on behalf of
ARGOSS.