List:MySQL++« Previous MessageNext Message »
From:Earl Miles Date:July 21 2005 2:55pm
Subject:Re: reply-to discussion
View as plain text  
Chris Frey wrote:
> When I come across broken mailing list configurations, such as mysql++'s ;-)  
> I use the following procmail recipe, and everyone's happy. (Or at least I am)
> 
> ####### mysql++
> :0
> * List-ID:.*plusplus.mysql.com
> {
>         # filter the Reply-To: line so it goes to the list, not the sender
>         :0hfW
>         | formail -Ybi "Reply-To: plusplus@stripped"
> 
>         # send to proper mailbox
>         :0
>         plusplus
> }

Oh! That's absolutely excellent! I'd never thought about having procmail 
actually do that for me, even tho I use it extensively for a few other things.

Thanks for the recipe!
Thread
Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =>__int64 followed by 'long'is illegal ???np18 Jul
  • Re: Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =>__int64 followedby 'long'is illegal ???Warren Young18 Jul
    • Re: Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =>__int64 followedby 'long'is illegal ???Earl Miles18 Jul
      • Re: Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =>__int64 followedby 'long'is illegal ???Warren Young18 Jul
        • Re: Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =>__int64 followedby 'long'is illegal ???Warren Young18 Jul
        • Re: Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =>__int64 followedby 'long'is illegal ???Earl Miles18 Jul
          • Re: Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =>__int64 followedby 'long'is illegal ???Warren Young18 Jul
            • Re: Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =>__int64 followedby 'long'is illegal ???Earl Miles18 Jul
              • Re: reply-to discussionChris Frey21 Jul
                • Re: reply-to discussionEarl Miles21 Jul