From: Marc Seibert <sup@maseinet.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] run sup (or sup-sync) as daemon Hello everybody,
Date: Fri, 03 Dec 2010 15:16:16 +0100 [thread overview]
Message-ID: <1291385110-sup-7331@maseinet.de> (raw)
In-Reply-To: <1291382774-sup-9612@bloovis.org>
Excerpts from Mark Alexander's message of Fr Dez 03 14:33:12 +0100 2010:
> Excerpts from Marc Seibert's message of Thu Dec 02 19:41:22 -0500 2010:
> > I am very new in using sup - and I am glad to find this nice tool for my console :-)
> > So I wonder if its a good idea to remove my procmail rules and manage the whole thing in ruby over sup.
>
> You can keep using procmail; I had been using that long before I
> started using sup, along with fetchmail. My filters would put messages
> in various directories based on From lines and so forth, and I just
> made each of those directories a separate source in sup. Now I'm
> using maildrop instead of procmail but the overall idea is the same.
>
> I also used to have fechmail running as a daemon, but at one point
> over a year ago, while debugging some maildir problems in sup, I
> switched to having sup initiate the polling by writing a before-poll
> hook that invoked fetchmail. That has been working well.
Yes, thanks alot.
I think I wil keep using procmail for the base filtering.
Ruby Filters would be fine, but procmail still works :-)
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-12-03 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 0:41 Marc Seibert
2010-12-03 5:52 ` Tero Tilus
2010-12-03 13:33 ` Mark Alexander
2010-12-03 14:16 ` Marc Seibert [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=1291385110-sup-7331@maseinet.de \
--to=sup@maseinet.de \
--cc=sup-talk@rubyforge.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