Patrick Ben Koetter writes:
> X-Mailman-Approved-At
> lose the X-prefix
> Modify to: List-Approved-Date
> Next Step: Create RFC or Extend RFC 2369?
New RFC. Once you get to the RFC stage, you don't modify them (even
for typos, they publish errata).
> X-Topics
> This co
* Murray S. Kucherawy :
> > -Original Message-
> > From: mailman-developers-bounces+msk=cloudmark@python.org
> > [mailto:mailman-developers-bounces+msk=cloudmark@python.org] On Behalf
> > Of Patrick Ben Koetter
> > Sent: Sunday, October 30, 2011 12:04 PM
> > To: Mailman Developers
> -Original Message-
> From: mailman-developers-bounces+msk=cloudmark@python.org
> [mailto:mailman-developers-bounces+msk=cloudmark@python.org] On Behalf Of
> Patrick Ben Koetter
> Sent: Sunday, October 30, 2011 12:04 PM
> To: Mailman Developers
> Subject: [Mailman-Developers] Mai
I've created a list to sum up the current discussion/threads on the mailman
header work.
The list is separated in four sections:
I. CLARIFY
Needs discussion.
II. MODIFY
Needs to be registered with IETF or changes X- name.
III. KEEP
Do not change
VI. DELETE
Remove from M
