I am trying to setup mailman3 in docker and have some questions, I can see the finish line :) i hope.
I start my images and I can access the web,http://Servername.domain.com/postorius/lists/ and no list are there of course, but How do i sign in?
I click the forget link and I have to enter in a email address. I put in the email address I added to the docker-compose.yaml but that does not wrok.
I have these setup in the .yaml file.
MAILMAN_ADMIN_USER: The username for the admin user to be created by default.
MAILMAN_ADMIN_EMAIL: The email for the admin user to be created by default.
I found this url
http://Servername.domain.com/admin/login
However I never set a password and here is no forget button,
Basically once I have docker installed, and mailman3 up and no lists are available, How do I setup or/and sign in as admin?
Also In docker how can I test sending mail? the command "mailman-web sendtestemail youremailid@domain" from the mailman-web container does not work.
How can I make sure my containers can send and receive mail?
On 7/30/21 10:47 AM, bob B wrote:
Basically once I have docker installed, and mailman3 up and no lists are available, How do I setup or/and sign in as admin?
I'm not sure what the actual command would be do run the django-admin
interface in the docker image, but from below, it looks like it's
mailman-web. Run mailman-web createsuperuser to create an admin ID.
Also In docker how can I test sending mail? the command "mailman-web sendtestemail youremailid@domain" from the mailman-web container does not work.
This command tries to send the mail via SMTP to localhost port 25.
How can I make sure my containers can send and receive mail?
The MTA should be listening on port 25 and that need to be visible in the mailman-web container. See <https://asynchronous.in/docker-mailman/#setting-up-your-mta>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks but I jump into the docker web image and those commands don't work.
[root@....... docker-mailman]# docker exec -it mailman-web /bin/bash bash-5.0# mailman-web createsuperuser bash: mailman-web: command not found bash-5.0# bash-5.0# bash-5.0# bash-5.0# createsuperuser bash: createsuperuser: command not found bash-5.0# bash-5.0# bash-5.0# mailman-web sendtestemail youremailid@domain bash: mailman-web: command not found bash-5.0# sendtestemail youremailid@domain bash: sendtestemail: command not found bash-5.0# bash-5.0# bash-5.0# bash-5.0# bash-5.0# hostname mailman-web bash-5.0# exit exit [root@..... docker-mailman]#
On Fri, Jul 30, 2021, at 11:01 AM, Mark Sapiro wrote:
On 7/30/21 10:47 AM, bob B wrote:
Basically once I have docker installed, and mailman3 up and no lists are available, How do I setup or/and sign in as admin?
I'm not sure what the actual command would be do run the django-admin interface in the docker image, but from below, it looks like it's
mailman-web. Runmailman-web createsuperuserto create an admin ID.
Container images don't support mailman-web command yet, it has to be ported to use the mailman-web command.
You can run commands with docker exec -it mailman-web ./manage.py <command>.
For creating the superuser, you can run1
Although, if you have set the MAILMAN_ADMIN_EMAIL, that command should have already run in the setup process. You want to figure out the email sending process.
Although, you can create a second admin and set the password for it and login using that using the command mentioned at 1.
Also In docker how can I test sending mail? the command "mailman-web sendtestemail youremailid@domain" from the mailman-web container does not work.
You can run
docker exec -it mailman-web ./manage.py sendtestemail youremailid@domainThis command tries to send the mail via SMTP to localhost port 25.
How can I make sure my containers can send and receive mail?
The MTA should be listening on port 25 and that need to be visible in the mailman-web container. See <https://asynchronous.in/docker-mailman/#setting-up-your-mta>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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)
ok
./manage was the piece I was missing so getting closer :).
I set the MAILMAN_ADMIN_EMAIL in the .yaml, but what url do I use to login ?
http://mailman.domain.com/postorius/lists/. **This url does not like the email address I used for forget password.
or http://mailman.domain.com/admin **** this url has no password reset option
I added that environment variable "MAILMAN_ADMIN_EMAIL" after i already upped my containers,
But I then ran "docker-compose down" then "docker-compse up -d". Does that reload and setup everything again? or could that be the issue?
When I tried to send the test email it said "socket.gaierror: [Errno -2] Name does not resolve" sp maybe my mailman-web container can get dns???
On Fri, Jul 30, 2021, at 12:23 PM, bob B wrote:
ok
./manage was the piece I was missing so getting closer :).
I set the MAILMAN_ADMIN_EMAIL in the .yaml, but what url do I use to login ?
http://mailman.domain.com/postorius/lists/. **This url does not like the email address I used for forget password.
Your email has to be confirmed by Postorius for you to login at /accounts/login.
MAILMAN_ADMIN_EMAIL requires you to go through the forgot password process to set an actual password, it doesn't set a default password.
If you email setup is broken for some reason and you can't get it working, one thing you could do is ask Django to simply print the outgoing emails to stdout by adding the following to the settigns_local.py (and restarting mailman-web container):
EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'
You can find the emails in docker logs mailman-web output (or whatever the
command for container's stdout is) and click on the link to verify and login
into your account.
or http://mailman.domain.com/admin **** this url has no password reset option
To reset, you want to go to /accounts/password/reset/. URL should be findable from the Sign In page.
I added that environment variable "MAILMAN_ADMIN_EMAIL" after i already upped my containers,
But I then ran "docker-compose down" then "docker-compse up -d". Does that reload and setup everything again? or could that be the issue?
It reloads the configuration, but the admin is created in database, so that isn't re-created.
When I tried to send the test email it said "socket.gaierror: [Errno -2] Name does not resolve" sp maybe my mailman-web container can get dns???
Yeah, seems like something is wrong with the DNS setup there.
What version of container images are you using?
Also, what is the value of SMTP_HOST? Do you have that setup to point to the MTA?
-- thanks, Abhilash Raj (maxking)
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?
On Fri, Jul 30, 2021, at 1:04 PM, 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_1for 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?
You should replace smtp.example.com in both mailman-extra.cfg and settings_local.py with whatever the IP address of the MTA (which I assume is running on the host, so it'd be the "gateway" address from the container's network) so Mailman components can talk to Postfix to deliver email.
There is some gaps in the documentation because of the latest changes that have been made in the repo and the documentation and docker-compose files aren't versioned properly :(
I've opened a bug report to update the compose and versions
https://github.com/maxking/docker-mailman/issues/481
-- thanks, Abhilash Raj (maxking)
thanks that worked for sending test message by adding or smtp server (email host) in /opt/mailman/core/mailman-extra.cfg /opt/mailman/web/settings_local.py
I have a couple of questions about the container, if its OK.
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?
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?
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.comOn 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)
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.comI 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.comOn Sun, Aug 1, 2021, at 1:52 PM, John Covici wrote:
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.
Try https://asynchronous.in/docker-mailman/web.html
Can you point me where you saw the original URL so I can update it?
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
-- thanks, Abhilash Raj (maxking)
It was in https://asynchronous.in/docker-mailman
On Sun, 01 Aug 2021 16:55:11 -0400, Abhilash Raj wrote:
On Sun, Aug 1, 2021, at 1:52 PM, John Covici wrote:
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.
Try https://asynchronous.in/docker-mailman/web.html
Can you point me where you saw the original URL so I can update it?
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-- thanks, Abhilash Raj (maxking)
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.comSo if I want to start fresh (or resetup my environment and database etc...) how do I do that. I assume I
docker-compose down
backup these files
/opt/mailman/core/mailman-extra.cfg /opt/mailman/web/settings_local.py /opt/mailman/core/mailman-extra.cfg /etc/nginx/conf.d/* /docker-mailman/docker-compose.yamlDelete contents of /opt/mailman/core /opt/mailman/web /opt/mailman/database
replace these backed up files ( or edited version with config changes ) /opt/mailman/core/mailman-extra.cfg /opt/mailman/web/settings_local.py /opt/mailman/core/mailman-extra.cfg
Then run docker-compose up -d
Will that basically let me start fresh and recreate the database and database admin?
participants (4)
-
Abhilash Raj -
bob B -
John Covici -
Mark Sapiro