Over the last few week we have encountered the following problems with
LISTSERV 1.8d.   I tried posting this to the Site Maintainers list but got
no
reply.

Note: We are running LSMTP and WINLSCP v1.1b built on Feb23 1999
23:56:53.   While writing this, I noticed that there appears to be a more
current build of LSMTP from LSOFT.

1) Subscribers can not change from Digest to Regular subscriptions with
wa.exe?SUBED1=list.  Either logged into LISTSERV or not, subscribers
change the radio button from Digest to Regular and the following command
is sent to LISTSERV: "SUBSCRIBE listname firstname lastname"

After confirming command, subscribers then get a message that they are
"already subscribed to the list" but no mention if their settings were
updated.
Subsequently, list owner can see that the setting for subscription is still
Digest.

Subscribers CAN change from Digest to Regular subscriptions with Set
commands via email.

Subscribers CAN change from Regular to Digest subscriptions with
wa.exe?SUBED1=list or using Set commands via email.

Administration (wa.exe?ACTMGR1=List) can successfully change subscription
from Digest to Regular or Regular to DIgest.

On May 6th downloaded and installed latest build of LISTSERV. After
restarting LISTSERV determined:

    Problem #1 - Still could not change from Digest to Regular

    2) LISTSERV Postmaster began receiving messages from LISTSERV
containing the following message, "...a DISTRIBUTE job that was rejected for
the following reason: "Job did not pass security checks". Job 0000..."

    3) Posts to two lists going to archives but not sent to subscribers.
Neither regular real-time posts or Digest was sent.  NOTE: Both of the
affected lists are using the MAIL-MERGE feature.  Not sure if other lists
had problem.  Took action as soon as problem detected.

Replaced .exe files in LISTSERV's MAIN folder with files from BACKUP folder
then restarted LISTSERV. Now:

    Problem #1 - Subscribers can not change from Digest to Regular with
wa.exe?SUBED1=list
    Problem #2 - Error messages not received
    Problem #3 - Posts being sent to subscribers