Roundcube with mailcow (w/ Docker Compose)

Maago

ah, not a complete separate compose .. understand

CodeShellDev

technically it is possible to do that, you just need to have roundcube added to a network that mailcow‘s nginx container is able to connect to / is connected to.

Just add this to both compose files

networks:
    rc-net:
       external: true

services:
    rc:
       #…
       network:
           rc-net:
              #…

To make sure the network is always available even when mailcow is down create a persistent network with…

docker network create rc-net

Maago

yes. I set it now into the same docker network as mailcow and it works. Only sending mails not possible:
PHP Error: SMTP server does not support authentication

CodeShellDev

actually, I think postfix etc. may need to also access roundcube directly, it would be easiest to use the mailcow-network which every mailcow service uses instead of creating a roundcube-only network

Maago

I’m using the Mailcow network and Roundcube is part of 172.22.1 network. I can see it in “docker network inspect mailcowdockerized_mailcow-network”

CodeShellDev

like this:

docker network create \
  --driver=bridge \
  --opt com.docker.network.bridge.name=br-mailcow \
  --ipv6 \
  --subnet=172.22.1.0/24 \
  --subnet=fd4d:6169:6c63:6f77::/64 \
  mailcow-network

but as you can see you‘d have to set the ipv4/v6 subnet manually so changing the mailcow.conf file won‘t affect the subnet… but it is pretty unlikely that you want to change the ip subnet after having mailcow setup so this command should work, then in the compose file you would need to set

mailcow-network:
   external: true

[unknown] so you are using the mailcow-network for roundcube

try this https://docs.mailcow.email/third_party/roundcube/third_party-roundcube/#allow-plaintext-authentication-for-the-php-fpm-container-without-using-tls

If this works, then I‘ll be adding it to the documentation, I think I forgot to add it after my testing

If not, could you please post your roundcube compose section with environment variables.
And also it would be easier if you could also add the postfix logs…

CodeShellDev

Looking through my setup I noticed I left a config.inc.php file from the Integrated Install (forgot to migrate)…

In there I can see that the ports do not match…
So actually my docker environment variables are incorrect!:

ssl://postfix:587 becomes ssl://postfix:587:587, because ssl is already telling rc to use port 587 furthermore the integrated setup seems to be using port 588 for postfix so instead modify the variables like so…

      ROUNDCUBEMAIL_DEFAULT_HOST: dovecot:143
      ROUNDCUBEMAIL_SMTP_SERVER: postfix:588

I am wondering wether it is more suitable to use the env variables for configuring roundcube (easy access) or instead doing the config via a custom config.inc.php file that is mounted into rc/config, this way the documentation would stay more in lign with the integrated install, while also having each configuration variables available since the environment variables only support a few settings…
Tho composer plugins would still need to be installed by setting them in the variable

CodeShellDev

Actually just remove ssl:// and :143/:588 these variables do no even support ports, instead you must modify ROUNDCUBEMAIL_SMTP_PORT to be 588

Manage Sieve host also needs to be set inside of a config file

CodeShellDev

Scrap that, I finally made the (hard) decision to let go of the Plugin Env Variable and to instead do most of the plugin installation inside of configs (since there is almost always something that needs to be additionally added to them).

So as soon as my PR is live, Integrated Install and Standalone Install will be almost identical beside the mounts and the few Env Variables that I couldn’t bring myself to also move to the config (since that in my opinion is one of the pros for the seperate container).

Let’s hope the new PR won’t end up being a complete trainwreck. (like the other ones)

« Previous Page