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/