Subject: Re: [sup-talk] run sup (or sup-sync) as daemon Hello everybody,

From: Mark Alexander <[email-masked]>
Date: Fri, 03 Dec 2010 08:33:12 -0500

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.
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Marc Seibert <[email-masked]>
Date: Fri, 03 Dec 2010 01:41:22 +0100

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.
There is no daemon mode built in - if I got it right - so I want to write a cron job to sup-sync every ten minutes.
For this I have to write a script, that checks if there is a sup lock or not.
I just want too know, if there is a better solution.

Regards
Marc

---

From: Marc Seibert <[email-masked]>
Date: Fri, 03 Dec 2010 15:16:16 +0100

> 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
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Tero Tilus <[email-masked]>
Date: Fri, 03 Dec 2010 07:52:24 +0200

> manage the whole thing in ruby over sup.

I did exactly that.  Hooks (especially before-add-message) are your
best friends.

> There is no daemon mode built in - if I got it right - so I want to
> write a cron job to sup-sync every ten minutes.

Why would you want to do that?  When sup is running, it polls
periodically for new mail.  When its not, why would you care?

You can think of sup-sync as parameterized way of doing what sup
itself does when it polls for new mail (only from sources that are
marked "usua", i.e. they are expected to receive new mail) and does
indexing.  Sup-sync comes handy when you start with sup and want to
index all the sources or want to restore a dump.  Other than that, sup
maintains index by itself by polling on start and periodically after
that.

--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk