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.6 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, 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-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (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 762641F8C6 for ; Tue, 7 Sep 2021 21:20:07 +0000 (UTC) Received: by mail-qt1-x82f.google.com with SMTP id r21so30395qtw.11 for ; Tue, 07 Sep 2021 14:20:07 -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:references:mime-version :content-disposition:in-reply-to; bh=zmooVIkJvzIoSkg65aKWAUTLCjUJo3bnKvTzm5JHinI=; b=BsgN/K41/Su2P+FiI9LtamIxIvNpGU+oee1LkDCNemJZfg21mlMF+Fjf7ppGV+WOtX uwbKDiCa4W4hTt6hHojy+zNI4fy2dtGHw0JAx5/ucAW8L/mev2p03dFNYDwz6+GZnaad fHRYTpr4zy8uFnFX16d3Kg2PR0BBsAnS6RLuI= 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:references :mime-version:content-disposition:in-reply-to; bh=zmooVIkJvzIoSkg65aKWAUTLCjUJo3bnKvTzm5JHinI=; b=MSh+FYSih4N6KB/C6TyTed/7EZROYsQJZPKdJIyoyfIpTgsedQCs11zRLSzVq0jQ/R pK/o2WuBzVJYbYwum1Z+OLyrbTru2iONSH8CEekZrQfYO5sUxvS5pCFLici7HO1IFSWF Tq8OzzhDk6r/UVE7rz4RjlN9bT7fJNR2qJomyno1m8ZVsCwZ1+yeKd4qc3oS/FsftUDP ooIGTAGnEEnjIpz9AwwkvUnAtIN64eIaqgVG0Kac9xf7B9WRPGNmYR2wDDF28YSOLwrz xCG8B7l7MK6dPpGNLbHOC/zjSOSoiBMTgfr4RriLenCaR4ejxNAzgC//gSN4CDqOu25e 7s6Q== X-Gm-Message-State: AOAM5316E6jrMGnvJgQMW3CVXVHL7SMfIoiT3ESpDT40JuFsLX1xt/r5 J6+1TGlIswKoe/F0ffSFObnSGwTE5Tnq8w== X-Google-Smtp-Source: ABdhPJyrCQmujkdboXOf07UtEq3L1sPlA1v/epZjGvlgRfliVtxYkwdim6cNUiD4wHLeSR6b4ubsGQ== X-Received: by 2002:ac8:1289:: with SMTP id y9mr474875qti.378.1631049605881; Tue, 07 Sep 2021 14:20:05 -0700 (PDT) Received: from meerkat.local (bras-base-mtrlpq5031w-grc-32-216-209-220-181.dsl.bell.ca. [216.209.220.181]) by smtp.gmail.com with ESMTPSA id i14sm183371qtx.64.2021.09.07.14.20.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 07 Sep 2021 14:20:05 -0700 (PDT) Date: Tue, 7 Sep 2021 17:20:04 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: [PATCH] lei_to_mail+mbox_reader: fix handling of empty/bogus emails Message-ID: <20210907212004.nn23qtcfpjmbf5tl@meerkat.local> References: <20210902211225.pmnykwcwcxeaunt5@meerkat.local> <20210902215850.GA5063@dcvr> <20210903151500.h72mzcpqixgtytjs@meerkat.local> <20210904213658.GA27941@dcvr> <20210907181726.ghb6xn4qcsdchquw@meerkat.local> <20210907205617.GA3923@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210907205617.GA3923@dcvr> List-Id: On Tue, Sep 07, 2021 at 08:56:17PM +0000, Eric Wong wrote: > > 1. this means that each "lei up" call will be increasingly larger and larger, > > since when we init the search with rt:, it gets resolved into a datestamp > > (e.g. rt:2.weeks.ago becomes rt:1625699031). I'm worried that this will be > > increasingly hard on the server side, especially if someone > > fires-and-forgets a cronjob that ends up downloading ever-growing mboxes > > every 5 minutes. > > "rt:2.weeks.ago" stays "rt:2.weeks.ago" in saved searches :> Oh, you're right. Apologies for not digging deeper. > > 2. is there some sanity limit on the server side that would prevent someone's > > overly broad search query from gzipping and downloading gigabytes of mail? > > Not right now. With public-inbox-httpd, the actual git fetches > are handled fairly w.r.t to other requests (and I could > deprioritize them further, if needed...). The Xapian query OTOH... Okay, I guess it's not any different from someone doing the same thing over the web interface. It would be nice to have a way to limit how many messages are returned for gzipped mailbox downloads, seeing as they cannot be paginated in the same way web views are, but it's not a priority right away. Thanks, -K