From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: gdb@sourceware.org
Subject: Re: Posting from work/university addresses
Date: Sun, 05 Aug 2007 05:07:00 -0000 [thread overview]
Message-ID: <20070805050748.GA12733@ednor.casa.cgf.cx> (raw)
In-Reply-To: <200708042355.23161.rgetz@blackfin.uclinux.org>
On Sat, Aug 04, 2007 at 11:55:23PM -0400, Robin Getz wrote:
>On Sat 4 Aug 2007 20:03, Christopher Faylor pondered:
>>On Sat, Aug 04, 2007 at 09:50:48PM +0300, Eli Zaretskii wrote:
>>>>From: Ian Lance Taylor
>>>>Date: 04 Aug 2007 11:32:44 -0700
>>>>
>>>>As far as I can tell, you are requesting that we not do anything dumb,
>>>
>>>No, that's not it. My problem is that I don't see the motivation for
>>>rejecting such messages spelled out anywhere. The URL you mentioned
>>>_advises_ to do something, but, AFAIU, there's some policy issues
>>>involved here, which are not explained anywhere.
>>
>>Actually, the words politely requires that confidentiality notices not
>>be included. Since that was the best we could do until recently we
>>relied, unsuccessfully, on people to do the right thing. I've been
>>promising people for years that I'd modify the spam software enforce the
>>policy and a recent discussion on the gcc channel prodded me into taking
>>action.
>
>Is the concern of publishing the regex that people would modify things to get
>around it? Or why not just publish it somewhere?
No one ever said that there was a concern about publishing a regex.
That is an ongoing fiction developing in this thread. The system isn't
operational now. I said I'd send out more details when it was about to
go live. I'm obviously not going to send a stream of consciousness here
as I tweak things.
If you want to look at the current spam-blocking regexes they are here:
http://cygwin.com/cgi-bin/cvsweb.cgi/infra/ml-data/?cvsroot=sourceware
The 'bad_*' are the regexes which are the final defense triggered when
spamassassin, qpsmtpd, and clamav have let spam/viruses through.
The disclaimer regexes will eventually go in the "bad_keywords" file.
Finally, if you want to find out about rationales for policy decisions
then please use the overseers mailing list.
cgf
next prev parent reply other threads:[~2007-08-05 5:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 8:14 Why does gdb implement 'next' command with a series of "vCont;s"? congli
2007-07-30 22:12 ` Posting from work/university addresses Jim Blandy
2007-07-31 0:08 ` Anmol P. Paralkar
2007-07-31 1:08 ` Christopher Faylor
2007-08-02 16:58 ` Robin Getz
2007-08-02 17:12 ` Robert Dewar
2007-08-02 17:42 ` Robin Getz
2007-08-02 18:09 ` Ian Lance Taylor
2007-08-04 17:36 ` Eric Weddington
2007-08-02 18:23 ` Jim Blandy
2007-08-02 18:34 ` Christopher Faylor
2007-08-03 12:05 ` Eli Zaretskii
2007-08-03 14:27 ` Christopher Faylor
2007-08-03 14:39 ` Ian Lance Taylor
2007-08-03 17:10 ` Eli Zaretskii
2007-08-03 23:11 ` Christopher Faylor
2007-08-04 8:41 ` Eli Zaretskii
2007-08-04 18:36 ` Ian Lance Taylor
2007-08-04 18:51 ` Eli Zaretskii
2007-08-05 0:03 ` Christopher Faylor
2007-08-05 3:51 ` Robin Getz
2007-08-05 5:07 ` Christopher Faylor [this message]
2007-08-05 12:03 ` Robert Dewar
2007-08-05 18:27 ` Christopher Faylor
2007-08-06 6:53 ` Eli Zaretskii
2007-08-06 14:04 ` Ian Lance Taylor
2007-08-06 14:22 ` Eli Zaretskii
2007-08-04 20:04 ` Bob Rossi
2007-08-05 0:06 ` Christopher Faylor
2007-08-05 1:58 ` Bob Rossi
2007-08-05 3:13 ` Eli Zaretskii
2007-08-05 4:33 ` Christopher Faylor
2007-08-06 14:07 ` Ian Lance Taylor
2007-07-31 7:59 ` Wenbo Yang
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=20070805050748.GA12733@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=gdb@sourceware.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