* [sup-talk] run sup (or sup-sync) as daemon Hello everybody,
@ 2010-12-03 0:41 Marc Seibert
2010-12-03 5:52 ` Tero Tilus
2010-12-03 13:33 ` Mark Alexander
0 siblings, 2 replies; 4+ messages in thread
From: Marc Seibert @ 2010-12-03 0:41 UTC (permalink / raw)
To: sup-talk
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
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] run sup (or sup-sync) as daemon Hello everybody,
2010-12-03 0:41 [sup-talk] run sup (or sup-sync) as daemon Hello everybody, Marc Seibert
@ 2010-12-03 5:52 ` Tero Tilus
2010-12-03 13:33 ` Mark Alexander
1 sibling, 0 replies; 4+ messages in thread
From: Tero Tilus @ 2010-12-03 5:52 UTC (permalink / raw)
To: sup-talk
Marc Seibert, 2010-12-03 02:41:
> So I wonder if its a good idea to remove my procmail rules and
> 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
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] run sup (or sup-sync) as daemon Hello everybody,
2010-12-03 0:41 [sup-talk] run sup (or sup-sync) as daemon Hello everybody, Marc Seibert
2010-12-03 5:52 ` Tero Tilus
@ 2010-12-03 13:33 ` Mark Alexander
2010-12-03 14:16 ` Marc Seibert
1 sibling, 1 reply; 4+ messages in thread
From: Mark Alexander @ 2010-12-03 13:33 UTC (permalink / raw)
To: sup-talk
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
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] run sup (or sup-sync) as daemon Hello everybody,
2010-12-03 13:33 ` Mark Alexander
@ 2010-12-03 14:16 ` Marc Seibert
0 siblings, 0 replies; 4+ messages in thread
From: Marc Seibert @ 2010-12-03 14:16 UTC (permalink / raw)
To: sup-talk
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-12-03 14:45 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-12-03 0:41 [sup-talk] run sup (or sup-sync) as daemon Hello everybody, Marc Seibert
2010-12-03 5:52 ` Tero Tilus
2010-12-03 13:33 ` Mark Alexander
2010-12-03 14:16 ` Marc Seibert
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox