Re: [Mutt] #3287: imap recent not honoured

2013-01-17 Thread Mutt
#3287: imap recent not honoured -+-- Reporter: prlw1 | Owner: brendan Type: defect | Status: closed Priority: major | Milestone: 1.6

Re: [Mutt] #3287: imap recent not honoured

2012-05-25 Thread Mutt
#3287: imap recent not honoured ---+ Reporter: prlw1 | Owner: brendan Type: defect | Status: new Priority: major | Milestone: 1.6

Re: [Mutt] #3287: imap recent not honoured

2009-07-04 Thread Mutt
#3287: imap recent not honoured -+-- Reporter: prlw1 | Owner: brendan Type: defect | Status: new Priority: major | Milestone: 1.6

[Mutt] #3287: imap recent not honoured

2009-07-01 Thread Mutt
#3287: imap recent not honoured ---+ Reporter: prlw1 | Owner: brendan Type: defect | Status: new Priority: major | Milestone

Re: imap recent

2009-06-14 Thread Patrick Welche
On Thu, Jun 11, 2009 at 10:45:44AM -0500, Kyle Wheeler wrote: > On Thursday, June 11 at 01:38 PM, quoth Patrick Welche: > >I don't use the header cache - I would have to enable it to use it > >right? > >(off by default?) > > Ahhh, I assumed that you did use it. Yeah, you'd have to enable it.Hmm. >

Re: imap recent

2009-06-11 Thread Rocco Rutte
Hi, * Kyle Wheeler wrote: > Ahhh, I assumed that you did use it. Yeah, you'd have to enable it. > Hmm. I don't know how mutt handles new/old tracking on IMAP without > the header cache, but with a mailbox that big, it's going to be well > worth your while to enable it. I think via message flags.

Re: imap recent

2009-06-11 Thread Kyle Wheeler
On Thursday, June 11 at 01:38 PM, quoth Patrick Welche: I don't use the header cache - I would have to enable it to use it right? (off by default?) Ahhh, I assumed that you did use it. Yeah, you'd have to enable it. Hmm. I don't know how mutt handles new/old tracking on IMAP without the head

Re: imap recent

2009-06-11 Thread Patrick Welche
On Mon, Jun 08, 2009 at 02:49:45PM -0500, Kyle Wheeler wrote: > On Monday, June 8 at 12:21 PM, quoth Patrick Welche: > >Now I'm even more confused: mutt says after several days of not > >reading mail, mutt says: > > > >Msgs:220272 New:6 Old:710 > > > >and those refer to the 6 new messages I receiv

Re: imap recent

2009-06-08 Thread Kyle Wheeler
On Monday, June 8 at 12:21 PM, quoth Patrick Welche: Now I'm even more confused: mutt says after several days of not reading mail, mutt says: Msgs:220272 New:6 Old:710 and those refer to the 6 new messages I received while it is open. YIKES - that is a *huge* mailbox! It's interesting that

Re: imap recent

2009-06-08 Thread Patrick Welche
On Wed, Jun 03, 2009 at 10:32:09AM -0500, Kyle Wheeler wrote: > On Monday, June 1 at 10:27 PM, quoth Patrick Welche: > >So the first question is, am I missing a new setting in mutt? > > No - mutt's current behavior uses both \Unseen and \Recent along with > its own header cache in order to be rel

Re: imap recent

2009-06-03 Thread Kyle Wheeler
On Monday, June 1 at 10:27 PM, quoth Patrick Welche: So the first question is, am I missing a new setting in mutt? No - mutt's current behavior uses both \Unseen and \Recent along with its own header cache in order to be reliable across multiple brands of IMAP servers. And then how do I t

imap recent

2009-06-01 Thread Patrick Welche
Just trying today's mutt-head against a cyrus imap server. The only messages marked N are the ones which arrived while the inbox was open in mutt, not the ones which arrived since the inbox was last opened. [I think I used to have set imap_recent=yes, but now I see that imap_recent no longer exist