You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my email clients (both Yandex web mail client and Mailspring) it got rendered as this:
It obviously tried to send a HTML message, but something was very mangled during the sending. Looks like the (multi-line?) subject was somehow interleaved with the actual message body: probably the subject was meant to be "https://t.me/radio_t_chat/65425 Grigory Bakunov, [11.07.2...", but the mail server has inserted its headers in between the subject lines, so the message structure was completely destroyed, and the headers Content-Type and Content-Transfer-Encoding went to the message body instead of the message header.
The Unicode message text then got broken due to missing Content-* headers.
Probably, it has something to do with the link in the first line of the message? Dunno.
For comparison, here's a non-broken message I've received a while ago:
@rexim, sorry to bother you, but have you, too, received this message in broken form? I wonder if it's something about my email provider or about the loglist itself.
Today I've received a email with the following body from loglist:
In my email clients (both Yandex web mail client and Mailspring) it got rendered as this:
It obviously tried to send a HTML message, but something was very mangled during the sending. Looks like the (multi-line?) subject was somehow interleaved with the actual message body: probably the subject was meant to be
"https://t.me/radio_t_chat/65425 Grigory Bakunov, [11.07.2..."
, but the mail server has inserted its headers in between the subject lines, so the message structure was completely destroyed, and the headersContent-Type
andContent-Transfer-Encoding
went to the message body instead of the message header.The Unicode message text then got broken due to missing
Content-*
headers.Probably, it has something to do with the link in the first line of the message? Dunno.
For comparison, here's a non-broken message I've received a while ago:
The text was updated successfully, but these errors were encountered: