[Klug-general] To Dan regarding apology and response to Bash/Curl advice
Julia Freeman
klug at quixotic.org.uk
Fri Apr 15 21:24:07 UTC 2011
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, Apr 15, 2011 at 10:08:13PM +0100, Mike Evans wrote:
>
>> Then it defeats the object of replying to a thread.
>>
> which, presumably, is why some readers include the option to "reply
> list" as well as "reply", and might apply different rules in each case.
> However, as few of us attend a training course each time a new version
> of a mail reader is released I would have to consult the help pages, and
> when I do I find it not particularly helpful or informative. So what
> I'll do is continue to do what I know to be safe, and less likely to
> cause a problem to others. I'll reply without changing the subject when
> I wish to continue a thread. Simple really.
Not quite, the reply should always use the correct header ala:
In-Reply-To: <4DA8936B.2 at gmail.com>
Regardless of whether you did a normal reply, or a list reply. What the
later actually does is look at the List-*: headers, which are inserted by
mailman with information on your email. A normal reply uses the
"Reply-To:" header, which says which address to reply to...
Now, mailman and majordomo allow you to do what is called "reply to
munging" which makes it change the "Reply-To:" header from the senders own
"Reply-To:" to that of the list. This is the default for most mailling list
systems. Some mailing list admins change this behaviour.
Should any of you feel like it, turn on view all headers in your mail
client and see the gooy interesting bits that you don't normally see.
I hope that makes some sense.
J
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFNqLVxpQ4p2TvRQNARApFEAJ9rmK2HB14iDu7RG0lbxbF8NUoqNgCg3fbP
gahSlO+9IRIJiEhD/J1g80I=
=P8/k
-----END PGP SIGNATURE-----
More information about the Kent
mailing list