From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.59.13 with SMTP id h13cs123500fga; Sat, 20 Feb 2010 13:12:21 -0800 (PST) Received: by 10.224.36.147 with SMTP id t19mr21199qad.201.1266700340881; Sat, 20 Feb 2010 13:12:20 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 6si4183078qwk.0.2010.02.20.13.12.20; Sat, 20 Feb 2010 13:12:20 -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 643FF1588076; Sat, 20 Feb 2010 16:12:20 -0500 (EST) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by rubyforge.org (Postfix) with ESMTP id 2BB68158806E for ; Sat, 20 Feb 2010 16:10:20 -0500 (EST) Received: by qw-out-2122.google.com with SMTP id 8so194751qwh.29 for ; Sat, 20 Feb 2010 13:10:20 -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=Nlh+0z6czy7ZDi36yTZOkT3Fxv/ex2po+uobEa2fJhA=; b=EzfOUo5iiK3hnDSmkexEIN+4B3afsid9QSGWy9Z1zy31LKbZUq0m73ENdfG6/BZ6O9 wR73sBwbV48o7RVvGHsa1kCQAckEdaA50W0oqts/RRcHfdibr67i5gkL2OXdrijI5Jdp V81jZEMGidgWvjS6DE1Md2l4rQr3GRYHKYROw= 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=siFBVYBkQo0O81OaPhFPuXm7BiwLv7igoZJzv/+5OxQiKNGxDMl50BzL0KY9BYHC+z 6Iexgci64JbnBwywzRrzKjd2z0a1IQNBSBshY0nppouLyjXf3wSSjbBrvehZIUyHYi8S t86O0kP4oGnhWivDriJa/oIrCMa7oguGOne9g= Received: by 10.224.79.231 with SMTP id q39mr2360995qak.163.1266700220263; Sat, 20 Feb 2010 13:10:20 -0800 (PST) Received: from localhost (c-24-63-65-243.hsd1.vt.comcast.net [24.63.65.243]) by mx.google.com with ESMTPS id 4sm4487469qwe.43.2010.02.20.13.10.19 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 20 Feb 2010 13:10:19 -0800 (PST) From: Mark Alexander To: sup-talk In-reply-to: <1266687464-sup-6371@ben-laptop> References: <1266533680-sup-7580@sgoldmanlinux.tower-research.com> <1266612722-sup-5668@sgoldmanlinux.tower-research.com> <1266687464-sup-6371@ben-laptop> Date: Sat, 20 Feb 2010 16:10:18 -0500 Message-Id: <1266699970-sup-8044@r50p> User-Agent: Sup/git Subject: Re: [sup-talk] Switching to Exchange 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 Ben Gamari's message of Sat Feb 20 12:38:58 -0500 2010: > I would strongly encourage you to look into offlineimap. It's designed > exactly for this sort of application and does its job very well. For the past year or so, I've been using fetchmail + postfix + procmail to fetch mail to ~/Maildir. Is there any reason why offlineimap would be a better solution for use with sup? My understanding was that sup does not modify the mail sources, so there would be no changes that would need to be propagated back to the IMAP server. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk