Without looking at the list headers, log files, or the message itself, I can only make an educated guess, but I'd suppose this to be a looping message. Usually LISTSERV is good about detecting looped messages, but the list configuration in conjunction with the nature of the loop may have defeated that. If you have a current support contract with L-Soft, I'd recommend sending the list header and log file(s) for the date(s) in question to L-Soft support. Otherwise, take a look at the log file(s) yourself. Do you see the message posted to the list multiple times? Does the message appear in the list archives multiple times? And do you need the list to be Send=Public, or can you restrict the list posting process a bit more than that? -- Liam Kelly Senior Consulting Analyst L-Soft international [log in to unmask]