Headers on this echo...

[Todd Zullinger]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Laurent,

Laurent Jumet wrote:
> Why the Headers on this echo are not correct?

You'll have to provide some proof that they are incorrect.  What
defines "correct" headers?  :)

>     Messages come with this
> 
> Sender: gnupg-users-bounces at gnupg.org
> 
>     and it should be of course "gnupg-users at gnupg.org"

This is the way Mailman sends mail.  Sender is set to use
$listname-bounces@$domain because there are broken MTA's that will
send bounces back to Sender, rather than to the address in the
Errors-To or Return-Path headers.

This may be changed in a future version of mailman, as the number of
broken MTA's is diminishing and the number of MUA's that display
things like "on behalf of" when the Sender header differs from the
- From header is increasing.

See this recent thread on the mailman-users list for more discussion
and links to relevant RFC's:

    http://www.mail-archive.com/mailman-users@python.org/msg38403.html

> And there is no "Reply-To: gnupg-users at gnupg.org" Header.

See Mailman FAQ 3.48. 'What about setting a "Reply-To:" header for the
list?' for discussion of why many lists do not add a reply-to header
and why the Mailman default is to not set this to the list address.

    http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.048.htp

Your MUA should be able to handle this.  Mutt does quite well without
the reply-to header pointing to the list.  Submit a feature request to
the developers of your MUA if it's missing a list reply function.

- -- 
Todd        OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp
======================================================================
It was probably drugs more than anything else that made me a
Libertarian.
    -- John Gilmore

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.

iG0EARECAC0FAkR/6nAmGGh0dHA6Ly93d3cucG9ib3guY29tL350bXovcGdwL3Rt
ei5hc2MACgkQuv+09NZUB1pfnwCfU0nD1m//OvPGGpHsHyqpHkTs0zAAn3eAPj9h
CUdFAqF5vKLlwCQc6Bze
=98UM
-----END PGP SIGNATURE-----