Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [ANN] Sup 0.1 released
Date: Thu, 19 Jul 2007 13:49:28 -0700	[thread overview]
Message-ID: <1184878159-sup-2212@south> (raw)

Excerpts from William Morgan's message of Thu Jul 19 13:29:30 -0700 2007:
> I realize that's not ideal (in particular, users whose mail is delivered
> to IMAP servers not under their control are left out in the cold), but I
> really really don't want to write a slow, buggy, Ruby procmail clone as
> part of Sup.
> 
> Is there another option? I would really like the full power of procmail.

There is a way of tricking procmail into doing what I want. Sup could
take in a list of procmail rules and corresponding label assignments,
create a procmail configuration file that makes procmail act as a filter
that adds an X-Sup-Labels header with the corresponding labels, run all
new messages through procmail with that config file at poll time, and
then parse that header to determine the labels.

Pretty painful. But then you can just write some procmail rules for the
labels you want, and it doesn't matter what source the messages come
from (as long as you have procmail locally!).

-- 
William <wmorgan-sup at masanjin.net>


             reply	other threads:[~2007-07-19 20:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 20:49 William Morgan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-07-19 18:58 Eugen Minciu
2007-07-19 20:29 ` William Morgan
2007-08-19  0:12   ` William Morgan
2007-07-18  1:42 William Morgan
2007-07-18 22:21 ` jeff covey
2007-07-19 18:01   ` William Morgan
2007-07-19 18:18     ` nicholas a. evans
2007-07-19 18:55       ` William Morgan
2007-08-01 16:15       ` William Morgan

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=1184878159-sup-2212@south \
    --to=wmorgan-sup@masanjin.net \
    /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