multiple kolab installation question :(

[Antonio Straziota]

hi guys...

i'm tring the solution putting the webmail server as master kolab and
more slave as local mail server,

-webmail (master)
|- site1 (slave)
|- site2 (slave)
|- etc... (slave)


I create a user on site1 from webmail and... i always login on my user
even if site1 server is powered off... :-|
if i shut down webmail, i never login on my user on site1

peraphs it's a stupid question but, if my mailbox is stored on the
slave server i can access it only if the slave server is available and
if my master server should access my mailbox also if master si
unavailable? is correct?

If no, my problem couldn't be solved by installing all kolab as slave
of a single common server, because i need all local users  to be
stored on their local kolab without any affect from the master or from
other slave...

anyone has suggestion about the use of a single webmail for all kolab
installation?
for example, if i i want to install a server with only HORDE there is
something to do on that installation make it works correctly with all
kolab?

Thanks.


2009/1/25 Gunnar Wrobel <wrobel at pardus.de>:
> Quoting Antonio Straziota <devgioiatech at gmail.com>:
>
>> Thanks for reply...
>>
>>> Horde should be able to connect to the users kolabHomeServer instead of
>>> localhost. I'm not sure how Horde is preconfigured in native kolab
>>> installations, but it is able to do that in general.
>>
>> Ok ,so, from my "salve webmail" of the master i can access to mail box
>> on each other slave?
>
> Yes, this should work. If you have problems with this, please report back
> and we'll make it work ;)
>
> Cheers,
>
> Gunnar
>
>> I'll try it :-)
>>
>>> One drawback in your constellation are shared folders, which are shared
>>> on one
>>> server only. A user on server A can't share stuff with a user on server
>>> B.
>>> This can be avoided with "cyrus murder", a kind of cluster-enhancement
>>> for
>>> cyrus. It is a bit tricky in setup and certainly will need patches
>>> against
>>> kolabd.
>>
>> At this time I don't need this... but i'll study it for future ;-)
>>
>>> Mhm, what are your goals? Centralized user management (Kolab) or
>>> decentralized
>>> user management (indipendet samba sites)?
>>
>> I need decentralized one: every site has kolab server and a file
>> server accessible from user of THAT site.
>>
>> Really, my problem is that i've only one entry/exit point from/to
>> internet.
>> I have to make all kolab accessible from internet from that point, but
>> all kolab server must be indipendent from the other.
>>
>> Thanks again.
>> I'll try this architecture.
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>
>
>
>
> --
> ______ http://kdab.com _______________ http://kolab-konsortium.com _
>
> p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
>
> ____ http://www.pardus.de _________________ http://gunnarwrobel.de _
> E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
> Tel.   : +49 700 6245 0000                          Bundesstrasse 29
> Fax    : +49 721 1513 52322                          D-20146 Hamburg
> --------------------------------------------------------------------
>   >> Mail at ease - Rent a kolab groupware server at p at rdus <<
> --------------------------------------------------------------------
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
>