From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: POP3 adoption (was: [PATCH 1/2] doc|www: flesh out POP3 documentation for servers) and users
Date: Mon, 6 Feb 2023 09:27:37 -0500 [thread overview]
Message-ID: <20230206142737.ldlvu4xhnx7vxlo7@nitro.local> (raw)
In-Reply-To: <20230206060338.M551984@dcvr>
On Mon, Feb 06, 2023 at 06:03:38AM +0000, Eric Wong wrote:
> > +The password is: anonymous
> > +The username is: \$(uuidgen)\@$ctx->{ibx}->{newsgroup}
> > +where \$(uuidgen) in the output of the `uuidgen' command on your system.
> > +The UUID in the username functions as a private cookie (don't share it).
> > +Idle accounts will expire periodically.
>
> I just checked my POP3 instance on public-inbox.org; and not a
> single user has used it. I guess POP3 really is unpopular :<
I think it's because it's not a widely known feature. I intend to make it
available soon via lore.kernel.org, which should allow people to subscribe to
lists via gmail's POP3 integration.
I just need to implement the unified daemon features so we don't manage 5
different systemd services.
-K
next prev parent reply other threads:[~2023-02-06 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 20:41 [PATCH 0/2] POP3 docs + tests for users and BOFHs Eric Wong
2022-07-29 20:41 ` [PATCH 1/2] doc|www: flesh out POP3 documentation for servers and users Eric Wong
2023-02-06 6:03 ` POP3 adoption (was: [PATCH 1/2] doc|www: flesh out POP3 documentation for servers) " Eric Wong
2023-02-06 14:27 ` Konstantin Ryabitsev [this message]
2022-07-29 20:41 ` [PATCH 2/2] tests: maintainer test for using mpop 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: https://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=20230206142737.ldlvu4xhnx7vxlo7@nitro.local \
--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.
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).