Andrew, Thanks. But I'm still puzzled because, for example, I see failures for one address every day all month, but it isn't deleted. So the Delay(5) should catch the person regardless of the MAX(100). Since this is a high volume list, we really do want Max to be set high, or else a user's temporary "outage" will always result in an auto-delete (if I understand the parameters correctly, with this list's volume 100 may even be too low!) Or am I missing something? Nelson On Thu, 1 Dec 2005, Andrew Bosch wrote: >Adjust the Max() parameter to something much smaller than 100, depending >on list activity. If Listserv waits for 100 delivery errors or probe >failures for each affected address, then it will wait a long time before >deleting the address. > >andrew > > >>>> [log in to unmask] 12/1/2005 9:53:43 AM >>> >Every morning about 6 am I noticed a cpu spike. When I look at the >logs, I >see a daily AVERAGE for the last month of over 2000 probe failures for >a >list that has 11,783 subscribers (failures occur at about 6:15 am). >The >list header is. Any idea? I would think these would be auto-deleted. >Something dumb I'm missing? > >* >* >* Subject-Tag= >* Review= Owner >* Subscription= Open,Confirm >* Send= Private,NoMIME >* Reply-to= Sender,Respect >* Moderator= >* Language= NoHTML >* Attachments= No,Filter >* Errors-To= >* Confidential= No >* Validate= Yes,Confirm >* Auto-Delete= Yes,Full-Auto,Delay(5),Max(100) >* Renewal= 2-Monthly,Probe >* Sizelim= 600 >* Default-Options= Repro,Review >* Digest= Yes,Same,Daily,03:00,Size(550) > >* Daily-Threshold= 175 >