From: Marc Mutz (mutz@kde.org)
Date: Thu Apr 18 2002 - 07:52:01 CDT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 17 April 2002 18:49, Charles Lindsey wrote:
<snip>
> >I'm not sure about message-id, but at least Mutt creates In-Reply-To
> > headers that look like
> >--beg--
> >User-Agent: Mutt/1.3.16i
> >In-Reply-To: <3B2A52CC.839852AA@mandrakesoft.com>; from
> > mosfet@mandrakesoft.com on Fri, Jun 15, 2001 at 01:24:12PM -0500
> >--end--
>
> Now that is REAL ugly. Have they never heard of comments?
> Do they do the same thing with References?
No, it seems they don't.
> >So I assume that any mailer that masters the above header will master a
> >message-id with parameters, too (at least with one). But that's pure
> >guesswork.
>
> Does any mail system really care about the message-id, except when
> creating In-Reply-To or References?
I can't speak for other mailers, but KMail/KNode does or will use the
message-id to find the parent meassge for threading, obviously (or not so
obviously, since many users complain that we don't use the subject instead).
Also, Knode can mark an cross-posted article read in all groups when it has
been read in one group. KMail will get that feature eventually.
But these programs are not the problem. The problem are widely used, but
basically discontinued software such as NS4.
> My inclination is still to remain with 4c.
I have not much against remaining at 4c, actually. Going to 4d would simply
result in more backwards compatibility, which is esp. important with mail and
news, since they're not (only) on-the-wire, but also storage formats.
> Note that all that is expected of news agents is that they should
> tolerate/ignore everything after a naked ';'. It would do no harm for a
> mail agent to do the same thing, which I think means there is no problem
> for a mail+news agent that chooses to do so.
Of course. My concern is rather already deployed software. Allow parameters in
these headers and someone will use them for some obscure purpose and break
deployed agents.
Marc
- --
Marc Mutz <mutz@kde.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8vsFx3oWD+L2/6DgRAqShAKCr7852H676RDkbX29kfUsq6n7BSwCbBVFn
trARwWd7H5H0B6XmN/V3qmQ=
=fF0X
-----END PGP SIGNATURE-----