Not sure about this, I mean it makes sense to have more debug data available, but not sure about the method name and signature.

WDYT @fabpot ?

The response is already logged in the HttpClient i believe, no ?

I see how this could be used, but maybe add a toggle/config to enable it only in debug mode ?

Maybe i'm wrong, but i'm feeling a bit "afraid" of the added "weight" (messenger / serialization ..)

Looking at the linked issue, this is not about debugging but rather about providing extra info.
Maybe a generic getInfo() could work - and we'd ensure this contains the response header (and the json-decoded body)?

Looking at the linked issue, this is not about debugging but rather about providing extra info. Maybe a generic getInfo() could work - and we'd ensure this contains the response header (and the json-decoded body)?

@nicolas-grekas Nice, We can then ensure this via adding the whole response object?

Having a free-form array where each transport can add anything looks like a bad idea.

@nicolas-grekas what about something like this:

diff --git a/src/Symfony/Component/Notifier/Message/SentMessage.php b/src/Symfony/Component/Notifier/Message/SentMessage.php
index 6febf9ebc9..bd662f68aa 100644
--- a/src/Symfony/Component/Notifier/Message/SentMessage.php
+++ b/src/Symfony/Component/Notifier/Message/SentMessage.php
@@ -19,6 +19,7 @@ class SentMessage
     private MessageInterface $original;
     private string $transport;
     private ?string $messageId = null;
+    private array $info = [];

     public function __construct(MessageInterface $original, string $transport)
     {
@@ -45,4 +46,23 @@ class SentMessage
     {
         return $this->messageId;
     }
+
+    public function setInfo(int $responseStatusCode, array $responseHeaders = [], array $body = []): void
+    {
+        $this->info = [
+            'response' => [
+                'status_code' => $responseStatusCode,
+                'headers' => $responseHeaders,
+                'body' => $body,
+            ]
+        ];
+    }
+
+    /**
+     * @return array{response: array{status_code: int, headers: array, body: array}
+     */
+    public function getInfo(): array
+    {
+        return $this->info;
+    }
 }

[...]

With some #[\SensitiveParameter] ? I'm not still sure when to add this attribute or not

Having a free-form array where each transport can add anything looks like a bad idea.

In HttpClient we documented the standard info keys, and decorators can add their own things there alsp (e.g. the number of retries for the RetryableHttpClient). This works well. What's the alternative?

How can we move forward on that PR ? I think the @OskarStark solution is better than original. We don't want to put debug info but more info from return response if provided. Do you want me to make another PR with your solution directly ? Or could we update this one ? We've been waiting for this improvement for a long time now to pick the fees natively. Is the header is really necessary inside info (too much as @smnandre said) ?

Closing as this PR won't be fixed as is. If someone wants to continue working on this, please open a new PR, maybe based on @OskarStark idea.