Help test IMAP access to the IETF archives
Robert Sparks <rjsparks@nostrum.com> Thu, 27 August 2015 20:38 UTC
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFAF21A6F0E for <ietf@ietfa.amsl.com>; Thu, 27 Aug 2015 13:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lkVDMJsdSVr9 for <ietf@ietfa.amsl.com>; Thu, 27 Aug 2015 13:38:05 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C42A1A1BB9 for <ietf@ietf.org>; Thu, 27 Aug 2015 13:38:05 -0700 (PDT)
Received: from unnumerable.local (pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t7RKc4R1031590 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK) for <ietf@ietf.org>; Thu, 27 Aug 2015 15:38:05 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80] claimed to be unnumerable.local
Message-ID: <55DF7527.1020201@nostrum.com>
Date: Thu, 27 Aug 2015 15:37:59 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Help test IMAP access to the IETF archives
References: <55CA09A7.1030801@nostrum.com>
In-Reply-To: <55CA09A7.1030801@nostrum.com>
X-Forwarded-Message-Id: <55CA09A7.1030801@nostrum.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/5jmmdG-iPHUdy2XTH-C3mE9LET8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Robert Sparks <rjsparks@nostrum.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Aug 2015 20:38:06 -0000
Folks - We have been testing IMAP access to the IETF archives for several days now, with volunteers from the tools-discuss and ietf chairs lists, and it's been going well. Thank you if you've been helping test already (and please continue to do so)! Now we need more testers. We'd like to get a simple measure of load, so we'd like to have as many folks as are willing accessing the test instance at the same time with various clients during the next week. It would be particularly helpful to have several people using the system next Thursday. If you're willing to take the time to do this, please drop me a note directly (I've set reply-to on this message) so I have a feel for how many people are participating. Instructions for accessing the test instance are below. Please report any issues you find directly to me. Do not open tickets with the secretariat. Be aware that there are known issues with the data on the test instance (some lists have blank or truncated messages) that have not yet been addressed - it would be good to report any more you find to me, but they won't get fixed immediately. Please use tools-discuss@ietf.org for general conversation. If you have feature requests, that's a good place to send them. One request we've had from a few testers so far is to provide an additional shared folder with a mailbox for each list that has only the "recent" messages from that list - perhaps the last 6 months. It would be good to hear from folks, after they've tried what's there now, whether that would be useful to spend development time on, or if that time would be better spent elsewhere. The test instance is getting mail with only a slight delay after it comes through the lists - you should see current traffic. Please resist the temptation to download the entire archive of every list. I've done it - it's huge (~28G when MailMate does it) and it it's a severe torture test for clients. Interrupt your client if it starts trying to do that to you. Caching a copy of this test instance will not be useful when we deploy the production instance. Instead, what would help us the most is to configure your client to access those lists you normally subscribe to, and to spend some time next week browsing and searching those lists and exploring a few lists that are new to you. You can find the details for where the test instance is listening, and rudimentary instructions for setting up a few clients, at <http://trac.tools.ietf.org/group/tools/trac/wiki/ImapTesting>. Please improve that page as you see the opportunity. Thanks in advance for any time you can give this. RjS
- Help test IMAP access to the IETF archives Robert Sparks
- Re: Help test IMAP access to the IETF archives Robert Sparks
- Re: Help test IMAP access to the IETF archives Ralph Droms
- Re: Help test IMAP access to the IETF archives Tim Wicinski
- Re: Help test IMAP access to the IETF archives Joseph Lorenzo Hall
- Re: Help test IMAP access to the IETF archives Robert Sparks
- Google threatens to break Gmail Brian E Carpenter
- Re: Google threatens to break Gmail Brian E Carpenter
- Re: Google threatens to break Gmail Ross Finlayson
- Re: Google threatens to break Gmail Andrew G. Malis
- Re: Help test IMAP access to the IETF archives John Dickinson
- Re: Help test IMAP access to the IETF archives Rich Kulawiec
- Re: Google threatens to break Gmail Russ Housley
- Re: Google threatens to break Gmail Andrew G. Malis
- Re: Help test IMAP access to the IETF archives Dave Crocker
- Re: Google threatens to break Gmail Paul Wouters
- Re: Help test IMAP access to the IETF archives Robert Sparks
- Re: Google threatens to break Gmail Phillip Hallam-Baker
- DMARC stuff John Levine
- Re: Google threatens to break Gmail John Levine
- Re: DMARC stuff Michael Richardson
- mailman [was: Google threatens to break Gmail] Miles Fidelman
- Re: DMARC stuff JORDI PALET MARTINEZ
- Re: Google threatens to break Gmail Rich Kulawiec
- Re: DMARC stuff John R Levine
- Re: Google threatens to break Gmail Rich Kulawiec
- Re: DMARC stuff Dave Crocker
- Re: DMARC stuff Dave Crocker
- Re: DMARC stuff David Morris
- Re: DMARC stuff JORDI PALET MARTINEZ
- Re: Google threatens to break Gmail Brian E Carpenter
- Re: DMARC stuff Rich Kulawiec
- RE: Google threatens to break Gmail Christian Huitema
- Re: DMARC stuff John R Levine
- Re: DMARC stuff Dave Crocker
- Re: Google threatens to break Gmail Dave Crocker
- Re: Google threatens to break Gmail Martin Rex
- Re: Google threatens to break Gmail Joseph Lorenzo Hall
- Re: mailman [was: Google threatens to break Gmail] John Levine
- Re: Google threatens to break Gmail Rich Kulawiec
- Re: Google threatens to break Gmail Rich Kulawiec
- Re: Google threatens to break Gmail Brian E Carpenter
- Re: Google threatens to break Gmail John Levine
- Re: Google threatens to break Gmail Randy Bush
- Re: mailman [was: Google threatens to break Gmail] Pierre-Elliott Bécue
- Re: Google threatens to break Gmail Ted Lemon
- Re: Google threatens to break Gmail Harald Alvestrand
- Re: Google threatens to break Gmail Randy Bush
- Re: Google threatens to break Gmail Harald Alvestrand
- Re: Google threatens to break Gmail Ted Lemon
- Re: Google threatens to break Gmail Paul Wouters
- Re: Google threatens to break Gmail Phillip Hallam-Baker
- Re: Google threatens to break Gmail John C Klensin
- Re: Google threatens to break Gmail ned+ietf
- Re: Google threatens to break Gmail Philip Homburg
- Re: Google threatens to break Gmail John Levine
- Re: Google threatens to break Gmail Philip Homburg
- Re: Google threatens to break Gmail John C Klensin
- Re: Google threatens to break Gmail Brian E Carpenter
- Re: Google threatens to break Gmail Jelte Jansen
- Re: Google threatens to break Gmail John R Levine
- Re: Google threatens to break Gmail Phillip Hallam-Baker
- Re: Google threatens to break Gmail John C Klensin
- RE: Google threatens to break Gmail Ted Lemon
- Re: Google threatens to break Gmail John R Levine
- Re: Google threatens to break Gmail Mark Rousell
- RE: Google threatens to break Gmail John C Klensin
- Re: Google threatens to break Gmail Viktor Dukhovni
- Re: Google threatens to break Gmail Ted Lemon
- Incremental hacks and letting abusers control the… Dave Crocker
- Re: Incremental hacks and letting abusers control… John C Klensin
- Re: Google threatens to break Gmail Martin Rex
- Re: Google threatens to break Gmail John Levine
- Re: Google threatens to break Gmail Niels Dettenbach (Syndicat.com)
- Re: Google threatens to break Gmail Dave Crocker
- Re: Incremental hacks and letting abusers control… Ted Lemon
- Re: Google threatens to break Gmail Dave Crocker
- Re: Google threatens to break Gmail Viktor Dukhovni
- Re: Google threatens to break Gmail Martin Rex
- Re: Google threatens to break Gmail Niels Dettenbach
- RE: Google threatens to break Gmail Ted Lemon
- RE: Google threatens to break Gmail {dkim-fail} ned+ietf
- Re: Google threatens to break Gmail {dkim-fail} Hector Santos