[PATCH v22 00/28] riscv control-flow integrity for usermode
David Hildenbrand
david at redhat.com
Thu Oct 23 03:24:15 PDT 2025
On 23.10.25 02:33, Deepak Gupta wrote:
> I don't think I am sending that many patches. It's 28 patches.
> I did send v21 using same smtp settings on my end.
>
> Although since this week whenever I am sending patch series, after 14th/15th
> patch, I start getting below error for all recipients.
>
> """
> The user you are trying to contact is receiving mail at a rate that\n
> 4.2.1 prevents additional messages from being delivered. Please resend your\n
> 4.2.1 message at a later time. If the user is able to receive mail at that\n
> 4.2.1 time, your message will be delivered. For more information, go to\n
> 4.2.1 https://support.google.com/mail/?p=ReceivingRate 98e67ed59e1d1-33dfb7f8310sm153460a91.5 - gsmtp')
> """
>
> I did try "git config --local sendmail.smtpReloginDelay 60", it doesn't seem to
> help. If anyone has faced this and knows how to get around that'll be helpful.
> In the meanwhile, I'll keep figuring it out on what really changed this week.
I got that as well a couple of days ago after patch #16, it's annoying
and I did not figure out easily which gmail user to blame.
After git-send-email failed halfway through, I decided to just send the
remaining emails with --in-reply-to="" giving it the message ID of the
cover letter.
References: is in that case still messed up for the resends, but at
least all emails show up properly in the same thread.
I had to take care of the CC list, which was annoying as well.
--
Cheers
David / dhildenb
More information about the linux-riscv
mailing list