Re: [Mutt] #969: Can't clear the 'N' (unseen) flag on read-only
#969: Can't clear the 'N' (unseen) flag on read-only IMAP folders
Changes (by brendan):
* owner: mutt-dev => brendan
* milestone: => 1.6
Old description:
> {{{
> Package: mutt
> Version: 1.3.25i
> Severity: normal
>
> -- Please type your report below this line
> When reading read-only IMAP folders, I used to be able (1.2.5i) to
> clear the new flag by reading the message. When updating to 1.3.25i,
> the 'N' flag just stays and is still there the next time around. Going
> back to 1.2.5i, I notice that the 'toggle-new' function didn't work
> there on read-only imap folders, even though the flag got cleared by
> reading the message.
>
> Looking at RFC 2060, the client is allowed to modify the Seen flag if
> the server returns PERMANENTFLAGS on a SELECT:
>
> Here's a read-write folder:
>
> . select inbox
> * FLAGS (\Answered \Flagged \Draft \Deleted \Seen)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)]
> * 210 EXISTS
> * 0 RECENT
> * OK [UIDVALIDITY 914040081]
> * OK [UIDNEXT 9885]
> . OK [READ-WRITE] Completed
>
> and here's a read-only one:
>
> . select fulcrum.internal.ms
> * FLAGS (\Answered \Flagged \Draft \Deleted \Seen)
> * OK [PERMANENTFLAGS (\Seen)]
> * 7874 EXISTS
> * 0 RECENT
> * OK [UNSEEN 7872]
> * OK [UIDVALIDITY 914048337]
> * OK [UIDNEXT 7946]
> . OK [READ-ONLY] Completed
>
> The PERMANENTFLAGS shows which flags out of those listed in FLAGS
> the client is allowed to change permanently.
>
> "If the client can not change the permanent state of one or more of
> the flags listed in the FLAGS untagged response, the server SHOULD
> send a PERMANENTFLAGS response code in an OK untagged response,
> listing the flags that the client can change permanently."
>
> Hope this helps....
> rik.
>
> -- Mutt Version Information
>
> Mutt 1.3.25i (2002-01-01)
> Copyright (C) 1996-2001 Michael R. Elkins and others.
> Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
> Mutt is free software, and you are welcome to redistribute it
> under certain conditions; type `mutt -vv' for details.
>
> System: SunOS 5.7 (sun4u) [using slang 9938]
> Compile options:
> -DOMAIN
> +DEBUG
> -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE
> -USE_FCNTL -USE_FLOCK
> -USE_POP +USE_IMAP -USE_GSS +USE_SSL -USE_SASL
> -HAVE_REGCOMP +USE_GNU_REGEX
> +HAVE_COLOR -HAVE_START_COLOR -HAVE_TYPEAHEAD -HAVE_BKGDSET
> -HAVE_CURS_SET -HAVE_META -HAVE_RESIZETERM
> +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT
> +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET
> +HAVE_LANGINFO_YESEXPR
> +HAVE_ICONV +ICONV_NONTRANS +HAVE_GETSID -HAVE_GETADDRINFO
> -ISPELL
> SENDMAIL="/usr/lib/sendmail"
> MAILPATH="/var/mail"
> PKGDATADIR="/opt/net//share/mutt"
> SYSCONFDIR="/opt/net/lib/mutt"
> EXECSHELL="/bin/sh"
> -MIXMASTER
> To contact the developers, please mail to <mutt-dev@xxxxxxxx>.
> To report a bug, please use the flea(1) utility.
>
>
> >How-To-Repeat:
> >Fix:
> }}}
New description:
When reading read-only IMAP folders, I used to be able (1.2.5i) to
clear the new flag by reading the message. When updating to 1.3.25i,
the 'N' flag just stays and is still there the next time around. Going
back to 1.2.5i, I notice that the 'toggle-new' function didn't work
there on read-only imap folders, even though the flag got cleared by
reading the message.
Looking at RFC 2060, the client is allowed to modify the Seen flag if
the server returns PERMANENTFLAGS on a SELECT:
Here's a read-write folder:
{{{
. select inbox
* FLAGS (\Answered \Flagged \Draft \Deleted \Seen)
* OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)]
* 210 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 914040081]
* OK [UIDNEXT 9885]
. OK [READ-WRITE] Completed
}}}
and here's a read-only one:
{{{
. select fulcrum.internal.ms
* FLAGS (\Answered \Flagged \Draft \Deleted \Seen)
* OK [PERMANENTFLAGS (\Seen)]
* 7874 EXISTS
* 0 RECENT
* OK [UNSEEN 7872]
* OK [UIDVALIDITY 914048337]
* OK [UIDNEXT 7946]
. OK [READ-ONLY] Completed
}}}
The PERMANENTFLAGS shows which flags out of those listed in FLAGS
the client is allowed to change permanently.
"If the client can not change the permanent state of one or more of
the flags listed in the FLAGS untagged response, the server SHOULD
send a PERMANENTFLAGS response code in an OK untagged response,
listing the flags that the client can change permanently."
Hope this helps....
rik.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/969#comment:2>