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
Date: Wed, 13 Sep 2023 12:08:19 -0400 [thread overview]
Message-ID: <20230913-tarot-monogamy-2f614c@meerkat> (raw)
In-Reply-To: <20230912224034.M689061@dcvr>
On Tue, Sep 12, 2023 at 10:40:34PM +0000, Eric Wong wrote:
> Perhaps 50K is too much? I figured clients would have a way to
> limit that, but I don't really pay attention to POP3 clients...
The few clients I looked at didn't give any option to specify how many remote
messages I want to retrieve, so I think defaulting to 50,000 is not the right
approach. Maybe the default limit should be something "last 7 days or 1000
messages, whichever is larger"?
My initial target for deploying POP3 support is to allow Gmail users to
pull-subscribe to mailing lists, since Gmail is the #1 provider that we have
trouble with message delivery due to their draconian threshold limits.
However, I think if the default behaviour results in dumping 50,000 messages
into people's inboxes, they wouldn't use it, which is why I think we should
have a default that is lighter both on the server side and on the users.
-K
next prev parent reply other threads:[~2023-09-13 16:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 21:08 pop3 usability thoughts Konstantin Ryabitsev
2023-09-12 22:40 ` [RFC] pop3: support `?limit=$NUM' parameter in mailbox name Eric Wong
2023-09-13 6:20 ` Eric Wong
2023-09-13 15:33 ` Konstantin Ryabitsev
2023-09-13 22:03 ` Eric Wong
2023-09-15 19:17 ` Konstantin Ryabitsev
2023-09-13 16:08 ` Konstantin Ryabitsev [this message]
2023-09-14 0:38 ` Eric Wong
2023-09-15 20:03 ` Konstantin Ryabitsev
2023-09-15 20:41 ` Eric Wong
2023-09-18 13:46 ` Konstantin Ryabitsev
2023-09-18 21:14 ` Eric Wong
2023-09-19 21:28 ` Konstantin Ryabitsev
2023-09-22 2:18 ` [PATCH] pop3: support initial_limit " Eric Wong
2023-09-22 18:02 ` Konstantin Ryabitsev
2023-09-22 18:38 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230913-tarot-monogamy-2f614c@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).