The body of this email is in text/plain format,
includes consecurive dashes ( ----- ) and 4 backslashes ( \\\\ )
and also uses characters which are forbidden in html like those
used in <tags> and in &entities;
The reason I'm sending it is to verify the email formatting bug
reported in trac [1] is really fixed.
I'm also gpg-signing this email, just in case the gpg signature
stripping bug [2] was also fixed somehow.
I guess my email address will still be lost [3] upon hitting
Discourse topic watchers due to Discourse modifying the mail
but let's keep an eye on that too.
On Fri, Jan 12, 2024 at 11:23:22AM -0000, Martin Spott wrote:
Sandro Santilli wrote:
>
> --DG962+RbJVV7Aw4t
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> The body of this email is in text/plain format,
[...]
On Fri, Jan 12, 2024 at 12:49:40PM +0100, Sandro Santilli wrote:
On Fri, Jan 12, 2024 at 11:23:22AM -0000, Martin Spott wrote:
> Sandro Santilli wrote:
> >
> > --DG962+RbJVV7Aw4t
> > Content-Type: text/plain; charset=us-ascii
> > Content-Disposition: inline
> >
> > The body of this email is in text/plain format,
> [...]
>
> .... but it is still multipart,
Which one ? From myself or from Discourse ?
I don't know if you received my questions, Martin,
I think the mail you referred to was multi-part due
to a GPG signature I've added. I'm not adding one
to this mail, which should then be just text/plain
On Sat, 13 Jan 2024 at 19:25, Sandro Santilli <strk@kbt.io> wrote:
I don't know if you received my questions, Martin,
I think the mail you referred to was multi-part due
to a GPG signature I've added. I'm not adding one
to this mail, which should then be just text/plain
I'm receiving them as text/plain email, and mine should be also text/plain
[ intentionally sent to a single recipient being the SAC mailing list ]
On Sun, Jan 14, 2024 at 06:34:03AM +0100, Luca Delucchi wrote:
On Sat, 13 Jan 2024 at 19:25, Sandro Santilli <strk@kbt.io> wrote:
>
> I don't know if you received my questions, Martin,
> I think the mail you referred to was multi-part due
> to a GPG signature I've added. I'm not adding one
> to this mail, which should then be just text/plain
I'm receiving them as text/plain email, and mine should be also text/plain
Thanks, I confirm your was received here (via Mailman) as text/plain
as well, and passing DKIM authentication results from my server: