I am finding some missing documentation in the section on configuring mailman-web, it refers to a file https://asynchronous.in/docker-mailman/web/ which does not exist.
On Sat, 31 Jul 2021 21:21:24 -0400, John Covici wrote:
OK, thanks a lot -- if anyone here can help with proper config for those, that would be great. I do have a web server, but its apache rather than mginx and I am not sure how to properly translate. Also, doing a separate container for an mta which would just talk to mailman would get around the sendmail situation I have, although there may be a decent way to do that as well. I guess the hard part is to tie the multiple containers together.
On Sat, 31 Jul 2021 17:56:15 -0400, Abhilash Raj wrote:
On Sat, Jul 31, 2021, at 3:56 AM, John Covici wrote:
I have a couple of questions about the container, if its OK.
Sure it is :)
First, it says to run you create the directory /opt/mailman/mailman-core and /opt/mailman/mailman-web and then do the git clone. What directory should the git clone be in?
You can do clone anywhere you can run commands from. There aren't any files in the repository that you'd be directly using. You'll just be relying on the docker-compose.yaml file from the repo (or one of the other compose files if you choose to use a different database) unless you are going to build the container images on your own instead of using the published ones.
I just do it in my home directory of the user I am running commands as. /opt/mailman could be a good option too.
A couple of more questions -- is there a way to install the web server and the mta in the container, this way I could make the whole thing be independent of my host configs?
You probably don’t want to install mta and webserver in the Mailman containers, you want to add separate containers for them and make Mailman containers talk to them. This will let you keep the container for each component separate and it is just easier to manager.
You would need to add appropriate containers for webserver and mta in the docker-compose.yaml file and figure out the configuration on how to tie them to Mailman. The Mailman container images repo doesn’t provide such a configuration, but there are folks in the channel who have done it and you should be able to find them in this list’s archives.
On Fri, 30 Jul 2021 16:04:48 -0400, bob B wrote:
is this the info you need for the container version
[root@..... docker-mailman]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 30af82ac9315 maxking/mailman-web:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8000->8000/tcp, 127.0.0.1:8080->8080/tcp mailman-web cd01a99cf908 maxking/mailman-core:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core 77fe89ced9e8 postgres:9.6-alpine "docker-entrypoint.s…" 2 hours ago Up 2 hours 5432/tcp dockermailman_database_1
for smtp host
cat /opt/mailman/web/settings_local.py #allowed_hosts = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] #ALLOWED_HOSTS = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] ALLOWED_HOSTS = ['*'] DEBUG = True EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'smtp.example.com' EMAIL_PORT = 25
cat /opt/mailman/core/mailman-extra.cfg # mailman-extra.cfg
[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver # mailman-core hostname or IP from the Postfix server lmtp_host: localhost lmtp_port: 8024 # Postfix server's hostname or IP from mailman-core smtp_host: smtp.example.com smtp_port: 25 configuration: /etc/postfix-mailman.cfg [mailman] # This address is the "site owner" address. Certain messages which must be # delivered to a human, but which can't be delivered to a list owner (e.g. a # bounce from a list owner), will be sent to this address. It should point to # a human. site_owner: my_real_email_is_in_the_file.com
My docker most machine /etc/postfix/main.cf has
transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains
# Support the default VERP delimiter. recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no
is that correct? I leave them set to smtp.example.com because the will send out via the docker host machine, and so i ONLY have my actual outbound server listed in /etc/postfix/main.cf on the docker host machine, or do i need to replace smtp.example.com with our outbound server?
Also, If I want to blow away everything away (databse etcc) and rebuild it... what are those steps?
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it?
John Covici wb2una covici@ccs.covici.com
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it?
John Covici wb2una covici@ccs.covici.com
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it?
John Covici wb2una
covici@ccs.covici.com