NethServer Version: NethServer release 7.4.1708 (Final)
Module: Dovecot mailserver
ISSUE: User-shared mailboxes do not show in any client.
I am running into an issue that has got me puzzled a bit. I installed 2 Nethservers with the following specifics:
Both server1 and server2 where installed with FQDN as .example.com on the network settings page (CentOS portion of install)
Both server1 and server2 where installed using defaults except for network settings, where I changed IP to fixed and altered the FQDN. I left 188.8.131.52 as DNS server. On install-completion I went through the web-portion of the setup, altered the SSH port to something we use locally for SSH, and ran a full update followed by a reboot cuz I played with Windows too long and it never hurts.
Both servers are in the same state, the only difference being their configured IP and hostname (incl FQDN) at this point.
I proceeded to install the AD account provider on server1, thus creating the domain/realm ad.example.com with virtual server nsdc.ad.example.com. server1 is auto joined, and exists now as server1.example.com and server1.ad.example.com. I created the users user1, user2 and sogobind.
I then proceeded to install SOGo on server2, joined server2 to the just created domain and checked if I could log into the webmail. All is working, I even got the sensible domain @example.com as email domain, instead of the expected @ad.example.com.
NOTE: I did not change the servername (FQDN) in the Nethserver webinterface of server2 prior to joining the domain, nor did I alter the DNS server in any way. The Nethserver webinterface shows only 184.108.40.206 being used as DNS server. I made that 172.16.1.6 now, but that shouldnt be related. A minor irk is not being able to correctly set the FQDN to server.ad.example.com before joining, and thus ending up with server.example.com in the webinterface and this in the Samba info:
Us using user1 and user2 kinda logins, I will require aliases just the same tho. So, after confirming I have the users in SOGo, I created aliases in the form .@example.com
I altered the webinterface settings to reflect the email email@example.com instead of user1.example.com. This works fine in both sending and receiving mail. Up till now, I am extremely happy as well … as this was done in less then no time at all.
However … once I try to share user1’s mailbox, either by delegating the complete mailbox or by granting every right possible with the webinterface on the INBOX to user2, the fun starts.
As documented I made sure that I had set shared mailboxes to enabled, even tho this is the new default iirc:
config setprop dovecot SharedMailboxesStatus enabled
… config getprop yada yada returns ‘enabled’, so yay… this is set up like it should.
I checked the dovecot.config, and it has the Shared namespace enabled.
From my understanding, this should now work and I should be able to log into SOGo with user2, and see user1’s mailbox in a now visible and populated Other users folder or something to that degree. I dont.
Nor does it show in Thunderbird or Outlook2016 or Android mail.
When I check permissions using doveadm acl debug -u user2 Sharedfirstname.lastname@example.org/INBOX it tells me the location doesnt exist. Same for Sharedemail@example.com/INBOX.
I do have rights to open Sharedfirstname.lastname@example.org/INBOX.
I am a bit newish to this, but from my understanding this is correct, correct ?
Whatever I do with the way I logon to the mailboxes (domain\user|user|user@domain|name@domain), from whatever client, I do not see the Shared namespace in the user-mailbox, populated with the user1 shared folders.
Can anybody point me in the right direction ? What does it take to enable this AND make it visible to user2 in this case ? (I already tried setting ACL’s with doveadm acl command. No luck.) I’m not near a work terminal right now but will provide everything but the raw disks if needed … I am going crazy over this one.
I ran into the same issue with the pre-release, but made a mess of the config files while ‘diagnosing’ (erring in hopes of eureka moment) the issue and didnt want to have to build my question on that … however, I am now running a clean install with minimal changes to the config.
I have tried just about every other solution out there … I hope I am just missing something really obvious, as this is kindof the last minor detail that needs fixing before I can migrate our production environment.
Thanks for reading, any suggestion is appreciated!