From: Tom Rini <trini@konsulko.com>
To: Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
Cc: U-Boot-Denx <u-boot@lists.denx.de>
Subject: Re: GSuit limit for recipients
Date: Mon, 27 Sep 2021 17:06:19 -0400 [thread overview]
Message-ID: <20210927210619.GO31748@bill-the-cat> (raw)
In-Reply-To: <CAOF=9AuQSjW4zjhAidKUMu=uTzqCh4vZ=RL54aT1ou5LFUk5pA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
On Mon, Sep 27, 2021 at 05:58:08PM +0300, Oleksandr Suvorov wrote:
> Dear community,
>
> This weekend I tried to post (using patman) a patch set that should
> have been sent to 120 recipients (a lot of files were changed).
>
> I've got an error from the Gmail SMTP server:
> 4.5.3 Your message has too many recipients. For more information regarding
> 4.5.3 Google's sending limits, please visit:
> 4.5.3 https://support.google.com/mail/?p=TooManyRecipientsError
> e1sm1539543ljp.114 - gsmtp
>
> The doc says there is a limit for recipients - 100 per message. All my
> emails are hosted by Gmail/G-suit. I think I'm not the first who faced
> such an issue.
> Could you share your tricks or best practices on how to post patch
> sets with more than 100 recipients without changing an e-mail
> provider?
>
> Thanks in advance for your help!
Honestly, that probably means the patch needs to be split up more. Per
SoC / SoC family perhaps.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-09-27 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 14:58 GSuit limit for recipients Oleksandr Suvorov
2021-09-27 21:06 ` Tom Rini [this message]
2021-09-28 10:14 ` Oleksandr Suvorov
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=20210927210619.GO31748@bill-the-cat \
--to=trini@konsulko.com \
--cc=oleksandr.suvorov@foundries.io \
--cc=u-boot@lists.denx.de \
/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 NNTP newsgroup(s).