Ok, I’m testing a solution for a customer
AD domain realm is something like domain.local
public domain is something like mycompany.tld
NS is successfully joined to AD domain, its only domain is mycompany.tld, I see all users and groups… so far, so good.
now…
If I use userPrincipalName AD attribute (user@domain.local), once logged I see that this is my email address… I’d edit all accounts properties to change it to user@mycompany.tld…
in sogo’s documentation I read, regarding MailFieldNames:
An array of fields that returns the user’s email addresses (defaults to mail when unset). Note that SOGo will always automatically strip the protocol value from the attribute if the attribute name is proxyAddresses.
If I create a custom fragment to unset the MailFieldNames value or to set it to “mail”, once logged in webmail I see I’m using the correct email address… but…
but once logged I see in /var/lib/nethserver/vmail a dir named user@domain.local; if I send an email to this user on its real email address (either from an external account or from an internal one) a new dir named user@mycompany.tld is created and I can’t see its content from my webmail or my email client.
since my customer has only one domain I’d like to know how to setup my NS to solve my issue or an howto to configure it in such a situation
if I compose a new mail and search for an internal user, both domain.local and mycompany.tld addresses are shown (and I don’t like it)
moreover, searching for an address, I get the workstations (joined to domain) names, and this is clearly a bug
hope @stephdl will jump in, I know that nethserver-sogo is a package from him
thank you for your feedback
I see that altlinux packages are based on last release (20th july 2017)
BTW… I’m asked to find a real alternative to exchange… unfortunately sogo can’t be considered one, 'cause openchange is unsupported on centos and TB integration seems broken with latest releases of TB, lightning and sogo connector/integrator packages…
webmail is not an option, even if I have some customers that are using it
Ok, I tried with version 31.0.5 of SOGo Connector now, it works without problems, I didn’t tried with Integrator, but if you post errors later perhaps we can find the issue and I can compare the output with and without integrator.
I recall something similar to your issue, we talked about sometime ago with davidep. I tought the issue was solved by an update because i tested last night with a fresh vm
Start the vm
Full update
Install nethserver-dc
Install nethserver-sogo
Like i said i cannot reproduce your issue but we might do some changes like you introduced
Do others can test and see if the domain name in sogo is a dummy or good one ?