>On 19 Dec 00, at 17:11, Ben Parker <[log in to unmask]> wrote:
 ...
> LISTSERV lists used in such closed corporate environments may be able to
retain
> these proprietary mail program features, but only with special
configurations.

This is our environment (standalone LISTSERV running on an intranet
with 80% of the people using MS Exchange).   How do I find out about
these "special configurations" so that I can get the return-receipts
going back to the originators?


On Wed, 20 Dec 2000 19:00:04 -0500, Francoise Becker <[log in to unmask]>
wrote:

>On 19 Dec 00, at 17:11, Ben Parker <[log in to unmask]> wrote:
 ...
>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.

Yep, that's what I meant.

>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.

Yes, it seems that an Exchange return-receipt is a "bounce it
can't interpret"  (most of our lists have the default Auto-Delete
setting):

> The enclosed message has been identified as a delivery error for the
> xyz-l list because it was sent to [log in to unmask]

The question I still have is what is Exchange doing?  Does it get
confused that the WINMAIL.DAT is missing, and use the envelope
sender instead of Return-Receipt-To: which should still be there?
Or does it think Return-Receipt-To: should match the envelope
sender and opt for the wrong one?

Anyways, if there's something that can be done from the LISTSERV
side to work around this strangeness, let me know!

Thanks for setting me straight on a number of things,
Eva