From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <konstantin@linuxfoundation.org>
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-3.5 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.6
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736])
	(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 5B5021F560
	for <meta@public-inbox.org>; Mon, 18 Sep 2023 13:47:06 +0000 (UTC)
Authentication-Results: dcvr.yhbt.net;
	dkim=pass (1024-bit key; unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=google header.b=VRlEx8e3;
	dkim-atps=neutral
Received: by mail-qk1-x736.google.com with SMTP id af79cd13be357-77063481352so231437985a.1
        for <meta@public-inbox.org>; Mon, 18 Sep 2023 06:47:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=linuxfoundation.org; s=google; t=1695044824; x=1695649624; darn=public-inbox.org;
        h=in-reply-to:content-disposition:mime-version:references:message-id
         :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to;
        bh=XTJAX0EgfQnYtxelEcORkbicafLDbPC7XQC0QdJwaaA=;
        b=VRlEx8e3VewAc4umIgjaz9/x+K89cVqEOKUGhZuvycABdxsDdEbSO9qNyZ21fF0sTR
         SZ88F+eCGAqAUy1fmBmtOV0b0cNAScpoBMpmSaa2PuILwQLTYulDFS9mlzlEo2OlZp82
         TRxg1IoS8faXXFCvcBSsFbZ+Ygj7RD7O0HHzE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1695044824; x=1695649624;
        h=in-reply-to:content-disposition:mime-version:references:message-id
         :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date
         :message-id:reply-to;
        bh=XTJAX0EgfQnYtxelEcORkbicafLDbPC7XQC0QdJwaaA=;
        b=bJCn0gSM0o123EzLc+1MgyEgeVpkfbscQmxVuJDR67CR0rBLbgJCgK4iFKNRmePCzP
         OWptxvf2ozYgaxzEE5nGzSyRkuahGUekdAnPOhhM+fQa0qxxnGfe4oP7nGYFfL4XjJL7
         bz5CIiDmlUXUDl3Gy0wwhFtXvF2mTaezgXyG4ZMbtUa7SVYQG+661OorVHBheCMyFiTl
         060ijHIdNyeJeR0FnbD2mh8qtRJeSs/FFrGwDfm+RYyVLzyuazXIEH5MhW84vYidMiMU
         oLKrQOgRBCLxFZhVTUAIiG66pJ7ZQrmCTFnD7XR5fMvcQwHXp1/6vucnpUIodfYJN6eO
         Y4VQ==
X-Gm-Message-State: AOJu0YxTgYAKpky0TJfWSfEijhHWt4vShu1yRlks4rdcQXSwE6RffBHn
	0rs0/A3ZKEGw+n7C7JVkhXlZJI1CmXYZuGCKYig=
X-Google-Smtp-Source: AGHT+IFvqWwswTVhTiez/rlBNH+98cRyB8m/WL6INMi+nBFwX4WTTQxbfvRitj5o28Vt1mBV+dpzKw==
X-Received: by 2002:a05:620a:258d:b0:76e:f686:cad8 with SMTP id x13-20020a05620a258d00b0076ef686cad8mr15835295qko.13.1695044824701;
        Mon, 18 Sep 2023 06:47:04 -0700 (PDT)
Received: from meerkat.local ([209.226.106.110])
        by smtp.gmail.com with ESMTPSA id 27-20020a05620a079b00b00767b24f68edsm3164452qka.62.2023.09.18.06.47.04
        (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
        Mon, 18 Sep 2023 06:47:04 -0700 (PDT)
Date: Mon, 18 Sep 2023 09:46:55 -0400
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [RFC] pop3: support `?limit=$NUM' parameter in mailbox name
Message-ID: <20230918-barrel-unhearing-b63869@meerkat>
References: <20230912-impart-swinger-4c2434@meerkat>
 <20230912224034.M689061@dcvr>
 <20230913-tarot-monogamy-2f614c@meerkat>
 <20230914003828.M101484@dcvr>
 <20230915-reputable-maverick-13736d@meerkat>
 <20230915204110.M732304@dcvr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20230915204110.M732304@dcvr>
List-Id: <meta.public-inbox.org>

On Fri, Sep 15, 2023 at 08:41:10PM +0000, Eric Wong wrote:
> Thanks, pushed the series as
> a37e3ab3740c24c3 (pop3: limit default mailbox to 1K messages, 2023-09-14)
> 392d251f97d46579 (pop3: support `?limit=$NUM' parameter in mailbox name, 2023-09-12)

Oh, I did notice what is probably unintentional behaviour -- passing
?limit=XXX affects all mailbox access, not just the initial retrieval.

E.g. if I configured pop3 with ?limit=128, then leave for the weekend and
return on Monday, I will only be able to retrieve 128 new messages, regardless
of how many arrived over the weekend.

I'm not sure if this is what was intended -- I think it makes more sense to
have ?limit=XXX only affect the initial retrieval. In all other cases, when a
tracking uuid cookie is present, it should return all messages regardless of
?limit=.

Does that make sense?

-K