On 19 Dec 00, at 17:11, Ben Parker <[log in to unmask]> wrote: > On Tue, 19 Dec 2000 15:31:26 -0500, Eva Kalman <[log in to unmask]> wrote: <snip> > > Listserv sets the envelope sender to the "Errors-To" address, because > > that's where errors will usually go, and in most lists, this is set to > > owner-<I>listname</I> by default. > > LISTSERV reserves the OWNER-listname@hostname address for this purpose and > always has. This not the same as any Errors-To: header (which is an RFC822 > header whose use is defined as "Non-Standard, Discouraged" by RFC2076.) > LISTSERV does not set the MAIL FROM:<address> to the same as Errors-To: at all. > The Errors-To: will be ignored by LISTSERV, but the MAIL FROM:<address> will be > set correctly. The Errors-To: header, if present, may happen to be point to the > same address but if so it is not set that way by LISTSERV. Actually Ben, I suspect that Eva was referring to the address specified in the list header "Errors-To=" keyword rather than the non- standard mail header "Errors-To:". Either way it's incorrect, though. The Errors-To= list header keyword defaults, as Ben indicated, to the non-quiet listowners. It does not default to owner-listname, nor is it used as the "envelope" sender. The owner-listname address is *always* used as the "envelope" sender, regardless of what you set Errors-To= to. When LISTSERV receives an email at the owner-listname address, it knows to interpret it as a bounce. What it does with it as a result depends on what the Auto-Delete= keyword is set to. If Auto-Delete=No, then LISTSERV will indeed forward the message to the address(es) specified in Errors-To=. Otherwise, it sends a daily error monitoring report to the Errors-To= address(es) and may also forward bounces that it can't interpret, depending on the other parameters specified for Auto-Delete=. I hope that helps. Francoise