In article <[log in to unmask]>, Al Hartshorn <[log in to unmask]> says: >Just in case, what would I look for in the mailer. I thought that listserv >punched directly to RSCS, being a trusted mailer. To do a proper analysis of how things ARE, one should do a DISTRIBUTE MAIL DEGUG=YES at the host listserv site. This tell us how things are effectively configured. Barring RSCS routing problems, one would then interrogate mailers at the various listserv distribution end-point. FOR LMAIL, the usual syntax is TELL MAILER AT bitnode SH R fqdn (Columbia mailer usually has the command SH DO fqdn) Though I am not 100% absolutely sure, it is my memory that LISTSERV does use the local mailer (or how else would LMAIL's mail forwarding process get involved ;-) ?) Though I don't know the particulars (I'm not a LISTSERV or mailer maintainer, LISTSERV has a domain name table to affect distributions -- that's one reason to run the DEBUG job). //Path.LISTNAME JOB Echo=yes DIST2 Mail Ack=Mail Debug=YES //TO DD * (insert output of a 'REV list (SH' here) /* //DATA DD *,EOF,Res=Disk Date: Fri, 28 Apr 1995 00:00:00 GMT From: Al <[log in to unmask]> Subject: delivery problem X-To: We are having trouble deliverying. /* -- co-owner INFOSYS, TQM-L, CPARK-L, ERAPPA-L, JANITORS, LDBASE-L, et -L [log in to unmask] "The Internet: it's changing" +1 814 863 1843 31 Shields Bldg. -- Penn State Univ -- University Park, PA 16802-1202 USA