From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [205.139.110.120]) by mx.groups.io with SMTP id smtpd.web10.13084.1595944801454830084 for ; Tue, 28 Jul 2020 07:00:01 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=YDuXNp3h; spf=pass (domain: redhat.com, ip: 205.139.110.120, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1595944800; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=qxBsG4j82SnrPnFKrHKJzd6jwUT3VY4kvwz7TbxHfm0=; b=YDuXNp3ho+dQWJKzVCESDzC5ubuNYNxL4PyBSxfRrSkt59+vj5khkstlMcq2dilThQxaVo TdFPV1Zz2ctGcHjUYn+AzjMPnxvjlLdHCa8Gm379uFX5uWTYvKtgH0v/+SLA+2DR/Luppy RKpnb3T67ntfGhERV0yoChxSzYYziPM= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-296-PQsZnBGMNey4-OiMtLc1jQ-1; Tue, 28 Jul 2020 09:59:55 -0400 X-MC-Unique: PQsZnBGMNey4-OiMtLc1jQ-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 952E6101EE67; Tue, 28 Jul 2020 13:59:34 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-113-229.ams2.redhat.com [10.36.113.229]) by smtp.corp.redhat.com (Postfix) with ESMTP id C0F156FEC6; Tue, 28 Jul 2020 13:59:30 +0000 (UTC) Subject: Re: [edk2-devel] [PATCH v12 00/46] SEV-ES guest support To: Tom Lendacky , devel@edk2.groups.io Cc: Brijesh Singh , Ard Biesheuvel , Eric Dong , Jordan Justen , Liming Gao , Michael D Kinney , Ray Ni , Andrew Fish , Anthony Perard , Benjamin You , Dandan Bi , Guo Dong , Hao A Wu , Jian J Wang , Julien Grall , Leif Lindholm , Maurice Ma References: <78601308-ff64-3af4-ffdd-2fccfd49f64a@redhat.com> <3890a4e7-7095-8570-a4b2-8e4cc6116b49@amd.com> From: "Laszlo Ersek" Message-ID: <11556ba1-7ade-994c-4cea-01ad12f36205@redhat.com> Date: Tue, 28 Jul 2020 15:59:29 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 07/28/20 14:52, Tom Lendacky wrote: > On 7/28/20 5:07 AM, Laszlo Ersek wrote: >> On 07/27/20 19:49, Tom Lendacky wrote: >> >>> Yes, I always get an error when I reach 40 emails: >>> >>> Reported error: 550 5.0.350 Remote server returned an error -> 500 We have >>> received more than 40 messages in 30 minutes from you. To guard against >>> autoresponder mail loops, we must reject additional messages from you >>> temporarily. Please try again later. >>> >>> So I usually have to wait a few hours and resend the last ones so they >>> make it to groups.io. >> >> Sigh. >> >> Phil found one way to deal with this non-interactively: see the >> "sendemail.smtpBatchSize" and "sendemail.smtpReloginDelay" git-config >> options. From git-send-email(1): >> >> --batch-size= >> Some email servers (e.g. smtp.163.com) limit the number >> emails to be sent per session (connection) and this will >> lead to a failure when sending many messages. With this >> option, send-email will disconnect after sending $ >> messages and wait for a few seconds (see --relogin-delay) >> and reconnect, to work around such a limit. You may want to >> use some form of credential helper to avoid having to >> retype your password every time this happens. Defaults to >> the sendemail.smtpBatchSize configuration variable. >> >> --relogin-delay= >> Waiting $ seconds before reconnecting to SMTP server. >> Used together with --batch-size option. Defaults to the >> sendemail.smtpReloginDelay configuration variable. >> >> That way the "second batch" should need no manual work, hopefully. > > I've tried with and without batch-size and relogin-delay. My initial > submissions were without these parameters and I hit the 40 email limit. I > later tried a batch-size of 1 with a relogin-delay of 1 and that still > results in the 40 email limit. I haven't tried any combinations of a > larger batch-size. > > I don't think groups.io has a per-session limit, I think it is actually > tracking individual emails over a period of time, so I don't think these > parameters do anything for that. Thank you for explaining. I've now filed a request with to raise the limit (on this list only) to 200 messages per 30 minutes. That should allow people to post large series *and* to respond to other (unrelated) email threads as well, in the normal course of their workday. Thanks Laszlo