On 9/16/00 10:03 PM, Tom Rawson <[log in to unmask]> wrote...

> On 16 Sep 00, Ben Parker wrote:
>
>>> Is there a listserv setting that will reject messages with multiple
>>> address in the To: field?
>>
>> No.  However, unless you are using the IETFHDR setting, all multiple
>> addresses are replaced with the one List-Address in list messages.
>> So any extra addresses get removed/replaced.
>
> Well I have FULLHDR on my subscription ... most are set with SHORTHDR.
> But not IETFHDR.  On further research it seems the issue is that the
> sender used X-To and not To.  Here are the headers from a sample problem
> message (actual emails dummied in to keep from repeating them here too
> ...):
>
>  Date:         Wed, 13 Sep 2000 14:13:35 EDT
>  Reply-To:     [log in to unmask]
>  Sender:       Guatemala-Adopt <[log in to unmask]>
>  From:         Name <[log in to unmask]>
>  Subject:      Re: Out of Print Books?
>  X-To:         [log in to unmask], [log in to unmask], [log in to unmask],
>                [log in to unmask], [log in to unmask],
>                [log in to unmask], [log in to unmask], [log in to unmask],
>                [log in to unmask], [log in to unmask],
>                [log in to unmask], [log in to unmask]
>  To:           [log in to unmask]
>
>Is listserv going to pass along X-To as-is?  The addresses shown in X-To
>are in the archives too.
>
>Perhaps this is an AOL mail client behavior?  All the senders who did it
>this time were from AOL, though I can't tell if it's only their client
>that does this or if the others in the particular thread which most
>recently had this problem were simplyu more careful or more aware of what
>they were doing.

No, this is the LISTSERV putting all the other To recipients as X-To
headers, as per the X-Tags list keyword. Has nothing to do with AOL.


--
Adam Bailey    | Chicago, Illinois
[log in to unmask] | Finger/Web for PGP
[log in to unmask] | http://www.lull.org/adam/