From: Stewart Smith <stewart@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
ppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: administrivia: mails containing HTML attachments
Date: Wed, 16 May 2018 09:46:15 -0500 [thread overview]
Message-ID: <87k1s3y7yg.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180516144829.2dbefb0b@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> I have decided that any email sent to the linuxppc-dev mailing list
> that contains an HTML attachment (or is just an HTML email) will be
> rejected. The vast majority of such mail are spam (and I have to spend
> time dropping them manually at the moment) and, I presume, anyone on
> this list is capable of sending no HTML email.
certainly one way to get those pesky IBM Verse users off. To be fair,
Documentation/process/email-clients.rst also warns them appropriately.
I fully support ditching HTML mail.
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2018-05-16 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 4:48 administrivia: mails containing HTML attachments Stephen Rothwell
2018-05-16 7:07 ` Gabriel Paubert
2018-05-16 14:46 ` Stewart Smith [this message]
2018-05-17 1:42 ` Andrew Donnellan
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=87k1s3y7yg.fsf@linux.vnet.ibm.com \
--to=stewart@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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).