Here is one of two responses on the UCLAMAIL list.  Any comments Eric?
Duane
----------------------------Original message----------------------------
On Tue, 30 Apr 91 14:09:49 EDT,
   "Duane D. Weaver" <[log in to unmask]> said:
> Here at Ohio State, we are using ACCESS to send mail out to Internet.
 
My condolences.
 
> I believe that there is a problem with how ACCESS handles X-To: records.
 
The fault is equally LISTSERV's.
 
X-TO is the private protocol between UCLA/Mail and the UCLA ACP (and
hence Acces/MVS).  ACP converts SMTP MAIL FROM into X-FROM and SMTP
RCPT TO into X-TO.  UCLA/Mail uses X-TO to know who to deliver the
mail to.  This causes that unfortunate side effect with LISTSERV.
When I figured out that's what was causing duplicate mail on MVSTCPIP,
I put in
  *  X-Tags= Comment
in the list header, so the original header lines show up as
"Comment:  To:" instead of "X-To:".
 
As long as the UCLA ACP, Acces/MVS, (now called SNS TCP Access by
Interlink), and OpenLook from Network Solutions exist on the network,
it is not safe to have lists set up with the X- option -- original
header lines should be changed to Comment:.  My personal opinion is
that LISTSERV should not be changing the headers at all, but this is
the wrong list for that argument.
 
You should also beat on the vendor to accept and to generate BSMTP
instead of the terribly obsolete X-FROM/X-TO protocol, since you
probably can't get every list in the world changed.  We're now running
IBM's SMTP, which interfaces to UCLA/Mail via BSMTP.
 
 
/Leonard