HTTP 500 error when saving changes to Message Acceptance settings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Postorius |
In Progress
|
Undecided
|
Unassigned |
Bug Description
Hello,
I installed Mailman 3 and Postorius on CentOS 7, via the packages available at this repo:
https:/
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_
This is the error in the Postorius log:
[20/May/2015 19:59:35] "POST /postorius/
This is the output from mailman.log:
May 20 20:59:35 2015 (12584) 127.0.0.1 - - "PATCH /<email address hidden>/config HTTP/1.1" 400 2
Here is the trace output from the error:
*******
Environment:
Request Method: POST
Request URL: http://
Django Version: 1.6.11
Python Version: 2.7.5
Installed Applications:
('django.
'django.
'django.
'django.
'django.
'django.
'django.
'postorius',
'django_
Installed Middleware:
('django.
'django.
'django.
'django.
'django.
'django.
Traceback:
File "/usr/lib/
112. response = wrapped_
File "/usr/lib/
58. return fn(*args, **kwargs)
File "/usr/lib/
787. except HTTPError as e:
Exception Type: UnboundLocalError at /postorius/
Exception Value: local variable 'HTTPError' referenced before assignment
*********
Let me know what other information you need, or how I can help diagnose this issue.
Changed in postorius: | |
status: | New → In Progress |
assignee: | nobody → Florian Fuchs (flo-fuchs) |
information type: | Public → Public Security |
information type: | Public Security → Public |
Changed in postorius: | |
assignee: | Florian Fuchs (flo-fuchs) → nobody |
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.