<<< Date Index >>>     <<< Thread Index >>>

Re: IMAP status flags lost when refiling



On Sat, Apr 02, 2005 at 02:06:02AM -0500, Kyle Wheeler wrote:
> On Friday, April  1 at 08:24 PM, quoth Brendan Cully:
> > On Saturday, 02 April 2005 at 13:20, Tamotsu Takahashi wrote:
> > > On Fri, Apr 01, 2005 at 09:33:51PM -0500, Daniel Jacobowitz wrote:
> > > > On Wed, Mar 30, 2005 at 03:28:20PM +0100, Dave Ewart wrote:
> > > > > On Tuesday, 29.03.2005 at 15:21 -0500, Kyle Wheeler wrote:
> > > > > 
> > > > > > I've looked through the archives, and I'm not sure if this bug has 
> > > > > > been 
> > > > > > brought up since the bug database was lost... Debian 163616 
> > > > > > (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=163616) - 
> > > > > > basically, 
> > > > > > when messages are moved from one IMAP folder to another IMAP folder 
> > > > > > (on 
> > > > > > the same server), the flags that have not been saved to the server 
> > > > > > are 
> > > > > > lost.
> > > > > 
> > > > > Oh, yes please, a fix to that would be very useful.  Particularly,
> > > > > having messages which have been read in one folder appear as 'New' 
> > > > > when
> > > > > saved to another folder is very annoying.
> > > > 
> > > > Amen.  I've been running into this for a while now.
> > > 
> > > I guess that the problem (not a bug at all) is caused by
> > > server-side copying. Maybe you can safely remove these lines
> > > from commands.c (not imap/command.c):
> > 
> > I think a nicer solution is to create an option to set flags on the
> > server as soon as they've been changed in mutt. It might be slightly
> > slower, but probably not noticeable unless flags are set en masse
> > with a tagged command. I believe Pine goes this route.
> 
> Might it instead be possible to set the flags on the message after it is 
> copied? That way all the current optimizations are left in place, the 
> bandwidth used is about the same. The only thing I can think would be an 
> issue would be getting a handle on the saved message.

If you're going to do that, might as well set the flags on the message
before it is copied :-)  I'll give it a try.

-- 
Daniel Jacobowitz
CodeSourcery, LLC