On 2002-03-11 23:28:36, Rasmus Lerdorf wrote:
> It seems to work quite nicely for most. Having the mailing list software
> remove a user's ability to control where replies go is even nastier. Add
Yes, in general I'm against adding forced Reply-To headers by mailing
list software, too (having re
It seems to work quite nicely for most. Having the mailing list software
remove a user's ability to control where replies go is even nastier. Add
to that thet danger of mail loops from badly configured servers. We have
gone over this a bunch of times. Yes, it makes users perhaps think just a
f
Rasmus Lerdorf wrote:
> Please don't start this again. There is no technically valid reason to
> destroy mail headers on mailing lists, especially lists geared at
> supposedly technically adept users.
Sure, but having dicussions on both php-cvs@ and php-dev@ is nasty,
IMHO.
--
Sebastian
nly go a long
> way.
>
> James
>
> > -Original Message-
> > From: Sebastian Bergmann [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, March 12, 2002 6:04 AM
> > To: [EMAIL PROTECTED]
> > Subject: [PHP-DEV] Make php-cvs@ read-only
> >
> >
>
we can set the reply-to to be php-dev@ ... that would certainly go a long
way.
James
> -Original Message-
> From: Sebastian Bergmann [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 12, 2002 6:04 AM
> To: [EMAIL PROTECTED]
> Subject: [PHP-DEV] Make php-cvs@ read-o
'lo,
could we make the [EMAIL PROTECTED] 'read-only', ie. only the CVS
script may write to it?
Maybe mails sent to [EMAIL PROTECTED] could be forwarded to the
[EMAIL PROTECTED] list.
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
