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.7 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) (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 744021F8C8 for ; Tue, 7 Sep 2021 18:17:29 +0000 (UTC) Received: by mail-qv1-xf32.google.com with SMTP id a12so1616015qvz.4 for ; Tue, 07 Sep 2021 11:17:29 -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=1gERSpClR4baEXbAUBn0hNDd7YUnR3ZJX1nq9DQdD7c=; b=gLLUowWyzlF3TwRa/FDDonmNhYQmknceE6ryWEvAWQBWAwhBW3BdMj/Ps9Mv50Dn9z L406dvh3KhVCbhE3vmesWK3s8hkKRnItJJXFr2QORFS92hrVSyG3dCoJ6k9u3c1Pjtw0 kKKAoNxUyjcNhGxDs11vSsDUESZ4xrzM+A7e8= 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=1gERSpClR4baEXbAUBn0hNDd7YUnR3ZJX1nq9DQdD7c=; b=la8djfSevwp7eAEWo+q3V+D2C001pJFwqGKupSGx/bF3KexO49qiUGSTw6+NM2Milp BMgKVOS0YQKizvK63Yf+I0NByHyDkFvnbfsUzGnFsmtQptZellvl8ZM2xyk0Rd47Pp8K VG8NxKGob58js/gRHV4WKEG3EpiLIXAg3vm9A8l0JNFfBia/bUnXW29W6OWY5WnOV56b PHoZq+VFL2EkMtH1Ndq2bfyEv0B5AfyM3GCSSmyN8woOx9lOnVGXhwrugCh/6oQbTTYS pvJdCixz9i9WqLJhFCC36neHwz0HO8fOByATvKDRpaWhhoTiPFu2p5QXxsiOc1a+uFcL FduQ== X-Gm-Message-State: AOAM532Hr+Maco0Qt5pjuCsDjz314vY8dR98tfDSercms3tkq3kwK/x9 0pNXOMhm2eETgd/leTAFCOMLHOMThkl1YQ== X-Google-Smtp-Source: ABdhPJwzGxfIUq5OrhyRt3LYssJfrVo/4woHSJ9Tzr6JhDhJMDW912TtV8klLILRm07zct1ga4kg8w== X-Received: by 2002:a0c:b293:: with SMTP id r19mr11046691qve.19.1631038648098; Tue, 07 Sep 2021 11:17:28 -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 h6sm7799866qtn.51.2021.09.07.11.17.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 07 Sep 2021 11:17:27 -0700 (PDT) Date: Tue, 7 Sep 2021 14:17:26 -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: <20210907181726.ghb6xn4qcsdchquw@meerkat.local> References: <20210902211225.pmnykwcwcxeaunt5@meerkat.local> <20210902215850.GA5063@dcvr> <20210903151500.h72mzcpqixgtytjs@meerkat.local> <20210904213658.GA27941@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210904213658.GA27941@dcvr> List-Id: On Sat, Sep 04, 2021 at 09:36:58PM +0000, Eric Wong wrote: > Konstantin Ryabitsev wrote: > > Yep, that seems to work fine. Question -- I noticed that lei just issues a > > regular query, retrieves results with curl and then parses the output. Is > > there a danger of potentially running into issues with parsing the regular > > HTML output if it changes in the future? > > It's actually parsing gzipped mboxrd (&x=m). But you're right > we could use stronger safeguards in case we see gzipped HTML or > something else... Ooh, okay, I guess I should actually look at the output of the curl call. :) The questions I have, then: 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. 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? -K