Nextcloud mail app config error

[pagaille (Matthieu Gaillet)]

Thanks @davidep

–> . NO [NOPERM] Permission denied (0.001 + 0.000 secs).

[Bulat]

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

[thorsten]

Hi,

I am not shure, but for my feeling, it has something to do with this here:

Error on Sogo when accessing parent of shared mailboxes

Dear all, I found some minor strange behavior which I consider as a bug. Maybe it is just some kind of user error either. However, I am not shure if I set up correctly or if I can influence at all. Feel free to move / delete this topic if related to user error When opening a shared folder within SOGo, I get the following error message: “Communication Error with e-mail server” [grafik] However, browsing to any of the created shared mailbox subfolders, the error does not occur…

→ 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

[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.

[pagaille (Matthieu Gaillet)]

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.

[thorsten]

Is there any solution to configure mail within nextcloud in the mean time?

[oneitonitram (Martin)]

@mrmarkuz gave me this solution ad it worked for me

doveadm acl set -A Public authenticated lookup read

[greavette (Charles)]

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.

[pike (Michael Kicks)]

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.

[mrmarkuz (Markus Neuberger)]

@greavette

What, if any, are the risks to running this command on my Nethserver…

Maybe disabling shared mailboxes is the safest way without changing anything.

Nextcloud mail app config error

SOLVED : Just disable the shared mailboxes ! The problem is that nextcloud’s client lists all the folders of the server when connecting. That’s all right but for the Public folder the server answers permission denied. (maybe that’s the root cause @giacomo ?) Here’s the wireshark decode : [image]

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.

https://wiki2.dovecot.org/Tools/Doveadm/ACL

[oneitonitram (Martin)]

@mrmarkuz

Maybe disabling shared mailboxes is the safest way without changing anything.

how is this done?

[pagaille (Matthieu Gaillet)]

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.

[oneitonitram (Martin)]

how comes your dashboard has menu option i have to go to apps to get?

[dnutan (Marc)]

From the Applications sections there’s an “Add shortcut” app option.

[pagaille (Matthieu Gaillet)]

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.

[capote (Marko)]

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.

[Bulat]

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:

1. Remove Public mailboxes
2. doveadm acl set -A Public authenticated lookup read

[fausp (fpausp)]

@Bulat

The solution is the same as before:

1. Remove Public mailboxes
2. doveadm acl set -A Public authenticated lookup read

I am still not able to configure the nextcloud-mailapp with a self-sign-cert…
Could you please post a few screenshots of the mail-configuration?

[pagaille (Matthieu Gaillet)]

Well, I tried again and made some tests. Here are my findings :

Mail v1.7.2 - NC v20.0.4

• Connecting in “auto” mode doesn’t work : Unexpected error during account creation. I don’t really understand why but once I configure the servers manually (not using localhost but fqdns) it finally reports Request failed with status code 500 but I can see in the logs that the connections succeeded. Just click on the Mail icon to reload the page and the account appears and starts to index.

EDIT : Scratch the paragraph below :

• Beside that problem, the Public mailboxes, wether with access to the user or not are not a problem. The client successfully connects to the accounts and ignore the Public Mailboxes it doesn’t have access to, as expected.

• If the now famous command doveadm acl set -A Public authenticated lookup read is not issued, the account creation fails with error 500 and one can notice that message in nextcloud.log : IMAP error: You do not have adequate permissions to carry out this operation. Therefore it looks like the bug is still not fixed, I’ll report it to the developper.

Anyway on my entry level shared server with 2gigs RAM the indexing is really a memory hog and I’m still not able to use it. So I’ll not investigate further right now.

Matt

[pagaille (Matthieu Gaillet)]

Mmmh… thinking twice, I should check wether the “doveadm acl set -A Public authenticated lookup read” command has not been issued in the past on my system… Stay tuned.