how come we don’t have the same behaviour ? After all there isn’t much parameters when creating a shared mailbox ? All my test and production machines behave the same.
Anyway the mail app should probably handle this correctly.
1 Like
That’s a question for @davidep. But we did some experiments on our server and maybe it’s not 100% like a clean machine.
Try to run
/etc/e-smith/events//nethserver-mail-server-update/S98nethserver-mail-server-init-acl --force
See if the STATUS command now succeedes
1 Like
Thank you very much @giacomo
This solved my problem
In the “shared mailboxes” I had a folder “Junk” which was created when installing the package nethserver-mail-quarantine
or can it manually
I can not remove “Junk” through the web panel
I deleted “Junk” via ssh console
and it all worked
/ etc / e-smith / events // nethserver-mail-server-update / S98nethserver-mail-server-init-acl --force
This request returns the same answer on both servers
[NOTICE] Initialize ACLs of Public (vmail) IMAP namespace
p.s. when adding a shared mailbox
problem comes back
2 Likes
Hi,
I am not shure, but for my feeling, it has something to do with this here:
→ Maybe the forbidden ACL leads to the same error, however with a larger impact on the nextcloud client. I am more and more convinced that may be solved on the Dovecot level. Maybe it could be worth giving a try to alter devecot ACL.
Best regards
Thorsten
… by the way, I have the same error here, but I can not swith of the shared folders as we use them wildly instead of forewarding single mails. 
Agreed. While some clients are more or less sensitive to the current ACL, even as an user it looks odd to not be able to list the root while the child nodes are.
Is there any solution to configure mail within nextcloud in the mean time?
@mrmarkuz gave me this solution ad it worked for me
doveadm acl set -A Public authenticated lookup read
3 Likes
Hello All,
could someone (@mrmarkuz perhaps) explain what this command will do on my Nethserver:
doveadm acl set -A Public authenticated lookup read
I’m very interested in getting my Nextcloud Mail to work as well. But I’m hesitant to run anything on my Nethserver that is not standard (or done at install or during update). What, if any, are the risks to running this command on my Nethserver…and what would be the command to back out whatever this instruction is doing?
Thank you.
1 Like
The command is related to acl of Dovecot, the MDA of NethServer. You can look into Dovecot documentation for clarify yourself of the effect of the command.
2 Likes
Maybe disabling shared mailboxes is the safest way without changing anything.
The doveadm command just sets an additional read right for the Public folder. I don’t think that any client has a problem with that.
doveadm acl set -A Public authenticated lookup should reset the Public folder permissions as they were before.
4 Likes
how is this done?
Server manager :
Remove the public mailboxes. But I believe that @mrmarkuz 's fix is the definitive answer to this bug and that it should be included in the next releases.
1 Like
how comes your dashboard has menu option i have to go to apps to get?
From the Applications sections there’s an “Add shortcut” app option.
It looks like nextcloud finally got a fix : https://github.com/nextcloud/mail/issues/1735
If someone could test ?
EDIT : That’s for nextcloud 20. We’ll have to wait for the NS upgrade.
3 Likes
thats “funny”…
Yesterday I installed Nextcloud for the first time. After I couldn’t connect the mailboxes (although I hadn’t set up any public mailboxes), I uninstalled the package because I thought a reinstall would solve the problem. Now after a reinstallation I am missing the possibility to install any app, including the mail app.
Still not working!
Installed NethServer 7.9.2009
Updated Nextcloud 20.0.4
Mail application does not work with local email addresses.
The solution is the same as before:
- Remove Public mailboxes
- doveadm acl set -A Public authenticated lookup read