-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 jdow wrote: > That seems to be the ticket. Usually a Reply-To: address would be > used when you want a reply sent to a different address than the > "To:" line. For some people that's a handy tool. For this list it > seems to get in the way. That depends on your goals. Knowing the list behaves this way, someone who wants to be Cc'd on their posts will have a greater likelihood of that happening when most people just hit reply. (I'm not that sort of someone, one copy is just fine for me. :) > I was thinking in terms of a misconfiguration at Aaron's site. Ahh, I see. > It MAY be that his MUA is too smart for it's own good. I use <choke > puke>Outlook Express</choke> typically. It doesn't toss on the > Reply-To:. Both Evolution and OE and most other mailers will add the reply-to if you specify it in the account configuration, none that I've toyed with add it automatically. But I'm sure there are at least a few that will do something silly like this to their users. > It also does not reduce a dual "Reply-To:" down to one. That's a good thing. It shouldn't. I can't point at the proper RFC's, but I know that in some of the posts and debates about the default for this setting that I've read on the mailman-users list over the years it's been mentioned. > Regardless something screwy's going on. Really? I think all is well here. The list is merely adding its own address to the Reply-To, which is a decent compromise between not touching the reply-to and overwriting it completely. And it seems many of the mail clients in use here will honor that header and send mail to all the addresses in the reply-to. - -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp ====================================================================== It is OK to let your mind go blank, but please turn off the sound. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iG0EARECAC0FAkSh42gmGGh0dHA6Ly93d3cucG9ib3guY29tL350bXovcGdwL3Rt ei5hc2MACgkQuv+09NZUB1rTYACeIUntC+ymh/w/79b4nLO595MskCQAn0h7DjYT RPCTlpN7fLKKRmaRJL+H =Mj0I -----END PGP SIGNATURE-----
