From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Spam in the gnus-bug group
Date: Mon, 17 Apr 2006 11:44:02 +0200 [thread overview]
Message-ID: <m3u08sy1st.fsf@quimbies.gnus.org> (raw)
I've been kinda negative towards carrying the gnus-bug
non-mailing-list on Gmane because of all the "confidential" data in
the bug reports. I'm probably wrong on that count, but in any case,
the version on Quimby should be cleaned up.
So I'm doing that.
The rules I'm using is that any message that doesn't
1) have the word "gnus" in the body
or
2) doesn't have the string ".fsf@" in the Message-ID
or
3) doesn't have a References header
is probably spam, so I'm cancelling that.
And I've changed mail-to-news script on Quimby to use the same rules,
so if you're not posting with Gnus to gnus-bug@gnus.org, you should
say "Gnus" somewhere in the body. :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next reply other threads:[~2006-04-17 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 9:44 Lars Magne Ingebrigtsen [this message]
2006-04-17 11:10 ` Lars Magne Ingebrigtsen
2006-04-17 11:26 ` Lars Magne Ingebrigtsen
2006-04-17 11:56 ` Reiner Steib
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=m3u08sy1st.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).