shadowghost / mailcow-mailman3-dockerized Goto Github PK

If I go to mail. I can see and login to the mailcow UI, as well as SoGO.

Upon going to lists. I see a 400 Bad Request. There is nothing in error.log for Apache regarding the issue, so it's probably something with Postorius and how it is handling.

Any thoughts / where would the Postorius / Django logs be to see if I can debug it.

EDIT:
Upon running the createsuperuser command, I get the following error:

No such container: mailman-web — maybe something didn't create properly?

Hi, really excited about the potential for this project.

Commands run:
I first cloned the repo
sudo bash generate_config.sh
sudo docker-compose pull && sudo docker-compose up -d
The generated the following error:
cannot create network <hash>: conflicts with network <hash>: networks have overlapping IPv4

I thought the issue may have been with previous dockers conflicting network-wise.
I ran the following two commands before retrying the config to confirm:
sudo docker stop $(sudo docker ps -a -q)
sudo docker rm $(sudo docker ps -a -q)

Let me know if anything else would be helpful

I notice you disable let's encrypt SSL certificates with "SKIP_LETS_ENCRYPT=y" in the config.

Does this mean for any new domains I add to mailcow, I must manually update my Let's encrypt issuer e.g. certbot?

I found a 'cronjob' file in "templates/apache2" that has the following in it:

#!/bin/bash
cd /opt/mailcow-mailman3-dockerized && docker-compose down
certbot renew --pre-hook "systemctl stop apache2" --post-hook "systemctl start apache2" --renew-hook "systemctl reload apache2" --quiet
cp /etc/letsencrypt/live/<your-domain-here>/fullchain.pem ./data/assets/ssl/cert.pem
cp /etc/letsencrypt/live/<your-domain-here>/privkey.pem ./data/assets/ssl/key.pem
docker-compose restart

Is there anyway to rewrite this to avoid stopping all containers just to renew the SSL certificates? Should the <your-domain-here> be my primary mailcow domain and not the mailman domain too? I tried this and ran the script, it stopped all the containers and removed them but then they couldn't start back up: https://pastebin.com/raw/MQFqCNdC

Thanks

Hi!

The containers mailman-web, mailman-core and database failed to start with the error "Address already in use" after a system reboot.

With docker inspect I found out, that sometimes an other container starts before mailman-web/core and get the (dynamic) ip like 172.19.199.2. The container mailman-core failed to start, because his (static) ip is already used.

A simple docker-compose stop/start or down/up solves the problem. Or give all containers a static ip in docker-compose.yml.

What do you think?

I am trying to find the logs for mailcowdockerized_mailman-core_1 to find the logs for the REST API.

docker-mailman seems to indicate that the logs will be found at /opt/mailman/core/var/logs/mailman.log. I go to <path-to-repo>/data/mailman/ but there is no core directory in that location.

Thoughts?

steps taken:

1. full backup
2. docker-compose stop && docker-compose rm
3. create a new git branch and set it to track Shadowghost/mailcow-mailman3-dockerized's master
4. add back 0755 modifiers to all the entrypoint scripts and backup-restore as they didn't work.
5. generated config, saw it completely ignored the old settings, merged the two files.
6. docker-compose up -d, the users were working, but the mailbox content was not there, even after a restore. I assume it's a different path issue, but since it's a live machine I didn't want to waste time on debugging.
7. killed, removed all containers, returned to regular branch and restarted. luckily everything was working again.

Can the migration be tested and fixed please? also, can all the .sh files be committed as mode 0755?

Mind writing up a guide for Linode? They'll pay up to $300 for a guide and your package would sure be handy: https://linode.com/docs/contribute/

Hi,
tried an migration to mailcow-mailman3 from an fresh installation of mailcow.
createsuperuser failed:
`root@vmail01:/opt/mailcow-mailman3-dockerized# docker exec -it mailcowdockerized_mailman-web_1 /bin/bash

bash-4.4# python manage.py createsuperuser
Traceback (most recent call last):
File "manage.py", line 8, in
from django.core.management import execute_from_command_line
ImportError: No module named django.core.management 44353fab6e1f maxking/mailman-web:latest "docker-entrypoint.s…" 44 minutes ago Up 12 minutes 8000/tcp, 0.0.0.0:8080->8080/tcp`
I've changed the IP-range (172.22.1) and create port-forwarding 8080 due my proxy is running on an external VM (haproxy).
I've read in an other issue, that mailman hardcoded the IP - perhaps i must reconfigure to
172.19.199?

BTW: in line 29 of generate_config.sh is the last E missing: MAILCOW_HOSTNAM

Udo

Hello,
today I tried to convert my running mailcow but failed. Can you give an explanation on how to do it?

After messing around with Apache2 modules, I got everything working, to be greeted by a database connection error.

There's likely some dumb setting that I forgot about, but it seems like this should be handled by the docker setup.

Everything is setup, I can access both sites mail.<domain> and lists.<domain>. The issue now is that Mailman is not receiving mail. It sends mail (if I add a user, the user gets an email) but when I send an email back to the email address listed in the subscription email, it bounces.

I first tried entering the mail host as <domain> but then noticed that the emails were being sent from Postorius@lists.<domain> so I deleted it and started a list with the mail host as lists.<domain> but that didn't work. To complete the guessing, I also tried mail.<domain> but it still wasn't receiving mail (the bounce error changed each time though, let me know if posting that would be helpful.

The screen that I'm referring to when I saw entering the mail domain is this one:

Hi,

I am trying to get working with the REST API, which, to do so, it seems I must edit the Django configuration of mailman-web.

Their documentation (found here) indicates that there should be a file called settings_local.py which is found in /mailman/web/. I tried searching in <path-to-repo>/data/mailman/ but came up blank. I then searched in a few other directories (all those in <path-to-repo>/data/) but could not find anything.

If it would be possible to mess with these configuration files that would be amazing and/or interact with the REST API which I have as of yet been unable to use.