On Thu, 16 Aug 2001, Philip Guenther wrote:
# Extract the first Received: header field and then look for
# a "for" clause in it.
:0 w
* ^Received:\/.*
* MATCH ?? [ ]for[ ]+\/<[^>]+>
! $MATCH
:0:
hard-cases
# DON'T USE THIS!!!
:0 w
* ^Received:.*[ ]for[ ]+\/<[^>]+>
! $MATCH
Thanks for the help, I never thought of using formail that way :-)
But it looks like neither rule catches anything. They all fall through to
hard-cases, when i use 'formail -Y -s procmail testrc <mail-to-be-delivered'
A header looks like
From sistersa(_at_)xxxxxx(_dot_)net Tue Aug 14 20:17:57 2001
Return-Path: <sistersa(_at_)xxxxxx(_dot_)net>
Received: from mail-02.xxxxxx.net (mail-02.xxxxxx.net [x3.x6x.6x.5x])
by yyyyyyyy.com (8.9.3/8.9.3) with SMTP id UAA12747
for <humbug(_at_)zzzzzz(_dot_)net>; Tue, 14 Aug 2001 20:17:56 -0700
What am I missing?
-Dan
--
[-] Omae no subete no kichi wa ore no mono da. [-]
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail