LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

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

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

Print Reply
Melvin Klassen <[log in to unmask]>
Wed, 7 Aug 1996 09:09:09 PDT
text/plain (29 lines)
On Tue, 6 Aug 07:56 "Raymond G. Magauran, MD" <[log in to unmask]> wrote:
> I run a moderated list with each message to the list being confirmed via the
> "OK" mechanism. I have one subscriber/address that seems to give the
> listserv a bit of trouble. Each time I "OK" a message from him, it gets
> approved - using "OK" with or without the confirmation code in the text.
> However the message never gets posted. Instead the listserv sends to me the
> same message for confirmation, now with a new confirmation code - as if the
> message had be sent twice. If I confirm a second (or even a third) time,
> there is no change. The message never gets posted and a "new" confirmation
> request is processed with each cycle. Help?? Any suggestions appreciated.
 
I compared the first and second messages from the subscriber,
and it seems like the subscriber is *resending* the message:
+++
+ FILE 1    3           V1.2a/1.8a) with BSMTP id 5828; Tue, 6 Aug 1996 04:08:2
+ FILE 2    3           V1.2a/1.8a) with BSMTP id 3768; Tue, 6 Aug 1996 07:41:0
+ FILE 1    5     with TCP; Tue, 06 Aug 96 04:08:21 EDT
+ FILE 2    5     with TCP; Tue, 06 Aug 96 07:41:08 EDT
+ FILE 1    7            id aa25927; 6 Aug 96 8:08 GMT
+ FILE 2    7            id ai03529; 6 Aug 96 11:41 GMT
+ FILE 1    9            id aa22975; 6 Aug 96 9:06 +0100
+ FILE 2    9            id aa01189; 6 Aug 96 12:38 +0100
+ FILE 1   17  Message-ID: <[log in to unmask]>
+ FILE 2   17  Message-ID: <[log in to unmask]>
+++
 
Thus, it is *expected* that LISTSERV would ask for exactly *one*
confirmation per unique message.

ATOM RSS1 RSS2