On 09/29/2017 02:10 AM, Henrik Rasmussen wrote:
Thanks, Mark.
@Abhilash, any chance for an update to Docker-mailman to fix these known issues soon? https://gitlab.com/mailman/mailman/issues/256
@Henrik, Contrary to what I said earlier, your issue is not exactly #256. #256 is fixed in Mailman to the extent that the defective message no longer breaks Postorius or causes exceptions in REST, but the underlying issue causing the "KeyError: 'content-transfer-encoding'" exception is not in Mailman. It's in the Python email package. The issue that needs to be fixed for that is <https://bugs.python.org/issue27321>.
The bottom line is at this point, <https://bugs.python.org/issue27321> no longer affects Postorius, but it still affects message delivery. I have opened <https://gitlab.com/mailman/mailman/issues/406> about defending against that and also the UnicodeEncodeError you included in your OP.
@Mark,
Mark Sapiro wrote:
bin/mailman queue var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck
Isn't this a Mailman 2 command? What is the Mailman 3 equivalent?
No. 'bin/mailman queue' is the Mailman 3 command. The Mailman 2 command is 'bin/show_qfiles'.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan