>Thanks for the quick response.  Two more questions interspersed below.
>
>  >[. . .] An address starts being monitored
>  >when LISTSERV receives a bounce (in a format it understands) for the
>  >address in question.
>>
>>If four consecutive days pass without another bounce being received,
>>the address is no longer monitored.
>>
>>If another bounce is received on day #4 the address is removed.
>
>Hmm.  But this would be only the second bounce.  Still removed?

Yes.

It may help to think about this in terms of a discussion mailing
list.  Say you've got a reasonably lively discussion mailing list
that gets about 50 messages a day (with some really busy days and
some days where nobody posts much).  The question is, how can you
tell when an address is really bad?

One method is to wait four days (or whatever) and see if the address
is still bouncing.  This is the Delay() method.  (Note that with this
method you're not counting bounces or trying to match them up with
the original messages in any way; you're looking on day 4 to see if
there are any bounces for the address, and if they are, the address
fails the test.)

The other is to see if you all of your messages are bouncing.  So if
you get, say, a hundred fifty bounces in four days then all or most
of the messages are bouncing and you might as well remove it.  This
is the Max() setting.

The above criteria correspond to Delay(4),Max(150).  If an address
fails either test it gets removed.

[. . .]
>  >>2. Suppose one error happens every day for the next 3 days.  Is the
>>>subscriber removed from the list on the 4th day.
>>
>>No.
>
>hmm - but this would be 4 bounces in  4 days.  One for the first
>day, one each on the next 3 days.
>Want to take back your "No"?

Whoops.  I misread this.  You're correct, the address would be
removed on day #4.

Sorry about that,
--
Jacob Haller, Technical Support
L-Soft international, Inc
http://www.lsoft.com/