From: col@baibell.org (Colin Bell)
Subject: [sup-talk] Seen flag treated incorrectly on IMAP mail
Date: Fri, 02 Nov 2007 09:09:00 +1100 [thread overview]
Message-ID: <1193954846-sup-9117@lankhmar> (raw)
In-Reply-To: <47299802.50007@quintic.co.uk>
Excerpts from Marcus Williams's message of Thu Nov 01 20:10:26 +1100 2007:
>
> Yep, I submitted a patch earlier last month (search for imap patch) to
> fix this although what it did was use the /Recent flag to check for
> unread messages. This works as long as you dont use the IMAP source in
> any other client before sup checks for new messages.
Got it. Thanks for the patch.
next prev parent reply other threads:[~2007-11-01 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2d4a3f900012fe89@IMSS-WIN>
2007-11-01 9:10 ` Marcus Williams
2007-11-01 22:09 ` Colin Bell [this message]
2007-10-31 2:12 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=1193954846-sup-9117@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