L-Soft international, Inc.
Site Manager's Operations Manual
LISTSERV®, version 1.8d
1 March 1999
1When using IIS version 4.0, you will likely get an Error(5) from
'wa' when trying to do things like search, post to the list, or anything else
that requires 'wa' to pipe a command to LISTSERV. We believe this to be due to a
bug in IIS 4.0 (the problem does not appear in IIS 3.0 or earlier), specifically
in the code that enables automatic password synchronization for the anonymous
user stage. The only fix our support group are aware of is to open the Internet
Service Manager, find the "wa.exe" executable in the tree, and then do the
At this point 'wa' should resume working again. You might need to type the
password for the IUSR_xxxx account but our experience was that you needed only
to uncheck the box and click "OK".
- Open the property sheet for "wa.exe" by double-clicking it
- Click on the "File Security" tab
- Under "Anonymous Access and Authentication Control", click on the "Edit..."
button, which pulls up a dialog box entitled "Authentication Methods"
- Click the "Edit..." button next to "Account used for Anonymous Access:"
which brings up a dialog entitled "Anonymous User Account"
- UNCHECK the box for "Enable Automatic Password Synchronization"
- Click "OK"
2There is an alternate method of doing this kind of merge which
requires access to the machine LISTSERV is running on. You can simply use the
'listview' program to output the list files in text format, and redirect them
into editable files (with 'listview -a listname > listname.txt', for instance).
Then you can use a text editor to combine the two lists and either mail the
resulting merged list to LISTSERV or store the merged file as listname.list and
restart LISTSERV to reformat the file (as explained above in 7.1). However, note
carefully that the latter method (save and restart LISTSERV) is not recommended,
nor is it the supported method for storing lists, as it bypasses a number of
checks LISTSERV does when you use PUT.
3If you are interested in the mechanics of starting a VM-type
filelist, the best reference is "Setting Up the LISTSERV File Server--A
Beginner's Guide" by Ben Chi (email@example.com). This publication is available
from LISTSERV@LISTSERV.NET as FSV GUIDE, or at ftp://ftp.lsoft.com/documents/fsv.guide .
4Under unix, all files accessed by LISTSERV must be named in lower
case (i.e., 'ls' must show site.catalog, not SITE.CATALOG or Site.Catalog).
Internally LISTSERV does not care about case since it translates everything to
lower case for the purpose of accessing the unix file system, and you may use
upper or mixed case within the catalog file itself.
5If your old archives are from Majordomo or ListProc you might want
to look at an unsupported Perl script found at
ftp://ftp.lsoft.com/CONTRIB/notebook-conv.pl which converts
sendmail-style notebooks to LISTSERV format. This is really ListProc-specific
but it would probably work with Majordomo archives. In any case this
user-contributed script is not supported in any way by L-Soft, so please direct
any questions about it to its authors.
6If your local machine is running MS-DOS and/or Windows 3.x,
obviously this will not work--you will have to conform to the 8.3 naming
convention. Probably the best thing to do in this case is simply name the file
listname.mai, then rename it when you upload it to a mainframe or network
workstation account (or use the web administration interface described in
chapter 11, instead).
7Thanks to Marty Hoag of NEW-LIST.
8WWW_ARCHIVE MAILTPL is searched only for web-related template forms
and is bypassed for mail template forms. For instance WWW_ARCHIVE MAILTPL will
not be searched for ADD1 but will be searched for WWW_INDEX.
9The digests conform to RFC1153 with an acceptable deviation from the
recommended subject line (verified with the RFC author).
Site Manager's Operations Manual for LISTSERV®
Appendix A: System Reference Library for LISTSERV®
Appendix B: List Keyword Reference for LISTSERV®
Appendix C: Site Configuration Keyword Reference
Appendix D: Sample Boilerplate Files
Appendix E: Related Documentation and Support
Appendix F: Acknowledgements