I have LISTSERV installed on my machine called WWW.MYCORP.COM, but when I send mail to it, it says something like "...no such user."


There are several possibilities.


Does WWW.MYCORP.COM get its mail via a mail exchanger? If so, the error may actually be coming from the mail exchanger rather than from the machine LISTSERV is running on. You may be able to fix this problem by having the system administrator change the DNS records for WWW.MYCORP.COM so that mail goes directly to the LISTSERV machine, or by adding a mail alias that redirects mail sent to the non-existent LISTSERV account on the mail exchanger machine to LISTSERV@WWW.MYCORP.COM.


Is WWW.MYCORP.COM the only name for your machine? Check with your system administrator to see if there are any variant CNAMEs or MX records in the DNS that point to your machine. If so, you just need to add these aliases to the MYDOMAIN variable in LISTSERV's site configuration file. This is particularly important when running under Windows.


If running under Unix, did you create the Sendmail aliases for listserv and owner-listserv as outlined in the Installation Guide?


If you are running the Windows version and your bounces look like this:


Connected to listserv.myhost.com:                

>>> RCPT To:<listserv@listserv>        <== note the unqualified hostname

<<< 550 Recipient not local.                      

550 listserv@listserv.myhost.com... User unknown

550 error... User unknown                        


then the sendmail on your local mail host isn’t fully-qualifying addresses on outgoing mail within the local domain. You may be able to work around this by adding the unqualified name of the host (in this case LISTSERV) to the MYDOMAIN= variable in SITE.CFG. In other words, MYDOMAIN= should look something like this:


MYDOMAIN= LISTSERV.MYHOST.COM LISTSERV


After you make this change, stop and restart both LISTSERV and the SMTPL.EXE "listener".


The Windows versions running with the SMTPL.EXE "listener" are quite picky about their own addresses. Since the listener has no way to resolve the unqualified host name, unless you explicitly specify it in the site configuration file, the listener will reject it as not being local.


For unix hosts, please note that there is no good technical reason to run a mail server with host name qualification disabled, and if it is feasible, you should actually turn this option on in your sendmail configuration rather than apply the MYDOMAIN workaround.