On Tuesday 21 February 2006 17:37, Andrew Johnson wrote:
> Hi Ben,
>
> Please reply to core-talk messages on core-talk itself; see
> http://www.producingoss.com/html-chunk/setting-tone.html#avoid-privat
>e-discussions for reasons (that book is a good resource for Open
> Source projects BTW, with many ideas which I'm trying to introduce to
> the EPICS community).
Hi Andrew,
I am as opposed to 'privat e-discussions' as you ;)
I replied to you and Jeff personally because there was nothing in the
mail I received indicating that it came from core-talk. Apart from
'Received:' fields the only field that mentions core-talk is
X-Original-To: EPICS core-talk <[email protected]>
I have been using a procmail filter rule for core-talk and tech-talk
like the following one for years and it has always worked perfectly.
:0:
* ^[email protected]
| ${FORMAIL} -I"Reply-To: [email protected]" >>${CORETALK}
However, it doesn't work any more; '^TO_' doesn't recognize
'X-Original-To'.
Disruptions like these could be avoided by automatically setting
'reply-to' field messages sent from tech-talk and core-talk.
Some list mailers also use 'ListId:' field.
Ben
- Replies:
- Re: 3.15 C++ Exception classes Andrew Johnson
- Navigate by Date:
- Prev:
Re: 3.15 C++ Exception classes Andrew Johnson
- Next:
Fwd: Re: 3.15 C++ Exception classes Benjamin Franksen
- Index:
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Fwd: 3.15 C++ Exception classes Kay-Uwe Kasemir
- Next:
Re: 3.15 C++ Exception classes Andrew Johnson
- Index:
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|