full-disclosure - Re: Subject prefix changing! READ THIS! SURVEY! !

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20030822150916.GB5230@talus.logic.net>
From: esm at logic.net (esm@...ic.net)
Subject: Re: Subject prefix changing! READ THIS! SURVEY! !

Option 1, please.

-- 
Edward S. Marshall <esm@...ic.net>
http://esm.logic.net/

Felix qui potuit rerum cognoscere causas.

> -----Original Message-----
> From: Chris Cappuccio [mailto:chris@...dia.net]
> Sent: donderdag 21 augustus 2003 19:43
> To: full-disclosure@...ts.netsys.com
> Subject: [Full-Disclosure] Subject prefix changing! READ THIS! SURVEY!!
> 
> 
> Hey folks,
> 
> ALL LIST MEMBERS ARE ENCOURAGED TO RESPOND AND MAKE A CHOICE AS TO HOW
> THEY WANT THIS BASIC FUNCTION OF THE LIST TO CONTINUE OPERATING. 
> 
> The subject header is going to change.
> 
> This is a survey to see whether people want:
> 
> 1. To have no subject prefix, that is, we remove [Full-Disclosure]
> or
> 2. To shorten the subject prefix from [Full-Disclosure] to [FD]
> or 
> 3. Do nothing
> 
> 1. The first choice is preferable for me and, I would hope, for most folks. 
> Len says he didn't really want it when he started the list anyways.  So we
> are
> actually going to change it now.
> 
> 2. Choice two may be preferable for people who can only filter their
> incoming
> messages based on the subject prefix.  So, if you WANT there to continue
> to be a subject prefix, SPEAK UP!!!
> 
> 3. Choice three sucks and if anyone wants this SPEAK UP so we know just
> how many people want this.  This is the least preferrable as it clutters
> the Subject header and makes the list harder to read through for those of us
> using a text based e-mail client.
> 
> For those of you using procmail or a compatible filter, a good match
> for Full-Disclosure that relies on headers you will always see in
> list messages goes like this:
> 
> :0:
> * ^Sender.*full-disclosure-admin@...ts\.netsys\.com
> full-disclosure
> 
> That matches this header:
> 
> Sender: full-disclosure-admin@...ts.netsys.com
> 
> Alternately, you can tell your Pegasus/Mozilla/Outlook/OE/Whatever
> to match on this header.
> 
> -- 
> Nullum magnum ingenium sine mixtura dementiae fuit -- Seneca
> 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html