L-Soft international, Inc. Year 2000 Compliance FAQ

  1. Is LISTSERV Y2K compliant?
    Beginning with version 1.8d, LISTSERV is Year 2000 Compliant under all supported architectures except for VM, contingent on operating system support for Year 2000.

    LISTSERV 1.8d for VM has the code for Year 2000 compliance but has not yet (as of 1 March 1999) been certified Year 2000 compliant. Testing to-date has not revealed any problems, but is not completed on VM.

  2. How can I tell what version of LISTSERV I am running?
    Send the command "SHOW LICENSE" to LISTSERV. The last item on the response from LISTSERV is "Build date" -- this should be 26 Feb 1999 or later. If the build date reported by LISTSERV is earlier than this (even if it is reporting to be 1.8d) you should install the latest build.

  3. What should I do if I have a version of LISTSERV prior to 26 Feb 1999?
    If you are currently running version 1.8c or earlier or a beta build of version 1.8d , you should upgrade to the latest build of version 1.8d. If you have current maintenance, this is a free upgrade. Contact your sales representative to obtain a 1.8d LAK if you do not already have one.

  4. Is LSMTP Y2K compliant?
    Beginning with version 1.1b, LSMTP is Year 2000 Compliant under Windows NT, contingent on operating system support for Year 2000.

    LSMTP 1.1b is still undergoing testing under OpenVMS, Tru64 Unix (Digital Unix), and Solaris.

  5. How can I tell what version of LSMTP I am running?
    In the WINLSCP program, pull down the Show menu and select "Version & License". Alternatively, you can use the command line "LSCP SHOW VERSION". The version reported should be 1.1b and the date should be Feb 23 1999 or later.

    If the build date reported by LSMTP is earlier than this, you should install the latest build.

  6. What should I do if I am running a version of LSMTP prior to Feb 23 1999?
    If you are currently running version 1.1a or earlier or a beta build of version 1.1b , you should upgrade to the latest build of version 1.1b. If you have current maintenance, this is a free upgrade. Contact your sales representative to obtain a 1.1b LAK if you do not already have one.

  7. Is LMail Y2K compliant?
    Beginning with version 1.2d, LMail is Year 2000 Compliant, contingent on operating system support for Year 2000.

  8. How can I tell what version of LMail I am running?
    From the console of your VM login, issue the command "TELL MAILER SHOW VERSION" (this assumes that LMail is running under the MAILER account; if it is not, then issue the command to the user account LMail is running under). The response includes a line indicating the version number. If you are running a Y2K compliant version of LMail, this version number will be 1.2d or later.

  9. What should I do if I am running a version of LMail prior to 1.2d?
    If you are currently running version 1.2c or earlier, you should upgrade to the latest version, 1.2d. If you have current maintenance, this is a free upgrade. Contact your sales representative to obtain a 1.2d LAK if you do not already have one.

  10. What does it mean to be Y2K compliant?
    On any operating system which is Y2K compliant:
    • The product will not terminate unexpectedly on January 1, 2000 or on February 29, 2000 due to incorrect date manipulation.
    • Functions that use date ranges including dates on either side of these two dates will work as expected.
    • Functions that accept date parameters using a 2-digit year format will make an appropriate assumption about the 4-digit year represented.

  11. Does that mean LISTSERV uses 4-digit years everywhere?
    Not necessarily. It uses 4-digit years for all the user-friendly displays, inside log files, etc., but internally it can understand 2-digit years.

    For example in the web archive interface, the archives are listed with 4 digit years and are sorted in the correct order. However, a user can enter a search term using a 2-digit year, and LISTSERV will make the appropriate guess as to the first 2 digits of the year.

    Some internal file-naming conventions that have always used 2-digit years will continue to do so, for example the monthly archives are stored as LOGyymm. This file-naming convention was preserved in order to avoid breaking programs that users may have written to process the archive files. LISTSERV processes these files correctly, however, so there is no compliance issue.

  12. Is L-Soft’s infrastructure Y2K safe?
    We are confident that the support and services you are accustomed to getting from L-Soft will not be seriously affected by the rollover to the year 2000. All the operating systems and key applications we use for operations and production are year 2000 compliant. We are working on adding a year 2000 clause to our lease (including utilities) and to the contract with our phone company. All our mail servers run LSMTP, so our ability to support customers through email will not be affected. Our internet connection is through Digex, who inform us that the majority of their Y2K effort is already completed, and expect the remainder to be completed by September 30, 1999.


All terms and conditions in contracts between L-Soft international Inc. and the customer (Software Licensing Agreements, Outsourcing Agreements, etc.) apply, including but not limited to Warrantee and Limitation of Liability. Error processing SSI file