From: David Ford <david@blue-labs.org>
To: Holger Lubitz <h.lubitz@internet-factory.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ECN: Volunteers needed
Date: Fri, 11 May 2001 10:17:59 -0700 [thread overview]
Message-ID: <3AFC1EC7.7020805@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0105091559260.27312-100000@netcore.fi> <Pine.LNX.4.21.0105091249520.23642-100000@scotch.homeip.net> <9dbvh7$amg$1@cesium.transmeta.com> <3AFA8FD7.4B7C14A0@internet-factory.de>
I simply crontab an ECN off period for five minutes every hour and flush
the mail queue.
David.
Holger Lubitz wrote:
>"H. Peter Anvin" wrote:
>
>>I suspect that the main way to get this thing fixed is to make sure
>>ECN is enabled on the server side; for example, we have turned on ECN
>>on kernel.org. If a user is using a broken software stack, it's their
>>loss, not ours.
>>
>
>This is what we do here, too. The only exceptions: Our mail server
>(needs to deliver mail, even to broken sites) and our web proxy server
>(also needs to connect to broken sites sometimes). Everything else is
>ECN enabled. And this is the approach I'd suggest to anybody running 2.4
>servers.
>
next prev parent reply other threads:[~2001-05-11 17:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 2:31 ECN: Volunteers needed jamal
2001-05-09 2:41 ` David S. Miller
2001-05-09 2:45 ` jamal
2001-05-09 2:48 ` jamal
2001-05-09 2:52 ` Billy Harvey
2001-05-09 11:44 ` Matthew Geier
2001-05-09 13:34 ` Pekka Savola
2001-05-09 16:58 ` God
2001-05-09 17:41 ` H. Peter Anvin
2001-05-10 12:55 ` Holger Lubitz
2001-05-11 17:17 ` David Ford [this message]
2001-05-10 22:23 ` Michel Eyckmans (MCE)
2001-05-09 13:38 ` Gregory Maxwell
2001-05-09 14:10 ` Horst von Brand
2001-05-09 14:25 ` Gregory Maxwell
2001-05-09 17:08 ` God
2001-05-09 19:03 ` Gregory Maxwell
2001-05-09 19:23 ` ECN: Volunteers needed :: AOL ::: Spam filter God
-- strict thread matches above, loose matches on Subject: below --
2001-05-09 3:16 ECN: Volunteers needed Sally Floyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3AFC1EC7.7020805@blue-labs.org \
--to=david@blue-labs.org \
--cc=h.lubitz@internet-factory.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.