Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Oct 2005 02:28:14 +0300
From:      Giorgos Keramidas <keramida@ceid.upatras.gr>
To:        freebsd-questions@freebsd.org
Subject:   Re: procmail/formail syntax question
Message-ID:  <20051023232814.GB1753@flame.pc>
In-Reply-To: <20051023225648.GB31109@teddy.fas.com>
References:  <20051023190951.GA25702@teddy.fas.com> <20051023200717.GB82057@slackbox.xs4all.nl> <20051023214939.GB30009@teddy.fas.com> <20051023221317.GA1211@flame.pc> <20051023225648.GB31109@teddy.fas.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-10-23 18:56, stan <stanb@panix.com> wrote:
>On Mon, Oct 24, 2005 at 01:13:18AM +0300, Giorgos Keramidas wrote:
>>On 2005-10-23 17:49, stan <stanb@panix.com> wrote:
>>>On Sun, Oct 23, 2005 at 10:07:17PM +0200, Roland Smith wrote:
>>>>On Sun, Oct 23, 2005 at 03:09:51PM -0400, stan wrote:
>>>>> I'm trying to get procmail to rewrite the TO: header. I've tried something like:
>>>>>
>>>>> TO=`formail -xTo:`
>>>>
>>>> [...]
>>>
>>> So, I need to be able to rewrite the subject. Yes it's dumb but....
>> 
>> 	``Much confusion in you I sense, young Jedi.''
>> 
>> If you want to rewrite the *SUBJECT* of the messages, then why are you
>> trying to rewrite the *RECIPIENT* header?
>> 
>> Having said that, I think that what you're missing is the 'f' option in
>> the rule that pipes mail to formail and that you don't really need
>> formail for something as simple:
>> 
>> 	:0 Hf
>> 	* X-Virus-Status: Yes
>> 	| sed -e 's/^[sS]ubject:[[:space:]]\+/Subject: [virus] '
>
> Yes, Oh freat master, I sense a great confusion :-) 
> It's the To: header he wants rewriten.

You can always hit the Windows user hard on the head with a cluebat.
All the mail reading software for Windows that I've recently had to work
with supports filtering by the _SUBJETC_ of the messages too :-)




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051023232814.GB1753>