On Fri, 2003-10-17 at 12:27, Marc MERLIN wrote:
I just wanted to report that one of my mailman servers was also hit
by this bug.
All mails to the list were stopped until I applied the patch (i.e. the
shunted messages weren't the problem, new test messages weren't going
through)
The bug is
On Fri, Oct 17, 2003 at 12:31:48PM -0400, Barry Warsaw wrote:
On Fri, 2003-10-17 at 12:27, Marc MERLIN wrote:
I just wanted to report that one of my mailman servers was also hit
by this bug.
All mails to the list were stopped until I applied the patch (i.e. the
shunted messages weren't
On Fri, 2003-10-17 at 12:34, Marc MERLIN wrote:
Oops, forgot the most important.
I upgraded to cvs (2.2a0) and the problem was still there.
The patch applied to 2.2a0 and fixed the problem
Okay, that's bad. ;)
BTW, I should mention that if you're running your production servers
from CVS, I
I seem to recall that one of the original motivations for SpamBayes was to
support spam filtering within Mailman (or nearby, if not within). Has
anyone taken steps to more tightly integrate the two aside from doing
something like running sb_filter.py in front of Mailman's processing? I
think
On Fri, 2003-10-17 at 15:15, Skip Montanaro wrote:
I'd consider taking a look at the problem on my own, but I've never even
peeked at the Mailman code and don't have any idea where to plug SpamBayes
into it. I do know the SpamBayes code to a certain degree and would be
happy to work with
I was just about to report this, so here goes...
On Fri, 2003-10-17 at 18:41, Barry Warsaw wrote:
On Fri, 2003-10-17 at 12:34, Marc MERLIN wrote:
Oops, forgot the most important.
I upgraded to cvs (2.2a0) and the problem was still there.
The patch applied to 2.2a0 and fixed the
On Fri, 2003-10-17 at 16:34, Daniel Buchmann wrote:
Unfortunately, there is a bug when upgrading lists (at least from MM
2.1.2) to the Release_2_1-maint branch.
It seems to be caused by the latest SYNC_AFTER_WRITE patch:
Whenever a file ending in .in changes (e.g. Defaults.py.in) you must at
On Fri, 2003-10-17 at 22:46, Barry Warsaw wrote:
On Fri, 2003-10-17 at 16:34, Daniel Buchmann wrote:
Unfortunately, there is a bug when upgrading lists (at least from MM
2.1.2) to the Release_2_1-maint branch.
It seems to be caused by the latest SYNC_AFTER_WRITE patch:
Whenever a file
That reminds me... I have a couple lists that would benefit from TMDA-fronting
them. Is there any info on how to do this (especially with Postfix)?
Bob
-- Original Message ---
From: Barry Warsaw [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Fri, 17 Oct 2003 15:19:45 -0400