From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.5 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qv1-xf2e.google.com (mail-qv1-xf2e.google.com [IPv6:2607:f8b0:4864:20::f2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 222391F9E0 for ; Wed, 22 Apr 2020 22:17:28 +0000 (UTC) Received: by mail-qv1-xf2e.google.com with SMTP id t8so1845944qvw.5 for ; Wed, 22 Apr 2020 15:17:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=e6AqsRMSsUVwBlBVMxEFFwgFfrEDPaT37ANXVW8ppTQ=; b=NIz0ksy70BQ0WcjZsZqFwUkFuH4tys+jrrNkm3TcRAqt1rWo+8zA8Sx2DNqjAtN9+W MPy66xh6WAHyrOOaJ82VT0ZBweD748/VtuFvZiJkOdmyMErPAH00T7BC2zkt1FwGhbXj Jyo3pxZjQQfbmOj4Z4kHEsFqCdENt5/Vuf3uA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=e6AqsRMSsUVwBlBVMxEFFwgFfrEDPaT37ANXVW8ppTQ=; b=U9fjF4hbJ7L23nJbDRI6Pxonl6vU2FJ0lhIDiPxRrWiRoi63S3MIPm04H2PqkuMkG1 iVKxLN5G+1M1N65ZCHPVHWYL0gsTXVUZpAI3DtR7OSeVt/3WBCKIQd5HI4eyTqPtnIeO KpDisfZ7tLBItXdK+ubsrWUQwf/PKZoKUQjQMtFzgmq91TbBEmhdkXNTVZ+EQPY0wvpf U6kY/fjOzCtiuN+xtEisXwF6xMtyJYsNodDnP2xxR3GIjXE20yNEhv74EsopltNtVxyU gmcHBW7VkdSMGmBHEjtCB+9x0oNeDOpsxs+AzS616o/pLGLzQ6qjHYc49btB80Q4o3xC gB4w== X-Gm-Message-State: AGi0PualaRdmU+tTwLi6UcjLlmQnVDId+l6nn2u3jXKbKqK5r+dsyge/ 3/uBgrCnpjtfDJBdIdOU5RK11w== X-Google-Smtp-Source: APiQypKp1O7IMso+5fVgRsWvn7aD8a15DlipqJqzVFoOYXxVPY3XyxCets7LAAb0AvCECyF7ZiuYMw== X-Received: by 2002:a0c:f781:: with SMTP id s1mr1242306qvn.182.1587593846884; Wed, 22 Apr 2020 15:17:26 -0700 (PDT) Received: from chatter.i7.local (107-179-243-71.cpe.teksavvy.com. [107.179.243.71]) by smtp.gmail.com with ESMTPSA id n67sm361429qke.88.2020.04.22.15.17.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 22 Apr 2020 15:17:26 -0700 (PDT) Date: Wed, 22 Apr 2020 18:17:24 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: mail header indexing additions Message-ID: <20200422221724.hwx5pde2ege4fekz@chatter.i7.local> Mail-Followup-To: Eric Wong , meta@public-inbox.org References: <20200420015317.GA9660@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20200420015317.GA9660@dcvr> List-Id: On Mon, Apr 20, 2020 at 01:53:17AM +0000, Eric Wong wrote: > I'm probably going to start indexing List-Id: headers by > default, and have `lid:' be the search prefix for inboxes > which combine multiple lists and may have unstable email > addresses. This would be handy indeed! > Anything else that should be indexed by default? > > There'll also be an option to define indexing for other headers, > such as bug-tracker-specific IDs and such. I think if this is configurable, then it's really the only thing that's needed. Everyone's needs are going to be different, so indexing headers that aren't interesting to many people is just going to lead to storage bloat. -K