* [bluez/action-ci] 436a7d: email: compose a new message for each email
@ 2026-09-10 17:49 Luiz Augusto von Dentz
0 siblings, 0 replies; only message in thread
From: Luiz Augusto von Dentz @ 2026-09-10 17:49 UTC (permalink / raw)
To: linux-bluetooth
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-09-10 17:49 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-09-10 17:49 [bluez/action-ci] 436a7d: email: compose a new message for each email Luiz Augusto von Dentz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox