>>>>> "sjt" == Stephen J Turnbull >>>>> "Re: [Mailman-Users] GMane?" >>>>> Thu, 16 Feb 2006 15:56:46 +0900
>>>>> "jam" == John A Martin <[EMAIL PROTECTED]> writes:
sjt> I missed at least one of your posts, receiving Brad's reply
sjt> to it almost 24 hours in advance of your post. Even today
sjt> this is common for netnews.
Sorry, Gmane is not netnews. Gmane is not Usenet.
The Mailman-* lists were removed from Gmane at least two days before I
sent anything (recently) to this list. By what mechanism do you
suppose Gmane could have caused mail to be delayed or received out of
order after the list was removed?
JFTR after the first two mails I sent this list Wednesday,
To: mailman-users@python.org
References: <[EMAIL PROTECTED]>
Date: Wed, 15 Feb 2006 11:24:33 -0500
Message-ID: <[EMAIL PROTECTED]>
To: Brad Knowles <[EMAIL PROTECTED]>
Cc: John Swartzentruber <[EMAIL PROTECTED]>,
mailman-users@python.org
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Date: Wed, 15 Feb 2006 12:46:23 -0500
In-Reply-To: <[EMAIL PROTECTED]>
(Brad Knowles's message of
"Wed, 15 Feb 2006 18:21:08 +0100")
Message-ID: <[EMAIL PROTECTED]>
did not appear on the list for some time, I poked around saved monthly
reminders and realized that I was subscribed to this list with an
address at which I currently receive mail but at which I have not sent
mail for some time. I changed my subscription on the list web
interface and eventually received the mail confirmation request and
did the confirmation on the web interface.
Using my newly subscribed sending address I resent the first mail
indicated above which carried the following pertinent header fields to
the list.
Delivered-To: [EMAIL PROTECTED]
Received: from bag.python.org (bag [127.0.0.1])
by bag.python.org (Postfix) with ESMTP id 893591E400A
for <mailman-users@python.org>;
Wed, 15 Feb 2006 23:51:15 +0100 (CET)
Resent-Date: Wed, 15 Feb 2006 17:51:11 -0500
Resent-Message-ID: <[EMAIL PROTECTED]>
From: "John A. Martin" <[EMAIL PROTECTED]>
To: mailman-users@python.org
References: <[EMAIL PROTECTED]>
Date: Wed, 15 Feb 2006 11:24:33 -0500
In-Reply-To: <[EMAIL PROTECTED]>
(John Swartzentruber's message of
"Wed, 15 Feb 2006 09:41:02 -0500")
Message-ID: <[EMAIL PROTECTED]>
Not wishing to annoy Brad Knowles or John Swartzentruber with
additional copies of my second mail to the list I made a new mail (new
Message-ID (and new PGP signature)) with a single Header-Recipient and
the same Header-Date and the same content as the mail I had sent about
five hours and 10 minutes earlier.
Delivered-To: [EMAIL PROTECTED]
Received: from bag.python.org (bag [127.0.0.1])
by bag.python.org (Postfix) with ESMTP id 4A7171E4024
for <mailman-users@python.org>;
Wed, 15 Feb 2006 23:56:37 +0100 (CET)
Received: from athene.jamux.com (athene.jamux.com [65.222.215.34])
by bag.python.org (Postfix) with ESMTP
for <mailman-users@python.org>;
Wed, 15 Feb 2006 23:56:36 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
by athene.jamux.com (Postfix) with ESMTP id 027472F445
for <mailman-users@python.org>;
Wed, 15 Feb 2006 17:56:36 -0500 (EST)
From: "John A. Martin" <[EMAIL PROTECTED]>
To: mailman-users@python.org
In-Reply-To: <[EMAIL PROTECTED]>
(Brad Knowles's message of
"Wed, 15 Feb 2006 18:21:08 +0100")
Date: Wed, 15 Feb 2006 12:46:23 -0500
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
The above are I believe the most pertinent header fields but I expect
that any subscriber to this list can see the full header if they wish.
I expect also that anybody who cares to look will see that Brad's
response to my Message-ID: <[EMAIL PROTECTED]>, (not a
response to my <[EMAIL PROTECTED]>) was received by
bag.python.org at Feb 2006 18:58:30 +0100 (CET) which, by my
calculation is about two minutes shy of being five hours ahead of when
my Message-ID:<[EMAIL PROTECTED]> was received.
Delivered-To: [EMAIL PROTECTED]
Received: from bag.python.org (bag [127.0.0.1])
by bag.python.org (Postfix) with ESMTP id 85D4C1E4007
for <mailman-users@python.org>;
Wed, 15 Feb 2006 18:58:30 +0100 (CET)
Message-Id: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Date: Wed, 15 Feb 2006 18:57:24 +0100
To: "John A. Martin" <[EMAIL PROTECTED]>
From: Brad Knowles <[EMAIL PROTECTED]>
Cc: Brad Knowles <[EMAIL PROTECTED]>,
mailman-users@python.org,
John Swartzentruber <[EMAIL PROTECTED]>
It looks to me as if my clumsiness coming out of long lurking accounts
for about 5 hours in the delay of almost 24 hours that you observe
between receipt of Brad's answer and my question. (Extreme Top
Posting? :))
I am at a loss however to understand any of this being attributable to
or in any way related to netnews or to Gmane. Perhaps you would be
kind enough to show the evidence upon which you base this connection?
Hmm... maybe we have stumbled upon a new watch-word: "When in doubt,
Blame Gmane". Has a nice ring to it, no?
sjt> Gmane started its service for no apparent reason without
sjt> notifying anyone,
Lars should have consulted you in 2002 before offering a mailing list
archive to The Net, right?
sjt> they stopped it for no apparent reason
?!?
You mean Gmane stopped carrying the mailman-* lists?
Lars said, "The mailman people requested that they be removed", see
<http://article.gmane.org/gmane.discuss/9291>.
sjt> without notifying anyone.
See <http://article.gmane.org/gmane.discuss/9293>. Perhaps this is
not an everyday occurrence?
sjt> They have a history of being an attractive nuisance
sjt> (publishing email addresses and other spam-facilitating
sjt> activities). It's fundamentally irresponsible, but that is
sjt> the way they operate.
Did you have a similar view of Altavista ten years or so ago?
List owners (or more accurately, whoever subscribes a list to Gmane)
have a number of choices (Posting allowed, Read only, List member only
posting, No posting through Gmane, Encrypt addresses, Spam tagging,
and more). ISTM choosing the appropriate posting option and encrypted
address would go a long way toward reducing the nuisances.
Gmane is a Free Public Service. Like the man said, "If it cannot be
abused, it is not free". Such is the world.
Blame Gmane because bad people use it. :)
sjt> although I don't use Gmane and consider their operation to be
sjt> irresponsible, I'm moderately in favor of allowing them to
sjt> gateway the Mailman lists for the convenience it apparently
sjt> affords many users.
Good.
I have suggested to list owners that sooner or later someone will
likely subscribe their list to Gmane. This is because it is there and
there are folks that like to use it. To make the best of it I suggest
that list owners might want to subscribe their lists themselves and
perhaps get a better place (name) in the Gmane hierarchy but, most
importantly, so they can choose the options themselves. Also they can
more easily copy old archives to Gmane.
sjt> the Mailman list admins should be free not to use Gmane, or
sjt> to require Gmane improvements as a condition of using Gmane,
It is not as if Lars or his minions are trying to persuade anyone in
particular to subscribe a particular list. List subscribers are
likely sooner or later to try to subscribe a list, or persuade a list
owner to do so, unless steps are taken to prevent it.
sjt> The fact that Gmane *re*subscribed to Mailman lists in
sjt> violation of both their own policy and a previous request to
sjt> cease and desist speaks volumes for the risks and their lack
sjt> of respect for others' privacy, IMHO.
Do you really think anyone at Gmane subscribed the mailman-* lists?
Don't you imagine that someone, probably a subscriber, subscribed the
list?
Lars said he had made a mistake. See
<http://article.gmane.org/gmane.discuss/9291>.
jam
pgpttzsExwenD.pgp
Description: PGP signature
------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
