Mail account provisioning + SSO

ollioddi

Hi everyone.

I already have mailcow successfully running, along with Nextcloud. My hopes are to have a nice unified and integrated mail / file experience.

Therefore i would like to handle all account management in a single place.

I read the blog and that LDAP is coming late 2023 with mainly Keycloak support. I initially would prefer to use Authentik, but the integration is more important to me.

My first question is, has anyone got Nextcloud provisioning to work with Mailcow? I suppose the main benefit is that a user within Nextcloud automatically gets its email setup with an email provider, such as Mailcow.

See this screenshot for configuration:

My second question is if this is something that is also supported / improved with LDAP support and Keycloak.

The ideal solution for me would be a single place to manage user accounts (Such as Keycloak) which can authenticate against Nextcloud and automatically provision an email account in Mailcow.

I hope someone can clarify future plans and if anyone has a similar setup. Thanks in advance

jonboy86

This sounds interesting

roelofz

This could be my experience, below my experience, looks the same.
No one with experience on this subject?

My story:
I’ve searched and searched, but haven´t found it.

I have a running Mailcow docker install and installed using the helper script Nextcloud.
I installed and downloaded nextcloud mail and am trying to connect it.
All descriptions say to use the external url (mailcow.domain.ext), but it doesn´t work using ssl or cleartext. Also using the internal IP does not work.

Since it hasn´t been documented and I must be doing something wrong, here’s the question:
Has anyone succeeded in getting this to work?

Steps to reproduce:
Install and configure mailcow, using mailcow documentation
install Nextcloud using the third party script
Install Nextcloud mail and try to connect using the user interface

Ubuntu 22.04 lTS
dual cpu 8Gb mem
Docker: 24.0.6, build ed223bc
compose: v2.9.0
Mailcow version: 2023-10a

PS: Nextcloud can communicate with Collabora container, separate docker container (took some time too, it is functional as far as I can see)

Thanks!

PS: the backup script is missing the Nextcloud file data, as also the complete website content, I fixed this in my backup script. If someoneś interested, let me know.

roelofz

I searched a little further.
It looks like two things are possible problems.

My mailserver is resolved in docker by the external address, Unbound is the source of this, I don´t know how to get unbound to change this.
Secondly I found a setting in Nextcloud preventing to connect to an IP address or the localhost (changing this setting and restarting Nginx did not work).

There is logging of the connection attempt:

Oct 24 23:35:04 de1420939bae dovecot: imap-login: Login: user=user@maildomain.ext, method=PLAIN, rip=172.22.1.248, lip=172.22.1.250, mpid=564520

Oct 24 23:35:05 de1420939bae dovecot: imap(user@maildomain.ext)<564520><ITunHH0IUr2sFgH4>: Disconnected: Logged out in=151 out=1721 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0
Result in Nextcloud: IMAP server is not reachable

So maybe this helps in helping us!