Ben Parker: Thanks for looking into this. I've passed your information on to our listserv administrator. >Thank you for bringing up this anomaly. I did some tests on your test list >and was able to duplicate your results. I also tested on 2 different servers >here at L-Soft. I believe it is a mail routing issue in your case. You are >using LISTSERV on OSF1-4.0 and PMDF as your mailer. PMDF, like a traditional >unix sendmail requires you to create the necessary mailer aliases for all >lists and ancillary addresses (listname-Request, listname-subscribe-request, >etc.) on your LISTSERV Server. Our LSMTP mailer (soon to be available for >unix) and the built-in SMTP Listener program do not require you to create >alaises, this is handled automatically. > >I don't know the details of your server but I presume when you inspect all the >aliases, there is some alias rule set such that anything *@listserv.uh.edu not >specifically routed otherwise goes to the LISTSERV@... command address and >thus produces the error you observed. On the L-Soft servers, I get a '550 no >such list' error, unless I specifically create an alias set to the List-ID >value. I'd still like to know why it makes an exception for the list owner. The list owner cannot duplicate this problem using his owner's address. Thanks. George Buckner Owner, Psyche-*, ASSC-*