On Tue, 27 Feb 2001 08:17:10 -0700
Matthew Seidl <[EMAIL PROTECTED]> wrote:
> Over the weekend one of the uesers on one of my lists had both
> their DNS servers go down. This means that any attempt to deliver
> mail to them had a 4 minute DNS failure timeout.
> This went fine, till about 5 mes
> "CR" == Chris Ryan <[EMAIL PROTECTED]> writes:
CR> Do you have a timeframe on when the next big commit is going
CR> to be?
Sometime today or tomorrow.
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/
Do you have a timeframe on when the next big commit is going to be?
Thanks in advance.
Chris Ryan
[EMAIL PROTECTED]
"Barry A. Warsaw" wrote:
>
> > "CR" == Chris Ryan <[EMAIL PROTECTED]> writes:
>
> CR> Does anyone know how this should be fixed or what I did wrong?
> CR> I have the
> "CR" == Chris Ryan <[EMAIL PROTECTED]> writes:
CR> Does anyone know how this should be fixed or what I did wrong?
CR> I have the latest of mimelib 0.2 installed.
I'd say wait until the next huge round of checkins. I've got lots of
fixes for cvs problems waiting in the wings.
-Ba
I setup the latest of mailman from cvs yesterday and I'm having some
difficulty getting it all working.
My first problem was with /scripts/mailcmd on line 49:
print >> sys.stderr 'Mailman error: mailcmd got bad listname: %s\n%s' \
^ -- missing comma after sys.stderr
I also h
> "MS" == Matthew Seidl <[EMAIL PROTECTED]> writes:
MS> It seems to me that qrunner should at least try messages in a
MS> most recent first order, instead of oldest first. But that
MS> might still lead to starvation of some messages in the queue.
The easiest fix is to add a `sh
Over the weekend one of the uesers on one of my lists had both their
DNS servers go down. This means that any attempt to deliver mail to
them had a 4 minute DNS failure timeout.
This went fine, till about 5 messages for them accumulated in the
qfiles directory. Then each qrunner that started u
