On 07/27/2015 05:42 AM, Nils Fredrik Gjerull wrote:
Hi,
Any thoughts please. Would appreciate at least an acknowledgement that
the e-mail was read, so I know I am not sending e-mails into the void :)
I also had a proposal/question about using a http header to set the
login domain. I guess that it is not supported so I should create a
proposal for it?
Den 22. juli 2015 15:32, skrev Nils Fredrik Gjerull:
Hi,
I have a use case were I want to make the SOGo webmail client
accessible through different DNS domains, and based on which DNS
domain is used a login domain is automatically chosen. I want to use
SOGo as a multi-tenant system without users having to choose a login
domain.
Let say that SOGo is available on mail.domain1.com and
mail.domain2.com, and in SOGo I have domain1 and domain2 as separate
login domains. If a user access the SOGo webmail client through
mail.domain1.com, domain1 will be used as the login domain. That way
the user do not have to select the domain or append it to the username.
I am primarily thinking about the SOGo webmail client and not CardDAV
and CalDAV, but I would not mind if it were possible to do it for
them as well. I understand that there is some kind of template
overriding system for the .wox templates. Would I be able to get the
current URL/domain and be able to set a login domain within such a
template?
I appreciate any suggestions.
Regards
It sounds to me like you're mixing technologies --
"domain login" (whether Windows or Samba AD) and SOGo webmail
Perhaps no one has responded simply because they are unsure what you're
trying to do.
IF you already have SOGo webmail available via two domains, are you
running two instances of SOGo and two instances of your mail server
(Dovecot/Postfix, etc.) or have you configured one instance to work for
both?
And, IF you have two "domain logins" are you running two AD servers?
Does domain login come before webmail login, etc? I may be totally
off-base (sorry)
--
users@sogo.nu
https://inverse.ca/sogo/lists