From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.130.91 with SMTP id r27cs34951bks; Mon, 21 Jun 2010 04:27:47 -0700 (PDT) Received: by 10.231.192.144 with SMTP id dq16mr5159773ibb.19.1277119666787; Mon, 21 Jun 2010 04:27:46 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 13si16200440ibo.100.2010.06.21.04.27.46; Mon, 21 Jun 2010 04:27:46 -0700 (PDT) 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 0A0F91858370; Mon, 21 Jun 2010 07:27:46 -0400 (EDT) Received: from mail-gw0-f50.google.com (mail-gw0-f50.google.com [74.125.83.50]) by rubyforge.org (Postfix) with ESMTP id 4CC011858364 for ; Mon, 21 Jun 2010 07:27:28 -0400 (EDT) Received: by gwb1 with SMTP id 1so2220514gwb.23 for ; Mon, 21 Jun 2010 04:27:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=M2oxSnThfRdivnqMkf5Me5ebY4KH86yafWUfPJao5GM=; b=tsOtCr1hK9GVhp8YfQCY0L2W4U9sp8W9t6dXhFsW7sMRlaUBsdK+Yq7jpdPA5aOk1F F5vsBNdPVghvSCG3i2SEuGJRWxAlf0x1KxlPMK81lRguHX5wNJyPQFAy2WhpfSLBWbnY mDwSYHVsG6texfqLW812Of3+cDMfRPrL0FrIA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=f3HWsgD6fJsq1N9PkF/T3t037CLQsmvLo7MyUzYYUtLtkBFBNj51ozaH81BU7h/33j av8n0KJ6/XTucZOCd0j1o1G5uF0Jb2NANykS4qAg2beV3y0kdP57VNzaSJHsKp8DK4fp 0jpqhZOO9CF5Wi1MB8/Ks/6A/tGeg606E1fzA= MIME-Version: 1.0 Received: by 10.229.189.140 with SMTP id de12mr2348791qcb.275.1277119647626; Mon, 21 Jun 2010 04:27:27 -0700 (PDT) Received: by 10.229.222.209 with HTTP; Mon, 21 Jun 2010 04:27:27 -0700 (PDT) Date: Mon, 21 Jun 2010 12:27:27 +0100 Message-ID: From: "Luis P. Mendes" To: sup-talk@rubyforge.org Subject: [sup-talk] Sup with several gmail accounts - advice needed 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Hi all, I just registered to this mailing list and am yet configuring sup. Before arriving to sup I was configuring mutt so that I could drop web based gmail. I have to congratulate the author and contributors of this excellent program. Although I've searched through the archived mailing list (not thoroughly) I need some advice from you. I have a main Gmail account and two other minor ones that are redirected to the main one. Mails from the minor ones get tagged whenever they arrive to the main one. In the main one, I have dozens of filters where some mails get tagged and archived whenever they arrive, other get tagged and not archived and still others just go to inbox. Since I began configuring mutt and until I found out sup, I had offlineimap synchronizing emails between gmail and my ~/Mail folder (Slackware LInux). I opened mutt and could browse to any subfolder I wanted. In Sup, what is the best way? Do I just add the '[Gmail].All mail' folder that is being synchronized with gmail and then I have to redo in sup all the filters I have in web based gmail? Or do I have advantages in adding to sup all the subfolders in disk, including the 'All mail' and get plenty of email repeated, as they already are because of offlineimap synchronization. Is there any other method for gmail imap synchronization that is preferred by sup users? I've read that upward imap synchronization is not yet available or is limited. This is also an issue for me. I can expect that it is going to be operational in the near term? If so, I could live well using almost only local based sup to manage my emails. When full synchronization is ready, web gmail could get updated like local sup. Right or not? Luis _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk