Re: procmail rules

[debian@clouded.org]

Yes, normally I wouldn't be searching the entire email, but this account
receives several requests each day with email address change requests from
the average uesr who only knows to type "Hello, I've moved and switched
ISPs so could you please change my email address to blah blah", etc.

So, I need to match on the following:

change .. e-?mail or address
update .. e-?mail or address
new .. e-?mail or address
different .. e-?mail or address

I know it's best to match only on subject lines but this account receives
so many emails with random subjects and different email bodies that this
is really all I can do. In fact, after this is fixed, I'll be reversing
the order and looking for the following, too:

e-?mail or address .. change

etc.. These recipes are actually enclosed in:

:0
* ^TO_changerequest|^Received:.*for changerequest
{
  ..
}

With verbose logging enabled, I can see it matching on the TO field and
passing right over my 'change email' recipes without matching. :(


On Fri, 15 Feb 2002, Cameron Kerr wrote:

> On Thu, 14 Feb 2002 debian@clouded.org wrote:
>
> >This isn't working for me:  (from /etc/procmailrc)
> >
>
> To be quite frank, your recipes are very non-specific, it would be easy to
> get a false positive, as you search the entire email, without retricting
> it to a certain header or jus the body. Also, you have not told us exactly
> what you are trying to accomplish, which means I have to guess
>
> >        :0:
> >        * (change|update|new|different).*(e-?mail|address)
> >        /var/mail/addresschanged
>
> What are the intended semantics for this rule??? What are you trying to
> accomplish?