From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.179.196 with SMTP id br4cs14879icb; Fri, 3 Dec 2010 05:44:35 -0800 (PST) Received: by 10.224.28.70 with SMTP id l6mr1270166qac.73.1291383874782; Fri, 03 Dec 2010 05:44:34 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 12si3983031qcd.47.2010.12.03.05.44.34; Fri, 03 Dec 2010 05:44: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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 0983019783B7; Fri, 3 Dec 2010 08:44:34 -0500 (EST) Received: from mail-qy0-f178.google.com (mail-qy0-f178.google.com [209.85.216.178]) by rubyforge.org (Postfix) with ESMTP id 7EE0418581F3 for ; Fri, 3 Dec 2010 08:34:26 -0500 (EST) Received: by qyk33 with SMTP id 33so10228840qyk.2 for ; Fri, 03 Dec 2010 05:33:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:content-type:subject :from:to:in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=RLmx3/N+Ubn9vGtdWQOsOGX/3dRRRxUeZmsk3rbLogw=; b=X1HWGYUQgN48PhIqyFJmQX5oFNewt8iZCKLpijJEQLO+akFH5PbjMWoocDRaQnMtPX yHaAbgAMMA1r9dBu+n99PhzG8do89bpPDoxjg+BmStQqATsEm1tZQLk/HnjwN9aliMrN 3bX+xZDLvNUhYV+nOAonuEFHs2GKaMVwYF1xU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=jKStno9SPVZZOK/o0N0HN9gBygmmmxFiu6AjkeY+azRch+79vJWilg8T0C3ynBnI3y 0SJW+dz6tdg2uB1oO8zuXiMBtTbptD3p0bQlzPbMRAlHJXI90JA6wL6D3uhk48DNxBvV IOibFn9waMK68xD/jpOhTFbuWyMAeAglV+zho= Received: by 10.224.47.77 with SMTP id m13mr1339441qaf.5.1291383195544; Fri, 03 Dec 2010 05:33:15 -0800 (PST) Received: from localhost (c-24-128-128-14.hsd1.vt.comcast.net [24.128.128.14]) by mx.google.com with ESMTPS id t35sm1224217qco.18.2010.12.03.05.33.13 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 03 Dec 2010 05:33:13 -0800 (PST) From: Mark Alexander To: sup-talk In-reply-to: <1291336288-sup-8394@maseinet.de> References: <1291336288-sup-8394@maseinet.de> Date: Fri, 03 Dec 2010 08:33:12 -0500 Message-Id: <1291382774-sup-9612@bloovis.org> User-Agent: Sup/0.11 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 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