Re: Gmail IMAP old vs new
- To: mutt-users@xxxxxxxx
- Subject: Re: Gmail IMAP old vs new
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Sun, 4 Nov 2007 22:07:05 -0600
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date:from:to:subject:message-id:references:mime-version:content-type:in-reply-to; q=dns/txt; s=default; bh=3B7bLH8ul53ehrWYNGbniqkYdrs=; b=fHa22nruRI1LZpn89tnw4JGUtr2ZIZ+my5aoehzrvmxfWAisMEtuGRvlg3TofylYFdR9/c0FxUkDGe6j78ty6zmDyQtsbS0i8aJRPzYht5p0ayzsmvRzRC+GnB9QxqyOkQ9yyRqlQlffS6NM7/fzncRwEFvu8B7fWX9G08Ocae0=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=ITwJI+ime317jjBB2YKxFMEUlDFOjPEyBgVmLMYFHIMr90pPpIaArmACoGzXMCCehExsfgjYNxGC6x7wPrPQdcOL+bhuS6918zxsK9aGkKXBExDP9UG5Bc1yN1fvjg/O5kWzYLyD6uKsN2oyZeRL/vH1/YVZ9WLitF1DkfCm6O0=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:User-Agent;
- In-reply-to: <20071104192524.GC8511@herminie>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- References: <20071104192524.GC8511@herminie>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.16 (2007-10-18)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday, November 4 at 01:25 PM, quoth Chris Sussmann:
> I have been using mutt for a while with getmail and pop access to my
> gmail account. Now with gmail offering IMAP, I am trying to switch
> over.
Technically, Gmail's IMAP isn't *quite* IMAP, and has quite a few
incorrect implementation details. See this discussion (Crispin
invented IMAP):
http://www.wired.com/software/webservices/news/2007/10/imap
> But when I receive new mail the status flag is O (for old) and not N
> (for New).
For a long time, mutt's support for O and N flags was dependent upon
IMAP support for the \Recent flag, which Gmail doesn't support at all
(as you can see here:
http://mail.google.com/support/bin/answer.py?answer=78761&topic=12762&disablechatbrowsercheck=1).
It's been rewritten recently (i.e. back around January 2006 or so) to
use \Seen instead, so you may want to upgrade your mutt from 1.5.11
(which relies on \Recent, which gmail doesn't support) to mutt 1.5.12
or newer (which relies on \Seen).
> My apologies if this is not really a mutt issue but a gmail issue.
Unfortunately, the problem is in fact they're *both* at fault. :) Or,
to put it more accurately, Gmail is really at fault, but newer mutt
versions have a workaround that works more reliably than the original
behavior (such that the old behavior could be considered a mutt "bug"
even though it really isn't).
~Kyle
- --
Be sincere; be brief; be seated.
-- Franklin D. Roosevelt
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFHLpbpBkIOoMqOI14RAjthAJ9wZNfIdMeJocckeqTrTKpbOniavQCfXH6S
6CIKwtu2tjq1CBHRzBe+oPI=
=f835
-----END PGP SIGNATURE-----