Erm, I believe you're mistaken. When our LISTSERV (1.8c NT) receives such a mesage, it has *not* sent the message to the list, because it believes that might create a loop. I send a reply to the poster reminding them that they must either remove or mask the Sender: line cc:Mail puts on the reply. LISTSERV's reaction to seeing itself as a source (Sender:) on a message is to refuse to send it farther, as this looks like a potential loop. Preceding the troublesome line with > or some other character will identify it for LISTSERV as something other than an 'active' header, and avoid tripping loop detection. FWIW, our main mail system is cc:Mail, which exhibits this behavior (copying headers into the bodies of replies without quoting). Chris Pepper At 8:12 AM -0400 04/23/98, KEVIN MCKENZIE wrote: >The error you are getting is that when a person responds to a listserv >posting and their email client is set to automatically show all the headers >in the reply. I get it quite frequently. Handling hundreds of lists at my >site there are still people who choose to have different email clients with >different preferences to handle their mail. It is really nothing to worry >about. The listserv sees the tags in the message and thinks that it could >be an error. It still sends the message and bounces an error to you as the >owner or maintainer. > > > > > >At 08:00 PM 4/22/98 -0400, you wrote: >>Has any one had this problem before? I'm running 1.8c. >>Any help will be appreciated... >> >>Al >> >> >> >>The enclosed message, found in the AMEX mailbox and shown under the spool >>ID >>0018 in the system log, has been identified as a possible delivery error >>notice >>for the following reason: "Sender:", "From:" or "Reply-To:" field pointing >>to >>the list has been found in mail body. >> >> -- Chris Pepper | National Audubon Society: Web & List Manager 212 979 3092 | <http://www.audubon.org/staff/pepper/>