>I just read this FAQ, and I still don't see a good reason why not to >change the REPLY-TO. The primary reason offered is that it will prevent >people from sending messages in private, but that is not really the case >(the FROM field will still contain the sender's address and it can simply >be cut & paste). I just don't see anything "evil."
Nothing evil, it's just a pain in the ass to have to cut and paste to send a private mail, vs. the significantly lower PITA-level associated with hitting 'reply-all' to send a public one. For those of use who use nice context-sensitive mailers like Pine or Mutt, the default reply behavior to a list is reply-all, anyway. >I am with Doug -- it is better to have something set up to where people >don't have to think about performing the normal operation, Also, not munging the reply-to tends to cut down on the "oops, that scathing flame / innappropriate proposition / disclosure of company secrets was not meant to go to the list" factor. --------------------------------------------------------------------- michal migurski- contact info and pgp key: sf/ca http://mike.teczno.com/contact.html -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
