I think your addressing problem (with Netcom's mailer) is created by
LISTSERV descriptions which are so long that they cause the text of the
LISTSERV message Sender or Reply-To header field(s) to be folded onto
two lines (or perhaps simply that the field is too long and Netcom
drops the text beginning with "<" (that contains the userid@fqdm).
(See OFFENDING HEADER? comment by me, below.)
 
I've seen this problem before, with Netcom users of LISTSERV lists with
long descriptions.
 
I'd argue, if I'm right about the cause, and if the cause (the long
descriptive text) is not contravening some RFC protocol spec, that
the Netcom users ought to go back to Netcom and insist that it produce
a conforming mail user/transport agent.
Peter R.
 
> Date:         Thu, 6 Jun 1996 10:36:52 -0500
> From: "Ingrid H. Shafer" <[log in to unmask]>
>
> ---- Begin Forwarded Message
> Date:         Wed, 5 Jun 1996 15:34:29 -0500
> Reply-To: Assoc for rights of Catholics in church-arcc (OFFENDING HEADER?)
>               <[log in to unmask]>
> Sender: Assoc for rights of Catholics in church-arcc  (OFFENDING HEADER?)
>               <[log in to unmask]>
> From: Ingrid Shafer <[log in to unmask]>
> Subject:      If you have technical problems . . .
> To: Multiple recipients of list VATICAN2 <[log in to unmask]>
>