Re: [Nanog-futures] Announce list: Re: Hughes Network
On Thu, May 22, 2008 at 9:35 PM, someone wrote:
Add me to the list of never-saw-that. In addition, I just checked the nanog archives, and there isn't an announcement of that type in the archives.
Below is the full email, with headers, from Monday. Hopefully it will put this issue to rest.... but somehow I doubt that. ;-) -Jim P. Received: by 10.90.53.15 with SMTP id b15cs245753aga; Mon, 19 May 2008 16:02:48 -0700 (PDT) Received: by 10.35.10.13 with SMTP id n13mr12798008pyi.30.1211238167720; Mon, 19 May 2008 16:02:47 -0700 (PDT) Return-Path: <nanog-announce-bounces@nanog.org> Received: from s0.nanog.org (s0.nanog.org [198.108.95.20]) by mx.google.com with ESMTP id s59si4779396pyh.13.2008.05.19.16.02.47; Mon, 19 May 2008 16:02:47 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of nanog-announce-bounces@nanog.org designates 198.108.95.20 as permitted sender) client-ip=198.108.95.20; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of nanog-announce-bounces@nanog.org designates 198.108.95.20 as permitted sender) smtp.mail=nanog-announce-bounces@nanog.org Received: from localhost ([127.0.0.1] helo=s0.nanog.org) by s0.nanog.org with esmtp (Exim 4.68 (FreeBSD)) (envelope-from <nanog-announce-bounces@nanog.org>) id 1JyENK-0006V5-UV; Mon, 19 May 2008 23:02:38 +0000 Received: from ind-iport-1.cisco.com ([64.104.129.195]) by s0.nanog.org with esmtp (Exim 4.68 (FreeBSD)) (envelope-from <pfs@cisco.com>) id 1JyENI-0006UC-1L for nanog-announce@nanog.org; Mon, 19 May 2008 23:02:36 +0000 X-IronPort-AV: E=Sophos;i="4.27,512,1204482600"; d="scan'208";a="107943185" Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by ind-iport-1.cisco.com with ESMTP; 20 May 2008 04:32:33 +0530 Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4JN2XlM012133 for <nanog-announce@nanog.org>; Tue, 20 May 2008 07:02:33 +0800 Received: from Philip-PB.local (sin-vpn-client-20-47.cisco.com [10.68.20.47]) by hkg-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4JN2WVp007247 for <nanog-announce@nanog.org>; Mon, 19 May 2008 23:02:32 GMT Message-ID: <48320722.70807@cisco.com> Date: Tue, 20 May 2008 09:02:58 +1000 From: Philip Smith <pfs@cisco.com> Organization: Cisco Systems User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: nanog-announce@nanog.org X-Enigmail-Version: 0.95.6 Authentication-Results: hkg-dkim-1; header.From=pfs@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim1002 verified; ); Subject: [NANOG-announce] email subject tags and footers X-BeenThere: nanog-announce@nanog.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: NANOG-Announce <nanog-announce.nanog.org> List-Unsubscribe: <http://mailman.nanog.org/mailman/listinfo/nanog-announce>, <mailto:nanog-announce-request@nanog.org?subject=unsubscribe> List-Archive: <http://mailman.nanog.org/pipermail/nanog-announce> List-Post: <mailto:nanog-announce@nanog.org> List-Help: <mailto:nanog-announce-request@nanog.org?subject=help> List-Subscribe: <http://mailman.nanog.org/mailman/listinfo/nanog-announce>, <mailto:nanog-announce-request@nanog.org?subject=subscribe> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: nanog-announce-bounces@nanog.org Hi everyone, Following the discussion on nanog-futures, we'd like to let you all know that the [NANOG] in the subject line and the three extra info lines mailman appends will be dropped from all future messages going to the NANOG list, starting in around 24 hours from now. If any of you have you changed your <nanog@nanog.org> e-mail filtering to depend on the [NANOG] subject tag, please consider this 24 hours notice to move to another message filtering technique. Best wishes, philip (for the SC) -- _______________________________________________ NANOG-announce mailing list NANOG-announce@nanog.org http://mailman.nanog.org/mailman/listinfo/nanog-announce
The announcement was made to nanog-announce, but not to nanog. I would expect that there are scads more readers of nanog than of nanog announce. For some, that could cause unexpected results, especially with the 24 hour notice. Corroborative detail below. (Oops, top posting) Regards. On May 22, 2008, at 10:45 PM, Jim Popovitch wrote:
On Thu, May 22, 2008 at 9:35 PM, someone wrote:
Add me to the list of never-saw-that. In addition, I just checked the nanog archives, and there isn't an announcement of that type in the archives.
Below is the full email, with headers, from Monday. Hopefully it will put this issue to rest.... but somehow I doubt that. ;-)
-Jim P. <snip/> MIME-Version: 1.0 To: nanog-announce@nanog.org X-Enigmail-Version: 0.95.6 Authentication-Results: hkg-dkim-1; header.From=pfs@cisco.com; dkim=pass ( <snip> philip (for the SC) --
_______________________________________________ NANOG-announce mailing list NANOG-announce@nanog.org http://mailman.nanog.org/mailman/listinfo/nanog-announce
James R. Cutler james.cutler@consultant.com
Everyone, The main nanog list is subscribed to nanog-announce. So everything sent to nanog-announce should appear on the nanog list too. If folks choose to unsubscribe from the nanog list, they will need to subscribe to nanog-announce to carry on seeing announcements. Hope this clarifies at least this piece for everyone. Yes it seems as though my "subject tags" e-mail sent around 11pm UTC/GMT on Monday didn't get to some folks on the main list; I'll try and find out what happened there. philip SC Chair -- James R. Cutler said the following on 23/5/08 13:16:
The announcement was made to nanog-announce, but not to nanog. I would expect that there are scads more readers of nanog than of nanog announce.
For some, that could cause unexpected results, especially with the 24 hour notice.
Corroborative detail below. (Oops, top posting)
Regards.
On May 22, 2008, at 10:45 PM, Jim Popovitch wrote:
On Thu, May 22, 2008 at 9:35 PM, someone wrote:
Add me to the list of never-saw-that. In addition, I just checked the nanog archives, and there isn't an announcement of that type in the archives.
Below is the full email, with headers, from Monday. Hopefully it will put this issue to rest.... but somehow I doubt that. ;-)
-Jim P. <snip/> MIME-Version: 1.0 To: nanog-announce@nanog.org <mailto:nanog-announce@nanog.org> X-Enigmail-Version: 0.95.6 Authentication-Results: hkg-dkim-1; header.From=pfs@cisco.com <mailto:header.From=pfs@cisco.com>; dkim=pass ( <snip> philip (for the SC) --
_______________________________________________ NANOG-announce mailing list NANOG-announce@nanog.org <mailto:NANOG-announce@nanog.org> http://mailman.nanog.org/mailman/listinfo/nanog-announce
James R. Cutler james.cutler@consultant.com <mailto:james.cutler@consultant.com>
------------------------------------------------------------------------
_______________________________________________ Nanog-futures mailing list Nanog-futures@nanog.org http://mailman.nanog.org/mailman/listinfo/nanog-futures
On 22 May 2008, at 23:16, James R. Cutler wrote:
The announcement was made to nanog-announce, but not to nanog. I would expect that there are scads more readers of nanog than of nanog announce.
When I was sending things to nanog-announce, it was the case that mail to nanog-announce was sent to people who had specifically subscribed to that list, plus anybody who hadn't but who was subscribed to nanog (in other words, it was sent to the union of both lists). That might have changed since the transition to mailman. It seemed like a useful approach, though. Joe
Joe Abley wrote:
On 22 May 2008, at 23:16, James R. Cutler wrote:
The announcement was made to nanog-announce, but not to nanog. I would expect that there are scads more readers of nanog than of nanog announce.
When I was sending things to nanog-announce, it was the case that mail to nanog-announce was sent to people who had specifically subscribed to that list, plus anybody who hadn't but who was subscribed to nanog (in other words, it was sent to the union of both lists).
That might have changed since the transition to mailman. It seemed like a useful approach, though.
Kinda makes you wonder what the purpose on the announce list is though. Are there actually people subscribed to nanog-annouce that aren't subscribed to nanog? Sam
On Fri, 23 May 2008 14:59:15 +0100 Sam Stickland <sam_mailinglists@spacething.org> wrote:
Kinda makes you wonder what the purpose on the announce list is though. Are there actually people subscribed to nanog-annouce that aren't subscribed to nanog?
Perhaps not but it could be useful anyway. People may be subscribed to both lists but are filtering announce to a separate folder. That way they can skim the busier list but pay a bit more attention to the announce one. Maybe there are other possibilities. More options is generally better. I do agree though that announcements, especially any concerning other lists, should probably be duplicated on that list. -- D'Arcy J.M. Cain <darcy@druid.net> | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.
On May 23, 2008, at 9:59 AM, Sam Stickland wrote:
Joe Abley wrote:
On 22 May 2008, at 23:16, James R. Cutler wrote:
The announcement was made to nanog-announce, but not to nanog. I would expect that there are scads more readers of nanog than of nanog announce.
When I was sending things to nanog-announce, it was the case that mail to nanog-announce was sent to people who had specifically subscribed to that list, plus anybody who hadn't but who was subscribed to nanog (in other words, it was sent to the union of both lists).
That might have changed since the transition to mailman. It seemed like a useful approach, though.
Kinda makes you wonder what the purpose on the announce list is though.
IMHO the purpose is (or should be) that the posting-privileges for announce is limited, so that messages from that list about things like changes in format or meeting times can be treated as authoritative. Regards Marshall
Are there actually people subscribed to nanog-annouce that aren't subscribed to nanog?
Sam
I'm subscribed to both now. ;-) The advantage to the NANOG subject header was obviously it was resilient to e-mail address changes for the list. A nice attribute given e-mails now come in from both nanog@nanog.org and nanog@merit.edu addresses. Anyhow, I assume there was compelling reason for the change. -J --- Jason J. W. Williams COO/CTO, DigiTar http://www.digitar.com E: williamsjj@digitar.com V: 208-343-8520 M: 208-863-0727 F: 208-322-8520 XMPP: williamsjj@digitar.com -----Original Message----- From: Sam Stickland [mailto:sam_mailinglists@spacething.org] Sent: Friday, May 23, 2008 7:59 AM To: Joe Abley Cc: nanog; nanog-futures Subject: Re: [Nanog-futures] Announce list: Re: Hughes Network Joe Abley wrote:
On 22 May 2008, at 23:16, James R. Cutler wrote:
The announcement was made to nanog-announce, but not to nanog. I would expect that there are scads more readers of nanog than of nanog
announce.
When I was sending things to nanog-announce, it was the case that mail
to nanog-announce was sent to people who had specifically subscribed to that list, plus anybody who hadn't but who was subscribed to nanog (in other words, it was sent to the union of both lists).
That might have changed since the transition to mailman. It seemed like a useful approach, though.
Kinda makes you wonder what the purpose on the announce list is though. Are there actually people subscribed to nanog-annouce that aren't subscribed to nanog? Sam !SIG:4836ce2871591551116042!
On Fri, May 23, 2008 at 12:29 PM, Jason J. W. Williams <williamsjj@digitar.com> wrote:
I'm subscribed to both now. ;-) The advantage to the NANOG subject header was obviously it was resilient to e-mail address changes for the list. A nice attribute given e-mails now come in from both nanog@nanog.org and nanog@merit.edu addresses. Anyhow, I assume there was compelling reason for the change.
There are a plethera of common headers available for filtering, regardless of To: -Jim P.
Once upon a time, wasn't nanog@ subscribed to nanog-announce@ ? It appears to not be now. I went looking in my archives for that message-id; the only copy of that mail I got was from you, and I am on both -futures and the main list. Thanks for sending that along, Jim. ---Rob "Jim Popovitch" <yahoo@jimpop.com> writes:
On Thu, May 22, 2008 at 9:35 PM, someone wrote:
Add me to the list of never-saw-that. In addition, I just checked the nanog archives, and there isn't an announcement of that type in the archives.
Below is the full email, with headers, from Monday. Hopefully it will put this issue to rest.... but somehow I doubt that. ;-)
-Jim P.
Received: by 10.90.53.15 with SMTP id b15cs245753aga; Mon, 19 May 2008 16:02:48 -0700 (PDT) Received: by 10.35.10.13 with SMTP id n13mr12798008pyi.30.1211238167720; Mon, 19 May 2008 16:02:47 -0700 (PDT) Return-Path: <nanog-announce-bounces@nanog.org> Received: from s0.nanog.org (s0.nanog.org [198.108.95.20]) by mx.google.com with ESMTP id s59si4779396pyh.13.2008.05.19.16.02.47; Mon, 19 May 2008 16:02:47 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of nanog-announce-bounces@nanog.org designates 198.108.95.20 as permitted sender) client-ip=198.108.95.20; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of nanog-announce-bounces@nanog.org designates 198.108.95.20 as permitted sender) smtp.mail=nanog-announce-bounces@nanog.org Received: from localhost ([127.0.0.1] helo=s0.nanog.org) by s0.nanog.org with esmtp (Exim 4.68 (FreeBSD)) (envelope-from <nanog-announce-bounces@nanog.org>) id 1JyENK-0006V5-UV; Mon, 19 May 2008 23:02:38 +0000 Received: from ind-iport-1.cisco.com ([64.104.129.195]) by s0.nanog.org with esmtp (Exim 4.68 (FreeBSD)) (envelope-from <pfs@cisco.com>) id 1JyENI-0006UC-1L for nanog-announce@nanog.org; Mon, 19 May 2008 23:02:36 +0000 X-IronPort-AV: E=Sophos;i="4.27,512,1204482600"; d="scan'208";a="107943185" Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by ind-iport-1.cisco.com with ESMTP; 20 May 2008 04:32:33 +0530 Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4JN2XlM012133 for <nanog-announce@nanog.org>; Tue, 20 May 2008 07:02:33 +0800 Received: from Philip-PB.local (sin-vpn-client-20-47.cisco.com [10.68.20.47]) by hkg-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4JN2WVp007247 for <nanog-announce@nanog.org>; Mon, 19 May 2008 23:02:32 GMT Message-ID: <48320722.70807@cisco.com> Date: Tue, 20 May 2008 09:02:58 +1000 From: Philip Smith <pfs@cisco.com> Organization: Cisco Systems User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: nanog-announce@nanog.org X-Enigmail-Version: 0.95.6 Authentication-Results: hkg-dkim-1; header.From=pfs@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim1002 verified; ); Subject: [NANOG-announce] email subject tags and footers X-BeenThere: nanog-announce@nanog.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: NANOG-Announce <nanog-announce.nanog.org> List-Unsubscribe: <http://mailman.nanog.org/mailman/listinfo/nanog-announce>, <mailto:nanog-announce-request@nanog.org?subject=unsubscribe> List-Archive: <http://mailman.nanog.org/pipermail/nanog-announce> List-Post: <mailto:nanog-announce@nanog.org> List-Help: <mailto:nanog-announce-request@nanog.org?subject=help> List-Subscribe: <http://mailman.nanog.org/mailman/listinfo/nanog-announce>, <mailto:nanog-announce-request@nanog.org?subject=subscribe> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: nanog-announce-bounces@nanog.org
Hi everyone,
Following the discussion on nanog-futures, we'd like to let you all know that the [NANOG] in the subject line and the three extra info lines mailman appends will be dropped from all future messages going to the NANOG list, starting in around 24 hours from now.
If any of you have you changed your <nanog@nanog.org> e-mail filtering to depend on the [NANOG] subject tag, please consider this 24 hours notice to move to another message filtering technique.
Best wishes,
philip (for the SC) --
_______________________________________________ NANOG-announce mailing list NANOG-announce@nanog.org http://mailman.nanog.org/mailman/listinfo/nanog-announce
_______________________________________________ Nanog-futures mailing list Nanog-futures@nanog.org http://mailman.nanog.org/mailman/listinfo/nanog-futures
participants (9)
-
D'Arcy J.M. Cain -
James R. Cutler -
Jason J. W. Williams -
Jim Popovitch -
Joe Abley -
Marshall Eubanks -
Philip Smith -
Robert E. Seastrom -
Sam Stickland