no mails to list members
Hi all.
I'm trying to upgrade my mailman2 installation to version 3. I thought lets test with on list first. I imported the list with: mailman import21 bla@lists.blabla.de bla/config.pck. This went well. Now i try to send an email to bla@lists.blabla.de but the message only got delivered to the mailman host.
Jan 03 14:43:44 2019 (10434) Peer: ('127.0.0.1', 38784) Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) handling connection Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) Data: b'LHLO shinymail.eu' Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) Data: b'MAIL FROM:<himbeere@meine-oma.de>' Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) sender: himbeere@meine-oma.de Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) Data: b'RCPT TO:<bla@lists.blabla.de>' Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) recip: bla@lists.blabla.de Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) Data: b'DATA' Jan 03 14:43:45 2019 (10434) ('127.0.0.1', 38784) Data: b'QUIT' Jan 03 14:43:45 2019 (10434) ('127.0.0.1', 38784) connection lost Jan 03 14:43:45 2019 (10434) Connection lost during _handle_client()
No messages ar actually delivered to the list members. Can someone tell me where i have to look to solve this problem? The "Delivery status" is set to enabled.
thanks and cheers t.
Just saw the message is in /var/lib/mailman3/queue/shunt. What messages are going there? Something wrong with my setup?
thanks and cheers t.
On 03.01.19 15:30, Thomas Stein wrote:
Hi all.
I'm trying to upgrade my mailman2 installation to version 3. I thought lets test with on list first. I imported the list with: mailman import21 bla@lists.blabla.de bla/config.pck. This went well. Now i try to send an email to bla@lists.blabla.de but the message only got delivered to the mailman host.
Jan 03 14:43:44 2019 (10434) Peer: ('127.0.0.1', 38784) Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) handling connection Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) Data: b'LHLO shinymail.eu' Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) Data: b'MAIL FROM:<himbeere@meine-oma.de>' Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) sender: himbeere@meine-oma.de Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) Data: b'RCPT TO:<bla@lists.blabla.de>' Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) recip: bla@lists.blabla.de Jan 03 14:43:44 2019 (10434) ('127.0.0.1', 38784) Data: b'DATA' Jan 03 14:43:45 2019 (10434) ('127.0.0.1', 38784) Data: b'QUIT' Jan 03 14:43:45 2019 (10434) ('127.0.0.1', 38784) connection lost Jan 03 14:43:45 2019 (10434) Connection lost during _handle_client()
No messages ar actually delivered to the list members. Can someone tell me where i have to look to solve this problem? The "Delivery status" is set to enabled.
thanks and cheers t.
On 1/3/19 7:43 AM, Thomas Stein wrote:
Just saw the message is in /var/lib/mailman3/queue/shunt. What messages are going there? Something wrong with my setup?
Look in Mailman's mailman.log for an error message and Traceback along with the shunting message which will describe the exception that caused the shunting.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Thursday, 3 January 2019 20:58:19 CET Mark Sapiro wrote:
On 1/3/19 7:43 AM, Thomas Stein wrote:
Just saw the message is in /var/lib/mailman3/queue/shunt. What messages are going there? Something wrong with my setup?
Look in Mailman's mailman.log for an error message and Traceback along with the shunting message which will describe the exception that caused the shunting.
Thanks for your answer. So the the file in queue/shunt contains information too? I will have a look.
cheers t.
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.)
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.
Again. Thanks for your help. t.
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 ?
--a
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/
Thomas
On Friday 04 January 2019 03:25 PM, Thomas Stein wrote:
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.
Thanks for sharing. My instance had same issue. With your investigation I was able to fix the same in mine.
Thanks a lot.
--a
On 04.01.19 09:40, Thomas Stein wrote:
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.
While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? Should I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? Is there some documentation what variables i can put in those templates?
thanks and cheers t.
On Friday 04 January 2019 08:19 PM, Thomas Stein wrote:
On 04.01.19 09:40, Thomas Stein wrote:
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.
While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? Should I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? Is there some documentation what variables i can put in those templates?
If you are using 3.2.0, you can do that from webapp itself. [ I haven't tried though]
--a
On 04.01.19 15:55, Abhijith PA via Mailman-users wrote:
On Friday 04 January 2019 08:19 PM, Thomas Stein wrote:
On 04.01.19 09:40, Thomas Stein wrote:
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.
While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? Should I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? Is there some documentation what variables i can put in those templates?
If you are using 3.2.0, you can do that from webapp itself. [ I haven't tried though]
Running 3.1.1 right now. 3.2.0 isn`t in the ubuntu repo yet afaik.
https://launchpad.net/ubuntu/+source/mailman3
thanks and 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/
On 04.01.19 16:02, Thomas Stein wrote:
On 04.01.19 15:55, Abhijith PA via Mailman-users wrote:
On Friday 04 January 2019 08:19 PM, Thomas Stein wrote:
On 04.01.19 09:40, Thomas Stein wrote:
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.
While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? Should I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? Is there some documentation what variables i can put in those templates?
If you are using 3.2.0, you can do that from webapp itself. [ I haven't tried though]
Running 3.1.1 right now. 3.2.0 isn`t in the ubuntu repo yet afaik.
This ppa seems to have 3.2.0.
https://launchpad.net/~efficios/+archive/ubuntu/ci
Is it trustworthy? Someone using this?
thanks and cheers t.
On Fri, Jan 4, 2019, at 7:02 AM, Thomas Stein wrote:
On 04.01.19 15:55, Abhijith PA via Mailman-users wrote:
On Friday 04 January 2019 08:19 PM, Thomas Stein wrote:
On 04.01.19 09:40, Thomas Stein wrote:
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.
While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? Should I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? Is there some documentation what variables i can put in those templates?
If you are using 3.2.0, you can do that from webapp itself. [ I haven't tried though]
Running 3.1.1 right now. 3.2.0 isn`t in the ubuntu repo yet afaik.
This link mentions that 3.2.0-1ubuntu1 is the current stable version.
thanks and 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/
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)
On 04.01.19 16:05, Abhilash Raj wrote:
On Fri, Jan 4, 2019, at 7:02 AM, Thomas Stein wrote:
On 04.01.19 15:55, Abhijith PA via Mailman-users wrote:
On Friday 04 January 2019 08:19 PM, Thomas Stein wrote:
On 04.01.19 09:40, Thomas Stein wrote:
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.
While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? Should I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? Is there some documentation what variables i can put in those templates?
If you are using 3.2.0, you can do that from webapp itself. [ I haven't tried though]
Running 3.1.1 right now. 3.2.0 isn`t in the ubuntu repo yet afaik.
This link mentions that 3.2.0-1ubuntu1 is the current stable version.
But not for ubuntu 18.04. This one indeed does.
https://launchpad.net/~efficios/+archive/ubuntu/mailman3
cheers t.
thanks and 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/
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/
On 1/4/19 6:49 AM, Thomas Stein wrote:
While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates?
There are multiple ways to reference templates, but just putting them in that location should work.
Should I name the template list:member:generic:footer.txt or list_member_generic_footer.txt?
Your list was created with an older version of import21. That version named the templates it stored with underscores rather than colons and set the URI for that template to use the underscore name. Thus, without changing the URI for the template, you need to continue to use the underscore name for those templates, but for other templates, you can use the name with colons and not worry about the URI.
Is there some documentation what variables i can put in those templates?
See <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.html>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks for the clarification Mark.
cheers t.
On Friday, 4 January 2019 19:25:20 CET Mark Sapiro wrote:
On 1/4/19 6:49 AM, Thomas Stein wrote:
While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates?
There are multiple ways to reference templates, but just putting them in that location should work.
Should I name the template list:member:generic:footer.txt or list_member_generic_footer.txt?
Your list was created with an older version of import21. That version named the templates it stored with underscores rather than colons and set the URI for that template to use the underscore name. Thus, without changing the URI for the template, you need to continue to use the underscore name for those templates, but for other templates, you can use the name with colons and not worry about the URI.
Is there some documentation what variables i can put in those templates?
See <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.html>.
participants (5)
-
Abhijith PA -
Abhilash Raj -
Mark Sapiro -
Stephen J. Turnbull -
Thomas Stein