I encounter something that looks exactly like this bug using Mailman 2.1.9 (specifically, the Debian mailman package 1:2.1.9-7). Any chance it got broken again?
I encounter something that looks exactly like this bug using Mailman 2.1.9 (specifically, the Debian mailman package 1:2.1.9-7). Any chance it got broken again?