On Sat, Sep 12, 2020 at 4:51 PM Mel Gorman [off-list ref] wrote:

On Sat, Sep 12, 2020 at 11:36:52AM +0200, John Wood wrote:

quoted

On Sat, Sep 12, 2020 at 12:56:18AM -0700, Kees Cook wrote:

quoted

On Sat, Sep 12, 2020 at 10:03:23AM +1000, James Morris wrote:

quoted

On Thu, 10 Sep 2020, Kees Cook wrote:

quoted

[kees: re-sending this series on behalf of John Wood [off-list ref]
 also visible at https://github.com/johwood/linux fbfam]

From: John Wood <redacted>

Why are you resending this? The author of the code needs to be able to
send and receive emails directly as part of development and maintenance.

I tried to send the full patch serie by myself but my email got blocked. After
get support from my email provider it told to me that my account is young,
and due to its spam policie I am not allow, for now, to send a big amount
of mails in a short period. They also informed me that soon I will be able
to send more mails. The quantity increase with the age of the account.

If you're using "git send-email" then specify --confirm=always and
either manually send a mail every few seconds or use an expect script
like

#!/bin/bash
EXPECT_SCRIPT=
function cleanup() {
        if [ "$EXPECT_SCRIPT" != "" ]; then
                rm $EXPECT_SCRIPT
        fi
}
trap cleanup EXIT

EXPECT_SCRIPT=`mktemp`
cat > $EXPECT_SCRIPT <<EOF
spawn sh ./SEND
expect {
        "Send this email"   { sleep 10; exp_send y\\r; exp_continue }
}
EOF

expect -f $EXPECT_SCRIPT
exit $?

This will work if your provider limits the rate mails are sent rather
than the total amount.

...or you could keep it simple and just pass "--batch-size 1
--relogin-delay 10" to git send-email ;)

-- 
Ondrej Mosnacek
Software Engineer, Platform Security - SELinux kernel
Red Hat, Inc.