Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: col@baibell.org (Colin Bell)
Subject: [sup-talk] Seen flag treated incorrectly on IMAP mail
Date: Wed, 31 Oct 2007 13:12:30 +1100	[thread overview]
Message-ID: <1193796632-sup-4626@lankhmar> (raw)

Hi,

When I connect Sup to a Dovecot imap server all mail that is flagged as new on the server is treated as read by Sup. Sup also sees all old mail as new.

I think its caused by this code in each(...) in imap.rb

 labels = { :Seen => :unread,
            :Flagged => :starred,
            :Deleted => :deleted
          }.inject(@labels) do |cur, (imap, sup)|
    cur + (state[:flags].include?(imap) ? [sup] : [])

This seems (to my non-existent Ruby skills) to be equating the IMAP
Seen flag to be the same as the Sup Unread flag, instead of Seen as
being Not Unread.

This is running the latest code from Subversion head.

--
Col



             reply	other threads:[~2007-10-31  2:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31  2:12 Colin Bell [this message]
     [not found] <2d4a3f900012fe89@IMSS-WIN>
2007-11-01  9:10 ` Marcus Williams
2007-11-01 22:09   ` Colin Bell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1193796632-sup-4626@lankhmar \
    --to=col@baibell.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox