Mark Sapiro:
There is a CSRF vulnerability ...
I have developed a fix...
I'm delaying the release ...
Hello,
don't understand why you wait? Yes some people may need time to plan a update.
But there are also people not needing such plan. They could use the
patch just now.
But maybe you
Mark Sapiro:
I am pleased to announce the release of Mailman 2.1.25.
Hello,
this version contain a fix for LP#1696066 that work for most postfix users.
But not for me :-/
postfix know different types of maps:
http://www.postfix.org/DATABASE_README.html#types
the corresponding files have
Ye Xiaoxing:
To Q1, you may look at the code of mailmanctl
https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/bin/mailmanctl . When you are running using `mailmanctl start`, it actually forks more processes for qrunners - maybe you can modify it somehow and write a watcher
Hello,
I'm porting a mailman installation from a legacy server into docker.
To make it not more complicated I decided to stay on the same mailman
version 2.1.29 (build from source)
Now I'm faced to the problem that mailman is started with "mailmanctl start"
This fork a daemon running in
Zitat von Jim Popovitch jim...@gmail.com:
... that mailing lists, like MTAs, have no business modifying the
From header;
I fully agree with these opinions an like to add should not modify
the messagebody
nor should mailing lists accept mail that they knowingly can't reflect.
reflect is
Bob Puff:
So guys... Is there a simple little hack we can do within MM 2.1 to try to
mitigate this issue, by adding .invalid or some other extension? I've got a
few lists that are getting to the point where MM sends the probe email, and
then figures it is not a bouncing address, but a lot of
Murray S. Kucherawy:
And along those lines, do any MUAs do useful things with the various List-*
fields, other than permitting one to sort on them?
Hello,
I think, that is the real problem: There are RFCs 2369 and 2919 and
virtually no MUA
implement them *usefull*.
I do sort my inbound
