[Mailman-Users] one mailing list shunting messages

[Mark Sapiro]

On 10/13/2016 09:51 AM, Knight, Eric wrote:
> I am not sure what to do about this message in error log, any help appreciated.
> 
> 
> Oct 13 11:47:30 2016 (12368) SHUNTING: 1476372076.1651051+54a50f9eb22730094aba33728b8cee7136dad7e2
> Oct 13 11:47:30 2016 (12368) Uncaught runner exception: local variable 'bodylen' referenced before assignment
> Oct 13 11:47:30 2016 (12368) Traceback (most recent call last):
>   File "/usr/server/sulists/Mailman/Queue/Runner.py", line 119, in _oneloop
>     self._onefile(msg, msgdata)
>   File "/usr/server/sulists/Mailman/Queue/Runner.py", line 190, in _onefile
>     keepqueued = self._dispose(mlist, msg, msgdata)
>   File "/usr/server/sulists/Mailman/Queue/IncomingRunner.py", line 130, in _dispose
>     more = self._dopipeline(mlist, msg, msgdata, pipeline)
>   File "/usr/server/sulists/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline
>     sys.modules[modname].process(mlist, msg, msgdata)
>   File "/usr/server/sulists/Mailman/Handlers/Hold.py", line 187, in process
>     if bodylen/1024.0 > mlist.max_message_size:
> UnboundLocalError: local variable 'bodylen' referenced before assignment
> 
> Oct 13 11:47:30 2016 (12368) SHUNTING: 1476376331.709368+f252c549b5b457fe876963e4dba623dd2047e456


What Mailman version is this? Are there any local modifications to
/usr/server/sulists/Mailman/Handlers/Hold.py?

You can run Mailman's bin/unshunt to process the shunted messages, but
only after fixing the issue in Hold.py (I'm sure this issue doesn't
exist in any version distributed by the GNU Mailman project). Or, you
can set the list's max_message_size to 0 (meaning unlimited) to avoid this.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan