-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 jdow wrote: > I'm feeling slow today. You're lucky if you don't feel slow everyday. :) > I can't see how the way the headers are applied Aaron would find > sending emails with a "reply" to you would cause a problem. A simple > reply should end up with the email going to the list, pretty much as > it should. If there are multiple addresses in the Reply-to header, then a reply will go to all of them, at least in many mail clients. That's correct and intended behavior, though it probably surprises a lot of folks because there are more lists (in my experience) that either replace the Reply-to header or leave it alone. Here's a quote from Aaron's original mail outlining the issue, which will hopefully clarify what his initial concern was that started this tangent. On Mon, 2006-06-26 at 15:28 -0500, Aaron Konstam wrote: I might as well get this off my chest there is one member of this list that sends me responses to my list messages at my actual address as the primary address but does not allow his e-mail address to accept mail. The issue arose because of the way the list adds its own address to the reply-to without stripping Aaron's existing reply-to header. So when Tim would reply to messages that Aaron sent, the reply would go to both Aaron and the list. I think that is all there is to it. The many variables of what someone else's mail client may or may not do for (or to) them isn't of much concern to me, so long as whatever it does isn't egregiously violating net standards or common courtesy (neither of which happened here, IMO). Have I missed a part of this that you're still interested in figuring out? - -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp ====================================================================== There are two kinds of light - the glow that illuminates, and the glare that obscures. -- James Thurber -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iG0EARECAC0FAkSh/AMmGGh0dHA6Ly93d3cucG9ib3guY29tL350bXovcGdwL3Rt ei5hc2MACgkQuv+09NZUB1odPACdHYpvmYXQqxqhXTPE3cd03zYLplwAoOxK3P/1 72pv23imo/fes1MqmaI1 =2Vw0 -----END PGP SIGNATURE-----