> I am about to embark on testing the auto-delete function of version 1.8c > running on VM. Has anyone out there been running it under version 1.8c and > how is it performing? > > Thanks, > Debbie Kodora > Listserv Administrator HQDA Auto-Delete is a very useful function for a high-activity list. At least in its default configuration, it's not useful for a low activity list (especially ones that aren't posted to every day) and can actually keep bad addresses from ever being deleted from such a list. It might be OK for a low activity list with parameter adjustments, but it may be just as easy to turn it off. Of course, many bounce messages are not in a format that LISTSERV can understand (DSN, Delivery Status Notification, RFCs 1891-4). Those you will still get. For those errors it does understand, LISTSERV seems to process bounces for addresses that aren't subscribed to the list. Since LISTSERV eats the bounce message, important trace information can be lost. So far that hasn't been a major problem for me -- I just have to watch the error monitor report and manually deal with addresses that have error counts that constantly increase past the deletion threshold. It may become more of a problem as more bounces get sent in DSN format and get handled by Auto-Delete. I wish there were an option to see the bounce message that caused a user to be deleted, as I like to save those in case someone asks why they were deleted. I find the explanation to be more effective when I enclose a copy of an error message. You may also want to have a look at the Probe feature. It may meet your needs better than plain Auto-Delete. Look under the Renewal keyword in the 1.8c documentation. P.S. - My experience with Auto-Delete is with Unix LISTSERV. I don't know if there are any significant difference with the VM version. Roger Fajman Telephone: +1 301 402 4265 National Institutes of Health BITNET: RAF@NIHCU Bethesda, Maryland, USA Internet: [log in to unmask] Postmaster: CU.NIH.GOV, LIST.NIH.GOV, MAILFWD.NIH.GOV, PACKET.NET.NIH.GOV List owner: LANMAN-L, PCIP, SNSTCP-L, and TN3270E, all @LIST.NIH.GOV