public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Steve [Gentoo]" <gentoo_steve@shic.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: procmail, formail and maildir for digests...
Date: Thu, 12 Oct 2006 11:07:53 +0100	[thread overview]
Message-ID: <452E13F9.6030305@shic.co.uk> (raw)
In-Reply-To: <20061011161240.GA26527@smtp.mth.uea.ac.uk>

Moshe Kamensky wrote:
> The -s option of formail allows you to specify an argument, which is a 
> program name. This program will be run for each message, with the 
> message on the stdin. So if you have such a program that delivers to a 
> maildir, you can use it. procmail itself is one such program, so you 
> should be able to do something like
>
> | formail +1 -ds procmail .procmailrc.gentoo
>
> and then have .procmailrc.gentoo say something like
>
> :0
> gentoo-user/
>   
That works perfectly... Thanks!

I'd overlooked that -s had an optional argument with formail - and while
I'd realised I probably wanted procmail to deliver messages, I hadn't
realised that I could have separate configurations as easily as that.

I'm surprised this example is neither one of the convenient examples in
the man procmailex man page... nor widely cited in the online howtos
I've seen.





-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2006-10-12 10:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 11:09 [gentoo-user] procmail, formail and maildir for digests Steve [Gentoo]
2006-10-10 11:29 ` Kevin Fullerton
2006-10-11 10:32   ` Steve [Gentoo]
2006-10-11 10:40     ` Rasmus Andersen
2006-10-11 14:07       ` Steve [Gentoo]
2006-10-11 12:17     ` [gentoo-user] " reader
2006-10-11 13:38     ` Re: [gentoo-user] " Michael Sullivan
2006-10-11 16:12 ` [gentoo-user] " Moshe Kamensky
2006-10-12 10:07   ` Steve [Gentoo] [this message]

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=452E13F9.6030305@shic.co.uk \
    --to=gentoo_steve@shic.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox