From: Lucien Murray-Pitts <lucienmp.qemu@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
John Snow <jsnow@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Peculiar reply from mail list handler???
Date: Tue, 8 Oct 2019 21:54:58 +0900 [thread overview]
Message-ID: <CALvKS=Ht-2zkdM8LxwyTYcVrg6ALoG099GZgkZcOzPW+P7rV0g@mail.gmail.com> (raw)
In-Reply-To: <e01f0c12-cd2f-d2f0-aac3-b8145239c45b@redhat.com>
On Tue, Oct 8, 2019 at 8:29 PM Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>
> On 10/5/19 9:09 PM, Peter Maydell wrote:
> > On Sat, 5 Oct 2019 at 18:13, John Snow <jsnow@redhat.com> wrote:
> >> I'm not clear on the particulars of mail delivery protocols or what
> >> lists.sr.ht is, but we indeed do not like HTML mail sent to this list.
> >
> > I suspect the lists.sr.ht address is just some subscriber to the
> > QEMU mailing list -- the list server sent your mail to all
> > the subscribers, including that one, which then complained
> > to you. But the QEMU list itself is OK with HTML email
> > (we prefer plain text, but we don't reject HTML).
>
> I subscribed to sr.ht some time ago to test the service because they
> provide a CI, git hosting, mailing list, so this might come from my
> account. If so, I'm surprise it send email on the subscriber behalf.
>
> Per https://man.sr.ht/lists.sr.ht/etiquette.md#plain-text:
>
> Rich text is not desirable for development-oriented email
> conversations, so you should disable this feature and send
> your email as "plain text". Every email client is different,
> you should research the options for your specific client.
> HTML emails are rejected by all sr.ht services.
>
> Surprisingly there is no option to allow HTML... (plain text is a design
> feature).
Yep, I forgot to change it and was intending to just write a quick message
without having to fire up my Linux box. Had a "damn it" moment the
second the reply bounced back.
But was a little more concerned the list had its own issues as the
domain looked a little suspect at first glance (I hadnt seen it before,
and the style looks unusual / lazy )
Anyway, something directly mailed back. And yes I will see where the
gmail "plain text first" options are so I dont mess it up again
Cheers,
Luc
prev parent reply other threads:[~2019-10-08 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 11:55 Peculiar reply from mail list handler??? Lucien Murray-Pitts
2019-10-05 17:12 ` John Snow
2019-10-05 18:09 ` Lucien Murray-Pitts
2019-10-05 19:09 ` Peter Maydell
2019-10-08 11:28 ` Philippe Mathieu-Daudé
2019-10-08 12:54 ` Lucien Murray-Pitts [this message]
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='CALvKS=Ht-2zkdM8LxwyTYcVrg6ALoG099GZgkZcOzPW+P7rV0g@mail.gmail.com' \
--to=lucienmp.qemu@gmail.com \
--cc=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).