Public bug reported:
At least sometimes, when a message is shunted because an exception is
thrown in IncomingRunner the pipeline saved in the msgdata of the
shunted message can start with the handler following the one being
handled when the exception is thrown.
This has been observed when Moderate attempted to reject a message and
raised Errors.RejectMessage. IncomingRunner then called BounceMessage to
send a reject notice and BounceMessage threw an IOError exception. The
message was shunted with a pipeline starting with the handler following
Moderate which had already been successfully popped from the pipeline.
When the message was unshunted, Moderate was skipped and the message
which should have been rejected was delivered to the list.
** Affects: mailman
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: In Progress
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1519062
Title:
Unshunting a shunted message can skip the original shunting handler.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1519062/+subscriptions
_______________________________________________
Mailman-coders mailing list
[email protected]
https://mail.python.org/mailman/listinfo/mailman-coders
