LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Pete Weiss <[log in to unmask]>
Thu, 28 Feb 2002 08:53:13 -0500
text/plain (35 lines)
IMHO, this situation is so unlikely that for L-Soft to devote their human
resources to "fix" it does not sound as productive as other coding tasks.

For a PRIVATE+REVIEW subscriber to post and then UNSUBSCRIBE before the
moderation has taken place seems like a rogue subscriber. Since LISTSERV
has the list definition option of NOTIFY=YES, unless you are getting lots
and lots of UNSUBS, it should be relatively easy to spot these lame
posters, espcially if you have gone through this exercise more than once.

Having said this, the list-owner FAQ could be updated (if it isn't
already there).

/Pete Weiss

At 17:10 02/27/2002 Wednesday, Siegfried Schmitt wrote:
 >I have just observed a problem on a list with
 >
 >   send = private
 >
 >when the review option is set for a subscriber. The subscriber sends a
 >message to the list and then he leaves the list *before* the editor can
 >approve the message. When the editor approves the message, he gets
 >a message saying "Message successfully approved." But the former subscriber
 >gets a message saying: "You  are  not  authorized
to  send  mail  to  the...".
 >and the message is *not* being distributed.
 >
 >I think the editor should be informed about this problem by a different
 >message saying something like: "Sorry, message ... could not be approved
 >because the original sender is no longer a member of list ...".
 >
 >Another solution for this problem might be to distribute the message based
 >on the approval of the editor alone and to ignore the fact that the
 >(former) subscriber does no longer have the right to post.

ATOM RSS1 RSS2