GNU Mailman

Mailman 3.0 goes awry when handling messages in an unexpected format

Bug #1333902 reported by NotTheEvilOne on 2014-06-24

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	GNU Mailman	New	Undecided	Unassigned

Bug Description

Hi,

This bug report is little bit inaccurate. I had the following situation.

I sent a message to Mailman 3 from mutt. I think that this message had no unixfrom header in "email.message.Message". The log file showed an exception thrown at "mailman/cure/runner.py".

The exception "AttributeError: class MIMEMultipart has no attribute 'sender'" was caused because "_process_one_file()" of "runner.py" accesses "mailman.email.message.Message.sender" without any validation. The loaded, pickled file contained a "MIMEMultipart" object, the other one a "email.message.Message" as far as I can remember.

I have attached a patch that ensures that "runner.py" is handling the expected Mailman "Message" instance but I think this was not the root of the problem.

Hope it helps anyway.

Best regards and keep up the good work on Mailman 3

Tags: