[Mailman-Users] Return-Path Problem

[Dan Mick]

> From: Eric Wang <MRlist at ActiveState.com>
> To: mailman-users at python.org
> X-Filtered-By: PerlMx makes it fast and easy.  See 
http://www.ActiveState.com/Products/PerlMx/Header
> Subject: [Mailman-Users] Return-Path Problem
> X-BeenThere: mailman-users at python.org
> X-Mailman-Version: 2.0.1 (101270)
> List-Post: <mailto:mailman-users at python.org>
> List-Id: Mailman mailing list management users <mailman-users.python.org>
> List-Archive: <http://www.python.org/pipermail/mailman-users/>
> Date: Wed, 10 Jan 2001 18:25:26 -0800
> 
> Let's see we have mail list ABC at list.foo.com
> 
> people normally post message to ABC at foo.com, after mailman delivered the
> message to subscribers,mailman will organize the mail header become like
> this:
> 	Return-Path: <ABC-admin at list.foo.com>
> 	.
> 	.
> 	.
> 	From:XXX at XXX.com
> 	To:ABC at list.foo.com
> 
> so , when some stupid mail client program reply such a email message,
> then ABC-admin at list.foo.com was taken as reply email address instead of
> ABC at list.foo.com.
> 
> My question is can we change the way mailman to organize message
> somehow, then the email address ABC-admin won't get the email it should
> not get?

1) I'm almost certain Mailman doesn't set it; the MTAs somewhere along
the path are.  return-path doesn't appear in the mailman code in
any capitalization (except one comment).

2) read http://cr.yp.to/immhf/envelope.html; according to djb, it
*must* be set to ABC-admin; any other setting would be wrong.

3) order of headers can't matter to an email client; any such client
is *horribly* broken.

What email client are we talking about?