...

When I send a message from the Postorius interface, it is neither sent out or stored. I briefly see this message: "Your reply has been sent and is being processed.", and then nothing happens.

When you say nothing happens, you just mean that you don't see anything in the UI or you don't see anything in the logs?

In the UI, I get a green line with text saying the message has been sent. However, the new message is not added to the the thread in any way. In the logs there is nothing that pertains to that particular action

Logs for mailman-web are in /opt/mailman/web/logs/mailmanweb.log (on the host).

The log mailmanweb.log is empty. uwsgi.log is not empty. Interestingly, in the mailman-web container, there is a mailmanweb.log in the root of the server which gets updated like this: INFO 2017-11-21 10:53:33,765 36 hyperkitty.views.mailman Archived message <20171121115328.2dc8970f@thor-E6530> to https://mailer.domain.com/ hyperkitty/list/aaa@klubb.domain.com/message/2XYZL6G35IJYOW5WG6IGXI424Q44DG FK/ but nothing is written when I try to send message from Postorius.

...

I have installed maxking's docker-mailman and copied my old setup with basic stuff like passwords and such. The only new thing is that I'm now running in userspace by putting in /etc/subuid and subguid:

mailman:10000:65536

This ideally shouldn't affect anything, I haven't tried running this way though.

...

and in /etc/docker/daemon.json:

{ "userns-remap": "mailman" }

So I get the following ownership in /opt/mailman:

drwxrwsr-x 3 10100 10000 4096 nov. 21 09:00 core drwx------ 19 10070 10000 4096 nov. 21 09:27 database drwxr-sr-x 5 10100 10101 4096 nov. 21 09:24 web

(I have created a user named mailman with uid 10100 so, in reality, it

says

...

"mailman" there instead of 10100 but I guess that is irrelevant here)

If would be interesting to see what processes are running inside each containers and who their owners are, in case this is at all relevant to the issue, which I am not so sure about.

Web container:

bash-4.3# ps aux PID USER TIME COMMAND 1 mailman 0:00 uwsgi --ini /opt/mailman-web/uwsgi.ini 36 mailman 0:00 uwsgi --ini /opt/mailman-web/uwsgi.ini 37 mailman 0:00 /bin/sh -c ./manage.py qcluster 41 mailman 0:00 python ./manage.py qcluster 54 mailman 0:00 python ./manage.py qcluster 55 mailman 0:00 python ./manage.py qcluster 56 mailman 0:00 python ./manage.py qcluster 57 mailman 0:00 python ./manage.py qcluster bash-4.3# ls -l total 96 -rw-rw-r-- 1 mailman root 0 Mar 29 2017 __init__.py -rw-rw-r-- 1 mailman root 42308 Nov 21 10:53 mailmanweb.log -rwxrwxr-x 1 mailman root 242 Mar 29 2017 manage.py -rw-rw-r-- 1 mailman root 12171 Oct 1 22:26 settings.py -rw-r--r-- 1 root root 9643 Nov 21 09:21 settings.pyc -rw-rw-r-- 1 mailman root 1777 May 23 21:31 settings_local.py -rw-r--r-- 1 root root 1196 Nov 21 09:21 settings_local.pyc -rw-rw-r-- 1 mailman root 1314 Mar 29 2017 urls.py -rw-r--r-- 1 root root 791 Nov 21 09:21 urls.pyc -rw-rw-r-- 1 mailman root 1425 Aug 6 17:04 uwsgi.ini -rwxrwxr-x 1 mailman root 1173 Mar 29 2017 wsgi.py

core container: bash-4.3# ps aux PID USER TIME COMMAND 1 mailman 0:00 {master} /usr/local/bin/python /usr/local/bin/master 26 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=archive:0:1 -C /etc/mailman.cfg 27 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=bounces:0:1 -C /etc/mailman.cfg 28 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=command:0:1 -C /etc/mailman.cfg 29 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=in:0:1 -C /etc/mailman.cfg 30 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=lmtp:0:1 -C /etc/mailman.cfg 31 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=nntp:0:1 -C /etc/mailman.cfg 32 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=out:0:1 -C /etc/mailman.cfg 33 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=pipeline:0:1 -C /etc/mailman.cfg 34 mailman 0:01 /usr/local/bin/python /usr/local/bin/runner --runner=rest:0:1 -C /etc/mailman.cfg 35 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=retry:0:1 -C /etc/mailman.cfg 36 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=virgin:0:1 -C /etc/mailman.cfg 37 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=digest:0:1 -C /etc/mailman.cfg

2017-11-21 11:18 GMT+01:00 Abhilash Raj <maxking@asynchronous.in>:

Hi Thor,

On Tue, 2017-11-21 at 10:53 +0100, Thor Atle Rustad wrote:

...

I have had this working before, so I guess it's a simple setup error.

When I send a message from the Postorius interface, it is neither sent out or stored. I briefly see this message: "Your reply has been sent and is being processed.", and then nothing happens.

When you say nothing happens, you just mean that you don't see anything in the UI or you don't see anything in the logs?

Logs for mailman-web are in /opt/mailman/web/logs/mailmanweb.log (on the host).

...

I have installed maxking's docker-mailman and copied my old setup with basic stuff like passwords and such. The only new thing is that I'm now running in userspace by putting in /etc/subuid and subguid:

mailman:10000:65536

This ideally shouldn't affect anything, I haven't tried running this way though.

...

and in /etc/docker/daemon.json:

{ "userns-remap": "mailman" }

So I get the following ownership in /opt/mailman:

drwxrwsr-x 3 10100 10000 4096 nov. 21 09:00 core drwx------ 19 10070 10000 4096 nov. 21 09:27 database drwxr-sr-x 5 10100 10101 4096 nov. 21 09:24 web

(I have created a user named mailman with uid 10100 so, in reality, it

says

...

"mailman" there instead of 10100 but I guess that is irrelevant here)

If would be interesting to see what processes are running inside each containers and who their owners are, in case this is at all relevant to the issue, which I am not so sure about.

...

---

Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- thanks, Abhilash Raj

I go with the workaround from Cameron Smith: sudo docker-compose exec mailman-web ./manage.py runjobs yearly makes messages appear

However, there was "something" else that caused my messages not only NOT to show up in Hyperkitty, but also caused them not to be sent in the first place. I believe the reason was wrong subdomain in SERVE_FROM_DOMAIN in docker-compose.yaml.

2017-11-22 0:38 GMT+01:00 Mark Sapiro <mark@msapiro.net>:

On 11/21/2017 01:53 AM, Thor Atle Rustad wrote:

...

I have had this working before, so I guess it's a simple setup error.

When I send a message from the Postorius interface, it is neither sent out or stored. I briefly see this message: "Your reply has been sent and is being processed.", and then nothing happens.

I assume you mean HyperKitty. Postorius has no facility for posting messages to a list.

...

I have installed maxking's docker-mailman and copied my old setup with basic stuff like passwords and such. The only new thing is that I'm now running in userspace by putting in /etc/subuid and subguid:

When you post from HyperKitty, HyperKitty creates a django.core.mail.EmailMessage() instance and calls it's send() method which causes Django to send the message to the list address. It then has to be received and processed by Mailman the same as any email post before it will appear in the archive.

Are you running with DEBUG = True. If so, Hyperkitty won't send the mail.

If DEBUG = False and normal posting is working, perhaps there is some Postfix issue in delivery of the message from Django to Mailman.

-- 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 https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/