Listowners-L Archives

Archiver > Listowners > 2002-03 > 1016756943


From: "Malcolm Paterson" <>
Subject: Re: [LO] Reply to whom?
Date: Thu, 21 Mar 2002 19:29:09 -0500
References: <5.1.0.14.2.20020321174330.0577ccb0@tqsi.com>


Hi John,

Well...that certainly explains that. <blush> I should have asked my son.

I notice though that both of your replies contain a header called
Return-Path, which contains the list address in one case, and your address
in the other. But when I hit REPLY, it goes to your address in each case
(the FROM address).

Well, maybe there's someone out there who is more up to date and can explain
how it works. (Like Tim, maybe?? I think he explained it to me in the first
place.)

Cheers!
Malcolm
----- Original Message -----
From: "John B. Lisle" <>
To: <>
Sent: Thursday, March 21, 2002 5:58 PM
Subject: Fwd: [LO] Reply to whom?


> Malcolm,
>
> By strange coincidence, your own email does NOT have a REPLY TO header...
>
> I believe that REPLY TO is considered an obsolete header and no longer
> needs to be supported.
>
> I checked the recent messages to this list and neither AOL, OE, nor Eudora
> mail clients seem to use it. Pegasus does use it.
>
> When a mail client uses it, it will override the TO header. When a mail
> client does not use it, replies go to the TO address.
>
> If you select REPLY TO LIST, then a REPLY TO header is inserted in a
> message, IF one does not already exist... So, if someone using Pegasus
and
> activates REPLY TO, then all of their messages on a list that sets Replu
to
> List, will actually go back to the originator.
>
> john.
>
>
> >Return-Path: <>
> >Received: from lists5.rootsweb.com (lists5.rootsweb.com [63.92.80.123])
> > by iris.host4u.net (8.11.6/8.11.6) with ESMTP id g2LMS8S27439
> > for <>; Thu, 21 Mar 2002 16:28:08 -0600
> >Received: (from )
> > by lists5.rootsweb.com (8.10.1/8.10.1) id g2LMP9521715;
> > Thu, 21 Mar 2002 15:25:09 -0700
> >Resent-Date: Thu, 21 Mar 2002 15:25:09 -0700
> >X-Original-Sender: Thu Mar 21 15:25:09 2002
> >Message-ID: <00b701c1d127$4296e6c0$>
> >From: "Malcolm Paterson" <>
> >Old-To: <>
> >Date: Thu, 21 Mar 2002 17:25:09 -0500
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="iso-8859-1"
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >X-Mailer: Microsoft Outlook Express 6.00.2600.0000
> >X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
> >Subject: [LO] Reply to whom?
> >Resent-Message-ID: <>
> >To:
> >Resent-From:
> >X-Mailing-List: <> archive/latest/42179
> >X-Loop:
> >Precedence: list
> >Resent-Sender:
> >Status:
> >
> >My understanding (FWIW) of how this business works:
> >In every e-mail message there is a header called "REPLY TO". With MOST
> >e-mail software we have no control over what goes in that header;
> >everytime you send a message, it will contain your address. When you
> >receive a message and hit the reply button, the address in the "REPLY TO"
> >header of the message you are replying to becomes the TO address in the
> >reply, which you are then free to change. (That is the standard protocol;
> >some programs may not conform to it.)
> >
> >Now, with that in mind, go back to when Smartlist is sending out messages
> >to list subscribers. Smartlist is no ordinary e-mail program; it can and
> >does decide what to put into the "REPLY TO" header. If the "Reply-to-List
> >sw is set on, the list address goes into the header, otherwise it uses
the
> >same address which is in the "REPLY TO" header of the message to the list
> >which is being distributed; which will almost always be the address of
the
> >sender.
> >
> > >From the point of view of the list owner, the reply-to-list option
> > a)helps to keep traffic up and b) shows whether queries to the list are
> > receiving replies.
> >
> >Cheers!
> >Malcolm
> >
> >
> >==============================
> >To join Ancestry.com and access our 1.2 billion online genealogy records,
> >go to:
> >http://www.ancestry.com/rd/redir.asp?targetid=571&sourceid=1237
>
>
>
> ==============================
> To join Ancestry.com and access our 1.2 billion online genealogy records,
go to:
> http://www.ancestry.com/rd/redir.asp?targetid=571&sourceid=1237
>
>




This thread: