It is interesting to note that in the description of PRIMETIME in the site
guide refers to list config PRIME= in the following sentence:

PRIMETIME
Defines the "prime time" for your node, during which mail to lists
configured as "Prime= Yes" should not be processed.


But in the list owners guide, it is described as:

The default is "Prime= Yes", which means that LISTSERV will allow postings
to be processed during prime time. You can also explicitly code "Prime= No",
which means that LISTSERV will use the value in its PRIMETIME site
configuration variable to determine "prime time" for the list.

These seem to be exactly opposite of each other.  If logic serves me
correctly, one is true and the other is false.  Judging from Stan's message,
I would say that the first is true, and to prevent delivery during
PRIMETIME, code PRIME= YES in the list header.


-----Original Message-----
From: Stan Horwitz [mailto:[log in to unmask]]
Sent: Thursday, February 21, 2002 2:32 PM
To: [log in to unmask]
Subject: Issue with PRIME keyword


I am trying to limit the time of day when certain lists can distribute
mail. This is with Listserv 1.8d on Tru64 Unix.

In the go.user file, I coded:

  PRIMETIME= 'MON-FRI: 10:00-17:00'

I restarte Listserv. In a test list, I coded "Prime= No". I then posted a
message to that list and the message was distributed immediately instead
of after 18:00. Why?

As far as I can tell, I am following the documentation correctly, but it
seems to make no difference at all.