Re: new mailman for FC2, security, fixes password retreval vulnerability

[Phil Anderson]

On Thu, 2004-07-01 at 16:36 -0400, John Dennis wrote:
> Some users have reported problems with bad queue counts after
> upgrading to version 2.1.5, the operating assumption is this was
> caused by performing an install while mailman was running. Prior to
> installing this rpm stop the mailman service via:
>
> % /sbin/service mailman stop
>
> Then after installation completes restart the service via:
>
> % /sbin/service mailman start

I stopped mailman on my server before applying the update, but I was
still greeted with 300 messages this morning informing me that I had -1
messages pending.

Anyone know how I can reset the counters on the lists?

Thanks,
Phil

new mailman for FC2, security, fixes password retreval vulnerability

[Bradley Tate]

Me too. If anyone has a solution to this problem I'd also appreciate 
hearing about it.

Thanks,
Bradley.

Phil Anderson wrote:
> On Thu, 2004-07-01 at 16:36 -0400, John Dennis wrote:
> > Some users have reported problems with bad queue counts after
> > upgrading to version 2.1.5, the operating assumption is this was
> > caused by performing an install while mailman was running. Prior to
> > installing this rpm stop the mailman service via:
> >
> > % /sbin/service mailman stop
> >
> > Then after installation completes restart the service via:
> >
> > % /sbin/service mailman start
>
> I stopped mailman on my server before applying the update, but I was
> still greeted with 300 messages this morning informing me that I had -1
> messages pending.
>
> Anyone know how I can reset the counters on the lists?
>
> Thanks,
> Phil

new mailman for FC2, security, fixes password retreval vulnerability

[Phil Anderson]

On Fri, 2004-07-09 at 00:58 +1000, Bradley Tate wrote:
> Me too. If anyone has a solution to this problem I'd also appreciate 
> hearing about it.

John Denis from Redhat sent this to me and the list, but for some reason
it didn't come through on the list.  I have been running with this patch
on for the last 5 days, and it fixed the problem.

On Sat, 2004-07-03 at 11:51 -0400, John Dennis wrote:
Jim Tittsler kindly provided this exmplanation to me.
I have not yet had a chance to investigate, but it may help you.

It is because it assumes there is always at least one dummy
entry in the admin queue (containing the version number).  A
patch to fix the problem is on SourceForge:

http://sourceforge.net/tracker/index.php?func=detail&aid=970383&group_id=103&at
id=300103