From: Bart Schaefer <schaefer@brasslantern.com>
To: Jason Price <jprice@cyberbuzz.gatech.edu>,
mailing list zsh-users <zsh-users@sunsite.dk>,
Nikolai Weibull <zsh-users-list@pcppopper.org>
Subject: Re: Newbie zsh setup warts (history, pipes, export, ...).
Date: Tue, 26 Oct 2004 09:27:53 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0410260902460.23496@toltec.zanshin.com> (raw)
In-Reply-To: <20041026155416.GM9745@puritan.pcp.ath.cx>
I suggest that further procmail discussion be re-routed to the procmail
list <procmail@lists.RWTH-Aachen.DE>.
On Mon, 25 Oct 2004, Jason Price wrote:
> ### PROCMAIL STUFF
>
> This works fairly well for me:
>
> :0
> * (^TO_|^Sender:[ ]+owner-)zsh
> zsh-list.spool
I think you may want ^TO rather than ^TO_ there. ^TO_ is for matching an
address, not a word. Also, the zsh lists have not set a Sender: header
for a very long time; rather, they have
Delivered-To: mailing list zsh-user@sunsite.dk
(or zsh-workers, as appropriate).
> I have no idea what PWS or Bart are/were doing with their mail to break
> that procmail recipe
Probably, sending you a personal copy, like I did with this message.
On Mon, 25 Oct 2004, s. keeling wrote:
>
> Here's what I'm using now:
>
> :0
> * 1^0 ^(TO_|Sender:[ ]+owner-)zsh
This is broken, or at least useless. The magic tokens are ^TO_ or ^TO
(all the characters have to be consecutive). You can't use TO_ or TO just
anywhere.
On Tue, 26 Oct 2004, Nikolai Weibull wrote:
> > > What are the 1^0 supposed to do?
>
> > That's "scoring" (man procmailsc).
> > It's how you build OR rules in procmail.
>
> Again, my guess, but definitely a weird way of having to do it.
You don't HAVE to do it that way. This works, too:
:0
* (^TO_|^Sender:[ ]+owner-)zsh\
|^From:.*(schaefer@brasslantern\.com\
|duvall@comfychair\.org\
|pws@csr\.com\
)\
|^(Delivered\-To|Mailing\-List|Received):.*zsh\-\
|^Newsgroups:.*comp\.shells\.zsh\
|^Posted\-To:.*zsh
Just don't forget the backslashes at the ends of lines (and they must not
have any spaces following them, before the newline).
> > All procmail recipes start with a beginning score of -1.
No, they start with a score of zero. Only rules that accumulate a score
greater than zero trigger an action.
next prev parent reply other threads:[~2004-10-26 16:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-24 23:06 s. keeling
2004-10-25 0:05 ` Clint Adams
[not found] ` <20041024232633.GB9382@lorien.comfychair.org>
2004-10-25 1:35 ` s. keeling
2004-10-25 10:19 ` Oliver Kiddle
2004-10-25 1:11 ` Bart Schaefer
2004-10-25 6:08 ` Wayne Davison
2004-10-25 16:25 ` s. keeling
2004-10-25 18:52 ` Juhapekka Tolvanen
2004-10-25 19:16 ` Jason Price
2004-10-26 3:57 ` s. keeling
2004-10-26 4:15 ` [ION Info #SZW-77636-264]: " s. keeling
2004-10-26 8:46 ` Olivier Tharan
2004-10-26 11:48 ` Nikolai Weibull
2004-10-26 15:16 ` s. keeling
2004-10-26 15:54 ` Nikolai Weibull
2004-10-26 16:27 ` Bart Schaefer [this message]
2004-10-26 17:45 ` Nikolai Weibull
2004-10-26 18:00 ` s. keeling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.61.0410260902460.23496@toltec.zanshin.com \
--to=schaefer@brasslantern.com \
--cc=jprice@cyberbuzz.gatech.edu \
--cc=zsh-users-list@pcppopper.org \
--cc=zsh-users@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).