workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Drew DeVault <sir@cmpwn.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>, workflows@vger.kernel.org
Subject: Re: Gmail (was: Re: lore+lei: part 2, now with IMAP)
Date: Tue, 16 Nov 2021 09:04:26 -0500	[thread overview]
Message-ID: <20211116140426.7yghiglow66sd7y3@meerkat.local> (raw)
In-Reply-To: <CFR94YBY5YOV.3HUOHZ34CUV2Q@taiga>

On Tue, Nov 16, 2021 at 02:51:59PM +0100, Drew DeVault wrote:
> > Overall, Migadu is a good recommendation for individual developer
> > accounts, but may be too restricting for maintainers that do end up
> > sending huge amounts of mail. Gmail or Fastmail could be better
> > options for those folks.
> 
> I'm surprised to learn that linux.dev is using Migadu rather than its
> own infrastructure. I would only recommend it for personal use.

1. We couldn't easily gauge how many people would be interested in the
   service, so the goal was to avoid setting up infrastructure if only a small
   subset of users would be interested in using it. And that's largely proven
   correct, as only about 20 people requested accounts on linux.dev, and only
   about 5-7 people use them regularly to send and receive mail.
2. Dealing with spammers is a huge effort sink, so if someone already has a
   good setup for recognizing and catching spammers, then we might as well
   delegate this to them.
3. Migadu offers open-source project discounts, so it's actually dramatically
   cheaper for us to use them than to run our own infra in terms of admin
   time. :)

> I will say that I have also occasionally hit Migadu's limits, but they
> have been accomodating in loosening them for legitimate use when asked.

Yes, I have no complaints about Migadu. They are great and I heartily
recommend it to others.

-K

  reply	other threads:[~2021-11-16 14:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 19:13 lore+lei: part 2, now with IMAP Konstantin Ryabitsev
2021-11-15 18:34 ` Gmail (was: Re: lore+lei: part 2, now with IMAP) Geert Uytterhoeven
2021-11-15 21:46   ` Konstantin Ryabitsev
2021-11-16  8:01     ` Geert Uytterhoeven
2021-11-16  8:04       ` Drew DeVault
2021-11-16  8:26         ` Geert Uytterhoeven
2021-11-16  8:29           ` Drew DeVault
2021-11-16 13:49             ` Konstantin Ryabitsev
2021-11-16 13:51               ` Drew DeVault
2021-11-16 14:04                 ` Konstantin Ryabitsev [this message]
2021-11-16 13:35       ` Konstantin Ryabitsev
2021-11-16 12:18     ` Han-Wen Nienhuys
2021-11-22 14:37 ` lore+lei: part 2, now with IMAP Jani Nikula
2021-11-22 15:07   ` Konstantin Ryabitsev

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211116140426.7yghiglow66sd7y3@meerkat.local \
    --to=konstantin@linuxfoundation.org \
    --cc=geert@linux-m68k.org \
    --cc=sir@cmpwn.com \
    --cc=workflows@vger.kernel.org \
    --subject='Re: Gmail (was: Re: lore+lei: part 2, now with IMAP)' \
    /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

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 NNTP newsgroup(s).