From: Russ Allbery (rra@stanford.edu)
Date: Wed Jun 30 2004 - 08:23:14 CDT
Henry Spencer <henry@spsystems.net> writes:
> I have to concur on this. Distasteful though it is, cmsg hasn't
> entirely gone away, and it's a genuine interoperability problem. We
> don't want to sanction its continuing use -- it *is* a botch -- but
> forbidding Subject content to begin with "cmsg " is desirable.
I'm not sure that I actually disagree with this approach, but I think we
should think a little about whether banning cmsg is the best transitional
step forward. Currently, it is standard practice for all control messages
to be generated with both a Control header and Subject: cmsg. It's not
clear to me that forcing all control message generators to change to a
different subject gets us any closer to where we want to be.
Maybe we should just ban cmsg for non-control messages? (That might have
even been what you meant.) Regardless of what we do, we should clearly
mark this as transitional, so that implementors are aware that later this
may well become acceptable Subject content again.
-- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>