David S. Miller wrote:
Matti Aarnio writes:
I am contemplating to periodically turn off the ECN bit to
let email out, but DaveM has veto there.
I veto, the whole point of moving to ECN was to make a statement and
get people to fix their kit.
We will remove these people, that's all
Richard Gooch wrote:
In fact, hopefully he's still in a dark mood, and he may take up the
suggestion to bounce mails of the following type:
- MIME encoded
- HTML encoded
- quoted printables (those stupid =20 things are particuarly hard to
read).
Surely it'd be better to get the list to
the FAQ
to reflect that we're now running ECN.
People have had plenty of warning. Think of it as a bonus that it
didn't happen back in February. They've had an extra 3 months to sort
something out.
The we'll turn it on in February warning is worth NOTHING in this
situation: February comes
Rogier Wolff wrote:
The we'll turn it on in February warning is worth NOTHING in this
situation: February comes and goes. March comes and goes. Everybody
who read the warning will think: Ok, so I must be fine.
A warning of the form: ECN will go on as soon as this message clears
the queues
On Tue, May 22, 2001 at 06:51:57AM -0500, Brent D. Norris wrote:
I veto, the whole point of moving to ECN was to make a statement and
get people to fix their kit.
Isn't this a problem though because the messge saying that ECN was enabled
was set after ECN was enabled? Thus these people
Matti Aarnio writes:
I am contemplating to periodically turn off the ECN bit to
let email out, but DaveM has veto there.
I veto, the whole point of moving to ECN was to make a statement and
get people to fix their kit.
We will remove these people, that's all.
Since HTML email also
Brent D. Norris writes:
I veto, the whole point of moving to ECN was to make a statement and
get people to fix their kit.
We will remove these people, that's all.
Isn't this a problem though because the messge saying that ECN was
enabled was set after ECN was enabled? Thus
I veto, the whole point of moving to ECN was to make a statement and
get people to fix their kit.
Isn't this a problem though because the messge saying that ECN was enabled
was set after ECN was enabled? Thus these people have no idea what is
going on and they probably won't know what to fix
PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: ECN is on!
Rogier Wolff wrote:
The we'll turn it on in February warning is worth NOTHING in this
situation: February comes and goes. March comes and goes. Everybody
who read the warning will think: Ok, so I must be fine
FOLKS, I HAVE ALL THE TIME USED 'Reply-To:' HEADER POINTING
TO linux-kernel -- INSTEAD OF ALL THE LISTS...
If you want to continue this, do it there.
(Before I decide to taboo Re: ECN is on! subject line..)
On Tue, May 22, 2001 at 12:23:29PM -0400, Richard Gooch wrote:
...
Well
Matti Aarnio writes:
I am contemplating to periodically turn off the ECN bit to
let email out, but DaveM has veto there.
I veto, the whole point of moving to ECN was to make a statement and
get people to fix their kit.
We will remove these people, that's all.
Later,
David S. Miller
[EMAIL
Richard Gooch [EMAIL PROTECTED] writes:
Sure, Dave is being bloody-minded, but that's the only way we'll see
people get off their fat, lazy asses and fix their broken systems.
In fact, hopefully he's still in a dark mood, and he may take up the
suggestion to bounce mails of the following
... and immediately I have been able to verify a bunch of
domains/servers which won't get thru when incoming connection
has ECN.I tested all of these with Linux running ECN, and
Solaris 2.6 without ECN. When Solaris got connection, and
ECN-Linux didn't, domain and its server got listed
13 matches
Mail list logo