From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.179.196 with SMTP id br4cs17348icb; Fri, 3 Dec 2010 06:45:34 -0800 (PST) Received: by 10.142.187.9 with SMTP id k9mr2016285wff.3.1291387534180; Fri, 03 Dec 2010 06:45:34 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id n10si4122417qcu.1.2010.12.03.06.45.33; Fri, 03 Dec 2010 06:45:34 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id B5614167831B; Fri, 3 Dec 2010 09:45:33 -0500 (EST) Received: from maseinet.de (unknown [213.165.84.77]) by rubyforge.org (Postfix) with ESMTP id 7EF0618581F3 for ; Fri, 3 Dec 2010 09:16:19 -0500 (EST) Received: by maseinet.de (Postfix, from userid 1000) id 7A2FC60004; Fri, 3 Dec 2010 15:16:16 +0100 (CET) From: Marc Seibert To: sup-talk In-reply-to: <1291382774-sup-9612@bloovis.org> References: <1291336288-sup-8394@maseinet.de> <1291382774-sup-9612@bloovis.org> Date: Fri, 03 Dec 2010 15:16:16 +0100 Message-Id: <1291385110-sup-7331@maseinet.de> User-Agent: Sup/git Subject: Re: [sup-talk] run sup (or sup-sync) as daemon Hello everybody, X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.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