On April 23 Mark Sapiro wrote:
| I am happy to announce the release of Mailman 2.1.10.
I have discovered a few problems with the release. None is a major show
stopper, but the most significant so far is that I broke cmd_subscribe
so that email subscribe to the -subscribe or -join address or the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Sapiro wrote:
| I am happy to announce the release of Mailman 2.1.10.
I have discovered a few problems with the release. None is a major show
stopper, but the most significant so far is that I broke cmd_subscribe
so that email subscribe to the
Brad Knowles wrote:
On 4/21/08, Brad Knowles wrote:
I have applied the patch to my installation and I'm sure it's good, but
I haven't seen any unparseable messages.
I haven't seen any more unparseable messages in the last few minutes,
but let's see how things go.
We've now had a
Brad Knowles wrote:
Going back to Jun 12 23:48:51 2007, it looks like we've had a total
of about 378,989 unparseable messages, although we only have just
over 8000 messages in the mailman/qfiles/shunt and
mailman/qfiles/shunt.old directories (7759 .psv files, and 312 .pck
files).
There are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am happy to announce the release of Mailman 2.1.10.
This is a security and bug fix release and it is highly recommended
that all sites upgrade to this version. Mailman 2.1.10 also adds support
for three new language translations, Galician, Hebrew
On Mon, Apr 21, 2008 at 3:50 PM, Mark Sapiro [EMAIL PROTECTED] wrote:
Note: If you are not ready to upgrade, patches for these two issues
are available at
http://sourceforge.net/project/showfiles.php?group_id=103
in the 2.1.9 file list.
THANK YOU!
-Jim P.
Mark Sapiro wrote:
I am happy to announce the release of Mailman 2.1.10.
Now running on mail.python.org. Please let us know if there are any problems.
--
Brad Knowles [EMAIL PROTECTED]
LinkedIn Profile: http://tinyurl.com/y8kpxu
--
Mark Sapiro wrote:
I am happy to announce the release of Mailman 2.1.10.
Congratulations!
I presume the usual upgrade instructions apply?
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.014.htp
dn
--
Mailman-Users mailing list
Mark Sapiro wrote:
I am happy to announce the release of Mailman 2.1.10.
This is a security and bug fix release and it is highly recommended
that all sites upgrade to this version. Mailman 2.1.10 also adds support
for three new language translations, Galician, Hebrew and Slovak and a
few new
David Newman wrote:
I presume the usual upgrade instructions apply?
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.014.htp
For upgrading python.org, I made the mistake of leaving Mailman running even
though I had shut down postfix and apache, and it still worked okay. I'd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 21, 2008, at 5:28 PM, Brad Knowles wrote:
Mark Sapiro wrote:
I am happy to announce the release of Mailman 2.1.10.
Now running on mail.python.org. Please let us know if there are any
problems.
Wow, awesome Brad. Thanks!
- -Barry
Brad Knowles wrote:
Remind me next time that we *MUST* upgrade to the betas and RCs on
python.org once you've made them available. The changes made to the code
which supports skipping unparseable messages means that mmdsr has to be
changed to suit, otherwise you could wind up with a daily
David Newman wrote:
I presume the usual upgrade instructions apply?
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.014.htp
Those are really somewhat outdated. I probably should have just
replaced them, but I created a new FAQ
Mark Sapiro wrote:
Note that in addition to the logging change for unparseable messages,
they will now be saved in the shunt queue, so if you have a lot,
you'll have to deal with that too.
These are the *.psv files? Yeah, we've got almost 8000 of them on
python.org. Do you have any
Brad Knowles wrote:
Mark Sapiro wrote:
Note that in addition to the logging change for unparseable messages,
they will now be saved in the shunt queue, so if you have a lot,
you'll have to deal with that too.
These are the *.psv files? Yeah, we've got almost 8000 of them on
python.org. Do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Sapiro wrote:
|
| I think the best solution is to turn off the preservation of
| unparseable messages, and add an mm_cfg.py setting to turn it on. I
| can work up a patch.
|
A patch is attached. It doesn't turn off preservation by default
On 4/21/08, Mark Sapiro wrote:
If you could apply this patch (you can apply it directly to the
installation directory, by e.g.
cd /usr/local/mailman
patch -p0 path/to/2.1.10.patch.txt
Patch applied fine, no complaints.
and set
QRUNNER_SAVE_BAD_MESSAGES = No
Done.
in mm_cfg.py
On 4/21/08, Brad Knowles wrote:
I have applied the patch to my installation and I'm sure it's good, but
I haven't seen any unparseable messages.
I haven't seen any more unparseable messages in the last few minutes,
but let's see how things go.
We've now had a couple of unparseable
18 matches
Mail list logo
