From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/action-ci] 436a7d: email: compose a new message for each email
Date: Thu, 10 Sep 2026 10:49:48 -0700 [thread overview]
Message-ID: <bluez/action-ci/push/refs/heads/main/2857bb-436a7d@github.com> (raw)
Branch: refs/heads/main
Home: https://github.com/bluez/action-ci
Commit: 436a7d6111155e0fe21fde8b7b3c6644675ae2b7
https://github.com/bluez/action-ci/commit/436a7d6111155e0fe21fde8b7b3c6644675ae2b7
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-09-10 (Thu, 10 Sep 2026)
Changed paths:
M libs/email.py
Log Message:
-----------
email: compose a new message for each email
The same EmailTool instance is used for every email of a run, but compose()
kept adding the headers to the same message object, so the second email
carried two From/To/Subject headers and Gmail rejected it:
550 5.7.1 This message is not RFC 5322 compliant. There are multiple To
headers.
Start from a new message in compose(). While at it, don't let quit() throw
on a connection the server has already dropped, which made the failure
escape send() and abort the whole run, and drop the leftover asyncio
import.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/action-ci/settings/notifications
reply other threads:[~2026-09-10 17:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/action-ci/push/refs/heads/main/2857bb-436a7d@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/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