From: Joseph Myers <joseph@codesourcery.com>
To: <overseers@gcc.gnu.org>
Subject: Re: GCC Bugzilla account creation configuration
Date: Fri, 11 Aug 2017 14:49:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1708111447360.11919@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.20.1708111425100.11919@digraph.polyomino.org.uk>
On Fri, 11 Aug 2017, Joseph Myers wrote:
> 2. Either enable HTML email for overseers and disable any aggressive spam
> filtering for the list, or create a new mailing list
> gcc-bugzilla-account-request that accepts HTML email, generally has no
> aggressive spam filtering and otherwise has the normal list configuration.
> Subscribe the people with access to create accounts to that list.
Note, regarding aggressive spam filtering: the filtering of messages with
confidentiality disclaimers should be *disabled* for this list, so that
people can just send email to it with their normal corporate email
configuration, even if it involves such disclaimers, and that will just
work.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-08-11 14:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 14:37 Joseph Myers
2017-08-11 14:49 ` Joseph Myers [this message]
2017-08-11 16:38 ` Christopher Faylor
2017-08-11 17:22 ` Joseph Myers
2017-08-11 17:42 ` Christopher Faylor
2017-08-11 18:11 ` Joseph Myers
2017-08-12 20:28 ` Gerald Pfeifer
2017-09-14 12:25 ` Frank Ch. Eigler
2017-09-14 12:33 ` Joseph Myers
2017-09-14 12:34 ` Frank Ch. Eigler
2017-09-14 22:26 ` Frédéric Buclin via overseers
2017-09-14 22:56 ` Joseph Myers
2017-10-03 21:47 ` Joseph Myers
2017-10-03 21:52 ` Frédéric Buclin via overseers
2017-10-07 21:44 ` Frédéric Buclin via overseers
2017-10-09 0:52 ` Joseph Myers
2018-03-03 23:09 ` Gerald Pfeifer
2018-03-04 14:07 ` Frédéric Buclin via overseers
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=alpine.DEB.2.20.1708111447360.11919@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=overseers@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).