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

Open Source and information security mailing list archives

Message-ID: <482C4D69-D44F-11D7-B3A2-00050219782F@xionic.net>
From: jkp at xionic.net (Jeff Pickell)
Subject: Subject prefix changing! READ THIS! SURVEY!!

Shorten it or don't change it....  just don't remove it altogether.  I 
am on several mailing lists and while I do filter things into different 
folders, it has always been easier if the subject contains a constant 
such as [Full-Disclosure].  I wouldn't say that it is strictly 
necessary, but it is easier when I am sorting through mail that has yet 
to be filtered.

Just my two cents....

Jeff Pickell

On Thursday, August 21, 2003, at 04:48 PM, Shanphen Dawa wrote:

> #1
>
> I know in sylpheed you can filter by some of the headers so a subject 
> line is kind of redudant.
>
> Looks like this:
>
> List-Unsubscribe: 
> <http://lists.netsys.com/mailman/listinfo/full-disclosure>,
> <mailto:full-disclosure-request@...ts.netsys.com?subject=unsubscribe>
> List-Id: Discussion of security issues 
> <full-disclosure.lists.netsys.com>
> List-Post: <mailto:full-disclosure@...ts.netsys.com>
> List-Help: 
> <mailto:full-disclosure-request@...ts.netsys.com?subject=help>
> List-Subscribe: 
> <http://lists.netsys.com/mailman/listinfo/full-disclosure>,
> <mailto:full-disclosure-request@...ts.netsys.com?subject=subscribe>
> List-Archive: <http://lists.netsys.com/pipermail/full-disclosure/>
>
>
> On Thu, 21 Aug 2003 10:43:02 -0700
> Chris Cappuccio <chris@...dia.net> wrote:
>
>> 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
>>
>
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html

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