public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. a73981bfb389142eb9563524c8023c524dce36c3 Date: Sun, 9 Aug 2020 04:38:16 +0000 (GMT) [thread overview] Message-ID: <20200809043816.BF44D3858D35@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via a73981bfb389142eb9563524c8023c524dce36c3 (commit) from 72ca39dacf00b1f40fa1ab6f82178a0b03f3d30e (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit a73981bfb389142eb9563524c8023c524dce36c3 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Sun Aug 9 07:37:13 2020 +0300 Rework note on spam to be more concise. diff --git a/htdocs/spam.html b/htdocs/spam.html index 8db948d4..61ee6209 100644 --- a/htdocs/spam.html +++ b/htdocs/spam.html @@ -17,40 +17,35 @@ want to run a list where only members can post).</p> <p>Some simple guidelines for how to deal with SPAM to the lists can help avoid creating unnecessary traffic:</p> -<pre> - - NEVER respond to SPAM, no matter *what* the message says about - "Remove" instructions. It is *quite* likely that, by responding, +<ul> + <li><em>Never</em> respond to SPAM, no matter what the message says about + "remove" instructions. It is <em>quite</em> likely that by responding you're simply sending the spammers more email addresses (such - as yours) to use and share with (or sell to) all the other - spammers throughout the world. - - - If the SPAM you receive came through a list you're on, it is - probably best to remove that list itself from the "To" and "Cc" - fields, unless your email is really for list members to *read*. + as yours) to use and share.</li> + <li><p>If the SPAM you receive came through a list, remove that list + itself should you decide to react after all, unless your email is + really for list members to read. + </p><p> That is, if *you* don't like SPAM, probably nobody else on the list does, and probably nobody wants to read how upset you are about the spam, because they're already just as annoyed. - + </p><p> Exceptions include email like this saying "people on this list - should not respond to spam *on this list*". ;-) - - Cc'ing the list maintainer in email to a postmaster somewhere - about spam might be okay, though. - - - NEVER respond to SPAM. I really mean this. That's why I - repeated it. If you want to *discuss* things related to the - SPAM, this means DO NOT INCLUDE ANY SPAMMER'S EMAIL ADDRESSES - IN THE LIST OF RECIPIENTS!!! - - Otherwise, not only is *your* email address "harvested" as a - future "we know there's a person behind this" address for spamming, - anyone who absent-mindedly responds to *your* email without - trimming the spammer's address (as I've done) also gets *their* - email address harvested this way. -</pre> - -<p>In addition to the above you may want to check out + should not respond to spam *on this list*". ;-)</p></li> + + <li><p><em>Never</em> respond to SPAM. Really. + If you want to *discuss* things related to the SPAM, do not + include spammers. + </p><p> + Otherwise, not only is your email address "harvested" as a + future "we know there's a person behind this" address, + anyone who absent-mindedly responds to your email without + trimming the spammer's address also gets their address + harvested.</p></li> +</ul> + +<p>In addition may want to check out <a href="https://www.abuse.net">www.abuse.net</a>.</p> </body> ----------------------------------------------------------------------- Summary of changes: htdocs/spam.html | 51 +++++++++++++++++++++++---------------------------- 1 file changed, 23 insertions(+), 28 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-08-09 4:38 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200809043816.BF44D3858D35@sourceware.org \ --to=gerald@sourceware.org \ --cc=gcc-cvs-wwwdocs@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: linkBe 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).