If it is a serious flow of mail, i would see if it can be filtered out on the dadisman text at the ISP level. -- Nate Eckstine (DoIT CityWide Webteam) City of Seattle Department of Information Technology 700 Fifth Ave. Suite 2700 Seattle, WA 98124-4709 USA (206) 733-9658 >>> Listserv Admin <[log in to unmask]> 7/27/2007 11:46 AM >>> Hello Marty, Yes - this started here on July 20th non-stop and is still going strong. The variation of [log in to unmask], changes frequently, but one pattern that we can see in the logs is that quite often, e-mail is sent to both Listname-Request@ and Listname-L@, but always to the listname-request@ address first and in these cases the variation of [log in to unmask] is identical. What is a puzzle here is that some of this e-mail is going to only recently created Confidential= Yes mailing lists - so we don't know how they are getting the listnames. We anticipate problems if the time delay between sending to listname-Request@, presumably a subscription request, and to the corresponding Listname-L@ was increased, as some of our List Owners might approve/add the subscription. --Trish Trish Forrest Queen's University On Thu, 26 Jul 2007, Marty Hoag wrote: > I used to administer LISTSERV(tm) here long ago but the > current administrators came to me and I volunteered to check > with this list. We're having some mysterious behavior lately. > I just wanted to send a quick note to see if anyone else has > seen this or it is an old problem. We've just started looking > into this.