Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#56865 - [mailman] "invalid cgi response" when trying to login to the admin page of mailing lists

Attached to Project: Community Packages
Opened by David Runge (dvzrv) - Monday, 25 December 2017, 23:04 GMT
Last edited by David Runge (dvzrv) - Sunday, 28 January 2018, 20:33 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To S├ębastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Description: mailman 2.1.25 produces an "invalid CGI response !!!" error (i.e. 504) when trying to login to the admin page of mailing lists.
This happens when using the standard uwsgi socket/service to serve the mailman cgi scripts and therefore also affects subscribing and private archives.

Downgrading mailman to 2.1.24 fixes the issue.

Additional info:
* mailman 2.1.25-1
* uwsgi 2.0.15-7
* access/error logs of nginx and uwsgi/mailman journal output in attachment

Steps to reproduce:
* start mailman
* access a mailing list's admin page and try to log in (or subscribe or login to a private archive)
This task depends upon

Closed by  David Runge (dvzrv)
Sunday, 28 January 2018, 20:33 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 2.1.25-21
Comment by S├ębastien Luttringer (seblu) - Friday, 29 December 2017, 12:46 GMT
uswgi is not part of mailman and I have no problem displaying this page with fcgiwrap.
Comment by David Runge (dvzrv) - Friday, 29 December 2017, 13:39 GMT
Well, neither is fcgiwrap.

As downgrading mailman (and not uwsgi and its plugins) fixed this for me, I have the feeling it is mailman related, but maybe I'm wrong.
Is there something else I can supply to make this more reproducable for you?
Comment by David Runge (dvzrv) - Monday, 22 January 2018, 15:34 GMT Comment by David Runge (dvzrv) - Saturday, 27 January 2018, 18:31 GMT
Patching src/common.c fixes this (they restricted the allowed CGI params massively between 2.1.24 and 2.1.25).
Comment by David Runge (dvzrv) - Sunday, 28 January 2018, 20:13 GMT
As this is a major blocker for mailman behind nginx, I'll go ahead and patch this for 2.1.25.
However, this change will be included in 2.1.26, so the patch can be removed after that!