workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Drew DeVault" <sir@cmpwn.com>
To: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
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 14:51:59 +0100	[thread overview]
Message-ID: <CFR94YBY5YOV.3HUOHZ34CUV2Q@taiga> (raw)
In-Reply-To: <20211116134917.cqpca6auuzt7f5sw@meerkat.local>

On Tue Nov 16, 2021 at 2:49 PM CET, Konstantin Ryabitsev wrote:
> We do have the maxi plan for linux.dev, and we *have* hit limits. The
> Migadu folks have been extremely accommodating for us, so it's not
> been a huge deal thus far, but I'm not sure if the relaxed
> restrictions they've put in place are just for the linux.dev domain or
> now apply globally. For example, sending large patch series (20+) used
> to trip up Migadu's outgoing rate limit for too much mail sent at
> once. We've not hit that error for a while, so I assume they've
> relaxed that restriction either just for linux.dev, or perhaps
> globally.
>
> It's important to keep in mind that the overall outgoing/incoming
> limits are per account, not per mailbox. Not a huge deal for personal
> use, but quickly adds up for setups like we have, which is why we ask
> folks not to subscribe to busy lists (see #4 in the list of our
> requirements here:
> https://www.kernel.org/doc/projects/korg/linuxdev.html#rules-and-restrictions)
>
> 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.

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.

  reply	other threads:[~2021-11-16 13:52 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 [this message]
2021-11-16 14:04                 ` Konstantin Ryabitsev
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=CFR94YBY5YOV.3HUOHZ34CUV2Q@taiga \
    --to=sir@cmpwn.com \
    --cc=geert@linux-m68k.org \
    --cc=konstantin@linuxfoundation.org \
    --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).