As for the traceback - I'm assuming it's from postorius, as this happens when attempting to load the held messages in the Postorius UI.
On Mon, Apr 23, 2018 at 3:29 PM, Darren Smith <silas.crutherton@gmail.com> wrote:
"It's in Mailman's database in the 'message' table."
I can see the message table - is there a way to see where it is marked as "held"? All I'm seeing in that table is id, message_id, message_id_hash, and path.
I'm wanting to be able to query for held messages for a given mailing list, as there are currently over 98,000 entries in the message table.
-Darren
On Mon, Apr 23, 2018 at 3:17 PM, Mark Sapiro <mark@msapiro.net> wrote:
So it appears that there was a message sent to one of our mailing lists that was put into the held message queue. However, when attempting to go to the message to do the moderation, the web page returns and Error 500.
Looking in the mailman log, I found this:
Apr 23 14:21:02 2018 (17878) REST request handler error: Traceback (most recent call last): File "/opt/mailman3/conda/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ database/transac tion.py", line 50, in wrapper rtn = function(*args, **kws) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ rest/wsgiapp.py" , line 214, in __call__ return super().__call__(environ, start_response) File "/opt/mailman3/conda/lib/python3.6/site-packages/falcon/api.py", line 227 , in __call__ responder(req, resp, **params) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ rest/post_modera tion.py", line 167, in on_get resource = self._make_collection(request) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ rest/helpers.py" , line 159, in _make_collection for resource in collection] File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ rest/helpers.py" , line 159, in <listcomp> for resource in collection] File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ rest/post_modera tion.py", line 157, in _resource_as_dict resource = self._make_resource(request.id) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ rest/post_modera tion.py", line 100, in _make_resource make_header(decode_header(resource['subject']))) File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 174, in make_he ader h.append(s, charset) File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 295, in append s = s.decode(input_charset, errors) UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: illegal multibyte sequence
It LOOKS as if there might be a character in the email somewhere -
On 04/23/2018 01:31 PM, Darren Smith wrote: possibly
in the subject or sender fields? - that is somehow unexpected.
It appears that the Subject: header is RFC 2047 encoded and there is an encoded word with charset gb2312 that contains an invalid encoding.
The message is apparently defective, but this kind of defect shouldn't cause a 500 error.
I can't tell for sure from the traceback if this is Postorius or some other application accessing the REST api. Is it Postorius or something else?
I am attempting to find the held message - can someone point me where I can go to see the message so that I can see what might be causing the problem?
It's in Mailman's database in the 'message' table.
-- 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/