From: David Brown <david.brown@linaro.org>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] Meta: Adding 'List-id' header to kernel-hardening posts
Date: Sat, 20 Feb 2016 10:12:07 -0700 [thread overview]
Message-ID: <20160220171207.GA89634@davidb.org> (raw)
In-Reply-To: <20160220033353.GA2139@openwall.com>
On Sat, Feb 20, 2016 at 06:33:53AM +0300, Solar Designer wrote:
>David,
>
>On Fri, Feb 19, 2016 at 11:25:38AM -0700, David Brown wrote:
>> I have been unable to locate a contact address for someone who
>> maintains this mailing list,
>
>That would mostly be me.
>
>> so I'm resorting to sending to the full
>> list. Apologies in advance for the noise this causes.
>
>There is:
>
>kernel-hardening-admin at lists.openwall.com
>
>This address is given in some of ezmlm's help texts.
>
>> I have noticed that this mailing list software inserts a non-standard
>> header to identify the list "Mailing-list:" instead of the RFC2919
>> (https://www.ietf.org/rfc/rfc2919.txt) "List-id" header. Depending on
>> the particular mail hosting and software, this can make filting on
>> this particular list either difficult or impossible.
>
>As Jason correctly pointed out, we do already have a List-ID header.
>Do you require it to be spelled List-id? I doubt that trying to match
>a specific case-sensitive spelling is a good idea, since if some client
>software is broken to only look for List-id, some other might only look
>for List-ID.
Sorry, I'd swear I looked for it. But, no there is no reason to
change the case of the header.
Thanks,
David
prev parent reply other threads:[~2016-02-20 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 18:25 [kernel-hardening] Meta: Adding 'List-id' header to kernel-hardening posts David Brown
2016-02-19 18:43 ` Jason Cooper
2016-02-20 3:33 ` Solar Designer
2016-02-20 17:12 ` David Brown [this message]
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=20160220171207.GA89634@davidb.org \
--to=david.brown@linaro.org \
--cc=kernel-hardening@lists.openwall.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.