From owner-freebsd-questions@FreeBSD.ORG Sun Sep 5 16:33:38 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BD5110656DB for ; Sun, 5 Sep 2010 16:33:38 +0000 (UTC) (envelope-from drew@mykitchentable.net) Received: from smtp1.mc.surewest.net (qsmtp.mc.surewest.net [66.60.130.145]) by mx1.freebsd.org (Postfix) with SMTP id 721AD8FC0C for ; Sun, 5 Sep 2010 16:33:38 +0000 (UTC) Received: (qmail 24825 invoked from network); 5 Sep 2010 09:28:44 -0700 Received: by simscan 1.1.0 ppid: 24820, pid: 24821, t: 0.2829s scanners: regex: 1.1.0 attach: 1.1.0 spam: 3.1.7-deb X-Spam-Checker-Version: SpamAssassin 3.1.7-deb (2006-10-05) on smtp1.surewest.net X-Spam-Level: * X-Spam-Status: No, score=1.8 required=13.5 tests=RATWARE_GECKO_BUILD autolearn=disabled version=3.1.7-deb X-Spam-CMAE-Analysis: _CMAETAG_ Received: from unknown (HELO blacklamb.mykitchentable.net) (69.62.230.77) by smtp1 with SMTP; 5 Sep 2010 09:28:43 -0700 Received: from [127.0.0.1] (bigdaddy.mykitchentable.net [192.168.1.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by blacklamb.mykitchentable.net (Postfix) with ESMTPS id 17D23165BCA; Sun, 5 Sep 2010 09:33:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mykitchentable.net; s=default; t=1283704416; bh=OBOVGeaM3LM+1Oxwrho3jSuMNa1xyvIv46QF+dXg184=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=icQemvEExrnOigUPwAoxmSRlruvzZm+39h5Bd9t9ZmSYWri9J2CFUKPa4u3zIV1CM RrXLfu/hldX89bHM8N7oPCKE4ZfidkZBi624dFOCySsmap+UTTkz7dZjEZQjLs3sUj DUot2wFUWwp3WQxhywsamIAeNTK9/h0edMI3QBWQ= Message-ID: <4C83C65B.6060508@mykitchentable.net> Date: Sun, 05 Sep 2010 09:33:31 -0700 From: Drew Tomlinson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: Glen Barber References: <4C814262.5060504@mykitchentable.net> <4C814634.1000003@gmail.com> <4C8164C7.9000107@mykitchentable.net> In-Reply-To: <4C8164C7.9000107@mykitchentable.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 100905-0, 09/05/2010), Outbound message X-Antivirus-Status: Clean Cc: freebsd-questions@freebsd.org Subject: Re: Regex Help For Procmail X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Sep 2010 16:33:38 -0000 On 9/3/2010 2:12 PM, Drew Tomlinson wrote: > Hi Glen, > > Thank you for your reply. > > On 9/3/2010 12:02 PM, Glen Barber wrote: >> Hi Drew, >> >> On 9/3/10 2:45 PM, Drew Tomlinson wrote: >>> I use procmail for mail delivery and I'm trying to concoct the right >>> regex to match From: headers and deliver to a folder. However mail is >>> sent from various addresses so I want to match all that end with >>> "famous-smoke.com>". Here's an example of a header: >>> >>> From: "Famous Smoke Shop" >>> >>> Because I also occasionally order, I don't want to catch mail from >>> anything that has the word "Orders" and "Famous" in the From field. >>> Thus here is my procmail recipe: >>> >>> # Deliver order info to inbox >>> :0 >>> *^From:.[Ff]amous.*[Oo]rder.*famous-smoke.com>$ >>> "${HOME}/Maildir/new/" >>> >> Is this supposed to be "match Famous OR Order"? This currently matches >> "Famous AND Order". > > No, I want "Famous AND Order". > >>> # Deliver other email to folder >>> :0 >>> *^From:.*famous-smoke.com>$ >>> "${HOME}/Maildir/.Shopping/Famous Smoke/Email/" >> Going by your examples, you want to catch "Famous OR Order" and place >> that in Maildir/new, and all other email from this address to go to >> Maildir/.Shopping/... >> >> Try this: >> >> # catch "famous" or "order" >> :0 >> * ^From:.*([Ff]amous|[Oo]rder).*famous-smoke.com>$ >> "$HOME/Maildir/new" >> >> # catch everything else from this sender >> :0 >> * ^From:.*famous-smoke.com>$ >> "$HOME/Maildir/.Shopping/Famous Smoke/Email/" >>> According to my procmail log, the From: header does not match. I would >>> expect the example From: header above to match the second regex and be >>> delivered to the specified folder. Where is my error? >> If my assumption above is incorrect, could you paste a snippet from your >> procmail log and point out what should be matching so we can have a >> specific example? > > This is the actual log entry from the example I used in this email: > > From Announce@email.famous-smoke.com Fri Sep 3 10:11:08 2010 > Subject: Another Must-Attend Event at Famous! > Folder: /home//Maildir/new/1283533874.95147_0.blacklamb. > 8161 > procmail: [95164] Fri Sep 3 10:13:05 2010 > procmail: Assigning "NL= > " > procmail: Assigning "LOG= > /home//Procmail/famous_smoke.rc" > > /home//Procmail/famous_smoke.rc > procmail: No match on "^From:.[Ff]amous.*[Oo]rder.*famous-smoke.com>$" > procmail: No match on "^From:.*famous-smoke.com>$" > procmail: Assigning "VERBOSE=OFF" > > > I think my problem is that I was missing a "space" between "*" and > "^From:". Your example shows a space and a reply from Brent Bloxam > suggests this is the problem as well. I don't quite understand the > difference between the two but have made the change and I'll see if it > works. I'm also going to hit Google and see if I can understand. No, still not matching. Basically, why doesn't this header: From: "Famous Smoke Shop" Match this procmail recipe: :0 * ^From:.*famous-smoke.com>$ "${HOME}/Maildir/.Shopping/Famous Smoke/Email/" From my procmail log: procmail: No match on "^From:.*famous-smoke.com>$" Thanks, Drew -- Like card tricks? Visit The Alchemist's Warehouse to learn card magic secrets for free! http://alchemistswarehouse.com