multiple kolab installation question :(

[Gunnar Wrobel]

Quoting Antonio Straziota <devgioiatech at gmail.com>:

> So,
> i made bootstrap for "webmail" server as master kolab and "site1" as
> slave of the first one.
>
> which kind of info resides on the master kolab about users hosted on  
> the slave?

The LDAP tree is replicated completely, meaning that all users are  
stored in LDAP on both servers.

> why, if i shut down the slave, i can access from master to a user that
> resides on slave? :'-(

What do you mean by "access" here? IMAP access? If the slave is  
powered down I doubt you can read the mails of the users.

> As you wrote, this is wrong! I should not access users of the slave if
> this server is powered off!

True.

In case you mean that you can login via Horde even if IMAP is powered  
down: This might be related to  
https://www.intevation.de/roundup/kolab/issue3282.

>
> About the sentence you don't understand, i wrong to wrote it :). The
> question is: can i access users on my slave also if the master is
> unavailable (powered off, ldap or any service not running)?

Yes.

>
> can you help me to understand?
>
> or anyone as a suggestion about compiling only horde for webmail use
> on multiple kolab?

The current suggestion is to install a full Kolab server for that. You  
could probably also download the corresponding horde-webmail release  
and apply the Kolab patch from CVS. But that requires a bit more  
knowledge.

Cheers,

Gunnar

>
> Thanks again... (HELP MEEEE, PLEASE :D)
>
>
> 2009/1/28 Bernhard Reiter <bernhard at intevation.de>:
>> On Dienstag, 27. Januar 2009, Antonio Straziota wrote:
>>> if my mailbox is stored on the
>>> slave server i can access it only if the slave server is available
>>
>> Correct. (I mean if no server serves the filesystem, you cannot access it
>> obviously.)
>>
>>> and
>>> if my master server should access my mailbox also if master si
>>> unavailable? is correct?
>>
>> I do not know what you mean.
>> The master server cannot connect to the IMAP server on the slave server
>> if this is not running.
>>
>> Note that the "master" "slave" terminology in Kolab Server mainly means
>> master and slave for the directory service. From the view of mailboxes it is
>> better to think of homeserver and non-homeserver.
>> (So for some users the "master" is home and for other users it is not.)
>>
>> The Webclient needs to make contact to the Homeserver for the user, because
>> that is where the folders are.
>>
>>
>>
>>
>>
>>
>> --
>> Managing Director - Owner: www.intevation.net      (Free Software Company)
>> Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
>> Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
>> Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>
>>
>
> _______________________________________________
> 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.kolab.org/pipermail/users/attachments/20090129/110e46de/attachment.sig>