Thanks Pete, you were correct.  It turns out that it is my MTA because when
I tried with yahoo and msn (don't know why I didn't think to do that before)
it worked out great.  Now it's a matter of convincing people here that it
works everywhere else but.  The List-Address seems ideal but as I mentioned
before, Listserv uses the name part of the email I specify as the list name
on the web interface.  And, if I try to do anything by selecting the new
name, Listserv does not recognize it as a list on my server.

Has anyone out there experienced this problem?  Is it true that if you
specify a list-address with the name part being something other than the
actual list name, you can no longer do anything with it on the web interface
(outside of directly editing the URL to specify the actual list name) or is
there something I'm missing?


Pete....thanks again.
I'm hopping I can get the list-address to work properly but if not, your
idea is definitely my fall back.


----- Original Message -----
From: "Pete Weiss" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, March 16, 2004 4:34 PM
Subject: Re: MASKING THE LISTNAME/ADDRESS IN THE TO: LINE FOR A REGULAR
POST.


> At 15:32 03/16/2004 Tuesday, Claude Etienne wrote:
>
>  >Pete Weiss........Thanks but unfortunately, your suggestion didn't work.
I
>  >get a none deliverable message saying the address doesn't exist (which I
>  >expected because it is a fictitious address) and the list name still
appears
>  >in the TO: line with the actual recipient address in the BCC: line.
>
> I tried this myself this afternoon.  Subscriber set to IETFHDR, listname
> was in the BCC:, non-existent userid (valid hostname) in the TO:
> field.  Mail was transmitted and the listname did NOT appear in the
> TO:.  Mail did bounce from the non-existent TO:.  I could have sent it to
> a real userid.
>
> Depending upon your MTA, it may be that the listname will appear buried
> in the RECEIVED headers (like it did on mine).
>
>
> /Pete