On 04.01.19 10:44, Abhijith PA via Mailman-users wrote:
Hi. Thomas
On Friday 04 January 2019 02:10 PM, Thomas Stein wrote:
On 04.01.19 05:15, Stephen J. Turnbull wrote:
Thomas Stein writes:
Thanks for your answer. So the the file in queue/shunt contains information too? I will have a look.
The file in queue/shunt is the message plus some Mailman metadata, as a Python pickle. You can find out what is in it using "bin/mailman.py qfile", but probably the log and traceback will tell you (or us) everything needed to fix the problem.
If it's a Mailman bug (somewhat unlikely), we send you a patch and you use "bin/mailman.py unshunt" to reinject the message into the mail system via Mailman. If it's a nonconforming mail message (somewhat more likely -- typically this happens when you have raw UTF-8 or other 8-bit characters in the message header), then the easiest thing to do is to edit a saved copy of the message and resend from your mail client. (It's theoretically possible to edit the pickle and use "unshunt", but Mailman currently does not provide that feature.)
Turns out mailman was not able to read a specific template. That seemed to be enough to throw an exception. Maybe i missed something else but after adjusting the permissions of that template everything worked as expected.
Can you explain little bit more about this template, path and its permission ?
Sure. I should start with mentioning the mailing list in question was imported with "mailman import21". After that i had:
root@shinymail:~# ls -l /var/lib/mailman3/templates/lists/hoppla.domain.de/en/ total 8 -rw-rw---- 1 list list 106 Dec 26 18:48 list_member_digest_footer.txt -rw-rw---- 1 list list 110 Dec 26 18:48 list_member_regular_footer.txt root@shinymail:~#
These txt files where owned by root:root. After changing it to list:list the problem disappeared.
cheers t.
--a
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/