HTTP 500 error when saving changes to Message Acceptance settings

Bug #1457271 reported by Josh Farwell
This bug affects 3 people
Affects Status Importance Assigned to Milestone
In Progress

Bug Description


I installed Mailman 3 and Postorius on CentOS 7, via the packages available at this repo:

I am using the default Postorius configuration. I am running Postorius using the provided development Django project from bzr. I have configured a domain that isn't real and a test list. Mailman has access to an outgoing MTA but the MTA can't send mail back via LMTP, at least at the moment.

I encountered an error when I attempted to change the test list's settings for Message Acceptance. When I try to save my change in settings, for any setting on that page, I get an error.

I was able to successfully change settings on that page (setting default_member_action to "accept", specifically) by using the Python REST client. I directly changed the value and ran .save() and everything looked correct and there were no errors.

This is the error in the Postorius log:

[20/May/2015 19:59:35] "POST /postorius/lists/testlist.mail.local/settings/message_acceptance HTTP/1.1" 500 78853

This is the output from mailman.log:

May 20 20:59:35 2015 (12584) - - "PATCH /<email address hidden>/config HTTP/1.1" 400 2

Here is the trace output from the error:



Request Method: POST
Request URL:

Django Version: 1.6.11
Python Version: 2.7.5
Installed Applications:
Installed Middleware:

File "/usr/lib/python2.7/site-packages/django/core/handlers/" in get_response
  112. response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/usr/lib/python2.7/site-packages/postorius/auth/" in wrapper
  58. return fn(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/postorius/views/" in list_settings
  787. except HTTPError as e:

Exception Type: UnboundLocalError at /postorius/lists/testlist.mail.local/settings/message_acceptance
Exception Value: local variable 'HTTPError' referenced before assignment


Let me know what other information you need, or how I can help diagnose this issue.

Revision history for this message
Florian Fuchs (flo-fuchs) wrote :

The reason for this is an improper handling of an empty "acceptable_aliases" response. I am working on a fix for this. In the meantime (if you don't need to actually set accepable_aliases) removing the "[]" from the "Acceptable Alias" field before submitting the form will do the trick.

Changed in postorius:
status: New → In Progress
assignee: nobody → Florian Fuchs (flo-fuchs)
frennkie (frennkie)
information type: Public → Public Security
information type: Public Security → Public
Changed in postorius:
assignee: Florian Fuchs (flo-fuchs) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.