On Sunday 17 June 2007 18:54, Stevens wrote:
> OK, Patrick, and others, let me take one last stab at this.
>
> First, Schultz said:

There is no 't' in my surname. And I do not like to be referred to by my 
family name alone.


> > Please learn not hijack existing threads. Using your mailer's Reply
> > function (for the convenience of getting the To: address filled in
> > for you) followed by complete replacement of the Subject: is _not_
> > the way to start a new topic. Use your mailer's "new message"
> > command.
>
> I guess I don't fully understand that one.

OK. There is an optional header in each email that is a reply to an 
existing message, In-Reply-To:, that links that message to the one to 
which it replies. This allows mail clients to display messages in a 
hierarchical view. Only when a new message is posted, one that is not a 
reply to an earlier message, is the In-Reply-To: header not present.

Whenever you use the "reply" function of your email client, it takes the 
Message-Id: header field of the message being "replied" to and uses its 
value in the In-Reply-To: field. Thus, regardless of the content of the 
Subject: header, your message is displayed by receiving mail clients in 
relationship to the message to which it is a reply, even if you did not 
intend it to be such a reply.

That is why it is inappropriate to use the "reply" function when you're 
starting a new topic.

If you want to be spared the effort of entering the destination (To:) 
address, use an address book entry or other feature of your mail client 
to free you of this tedium. Like many users of KDE on Linux, I use 
KMail, and it allows each mail folder to be associated with a mailing 
list, including its posting address. Thus, I never have to enter such 
repetitive information. I just issue the "New Message To List" command, 
and proceed directly to entering the Subject: and thence to the content 
of the message.


> ...
>
> Fred


Randall Schulz
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to