From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.13.12 with SMTP id z12cs1170036ebz; Sun, 3 Jan 2010 14:12:11 -0800 (PST) Received: by 10.224.97.10 with SMTP id j10mr10820767qan.64.1262556730083; Sun, 03 Jan 2010 14:12:10 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 9si18980778qyk.95.2010.01.03.14.12.08; Sun, 03 Jan 2010 14:12:09 -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; DomainKey-Status: bad (test mode) 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; domainkeys=hardfail (test mode) header.From=murks@lavabit.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 37D861858291; Sun, 3 Jan 2010 17:12:08 -0500 (EST) X-Greylist: delayed 1857 seconds by postgrey-1.31 at rubyforge.org; Tue, 29 Dec 2009 09:16:42 EST Received: from karen.lavabit.com (karen.lavabit.com [72.249.41.33]) by rubyforge.org (Postfix) with ESMTP id 79D8D18582BF for ; Tue, 29 Dec 2009 09:16:42 -0500 (EST) Received: from h.earth.lavabit.com (h.earth.lavabit.com [192.168.111.17]) by karen.lavabit.com (Postfix) with ESMTP id 6758F11B8B2 for ; Tue, 29 Dec 2009 07:45:42 -0600 (CST) Received: from localhost (eris.mozart.uni-klu.ac.at [143.205.216.185]) by lavabit.com with ESMTP id B7ETRI74ZU3W for ; Tue, 29 Dec 2009 07:45:40 -0600 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lavabit; d=lavabit.com; b=vHdgs5NcHkSgysz8gpLM/U3/g7Jr/MzP8iLLqGZt31+8E0/Y5Uq92pG/BS0zJvTwXwfn+RdTjVEHnweNBidzflqMX53x8gTgYcFbP0jVE4LHAuXgD/wdLbMvjbKZ8+lrmuFAvhNSvvj/Gu/hXYGYTiKoStPkmE4trUf5aAjV16o=; h=Content-Type:Subject:From:To:Date:Message-Id:User-Agent:Content-Transfer-Encoding; From: =?utf-8?q?Philipp_=C3=9Cberbacher?= To: sup-talk Date: Tue, 29 Dec 2009 14:45:38 +0100 Message-Id: <1262093816-sup-8151@tw> User-Agent: Sup/0.9.1 X-Mailman-Approved-At: Sun, 03 Jan 2010 16:54:55 -0500 Subject: [sup-talk] unread status 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 Hi, during the last couple of days I managed to get sup up and running, using ruby 1.8.7, xapian, msmtp and offlineimap. Now that I use it I noticed strange behavior regarding unread messages. It works like this: New messages in the inbox, I read through them, hitting 'a'. The messages vanish from the Inbox. So far so good. I hit 'L' 'Enter' and notice that all messages I just read are listed as unread. I navigate to unread, read the messages again and hit 'a'. Now they aren't marked as unread anymore. Also, when I read them in the inbox and they are still labeled unread and I restart sup they aren't labeled unread anymore. Well, expected behavior is to have them labeled read after I read them, obviously. I experienced something similar when I used the built-in imap support. There it wouldn't really Poll when I hit P, new messages only showed up after I restarted sup. Either these are bugs or I don't get how sup works, either way, help is appreciated. Regards, Philipp _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk