Re: Using TAB to check for new messages

> :) The problem I'm having is that when I hit TAB while viewing the default 
> :) inbox, sometimes pine detects recent messages in the other incoming 
> :) folders, other times it doesn't (and it seems to favor not detecting 
> :) recent messages!).
> :) 
> :) This feature seems to be very unreliable, unless there are some options 
> :) that I can tweak to make it work better. I definitely do not want the 
> :) option "tab-uses-unseen-for-next-folder" as I usually keep messages 
> :) marked as New in my inboxes.
>
> Tim,
>
>   Do you use the IMAPSTATUS token in the index-format?. If not, make sure 
> you use it.
>
>   A recent message is marked as "N" or "R", while and unseen message is 
> marked as "U" when you use IMAPSTATUS. If you have never tweaked the 
> index-format variable, then both recent and unseen messages are marked as 
> "N". This will only lead you to confusion.
>   
No, I've never changed index-format from its default. Are you saying 
that this will help pine better identify recent messages or it will help 
me identify the recent vs. unseen messages?
>   If you use tab-uses-unseen-for-next-folder, then Pine will open the next 
> folder if there are unseen (but maybe none recent) messages. If you only 
> want to use tab to check for recent messages, then unset this feature. The 
> down side, though, is that since Pine keeps (a certain number of) streams 
> open then Pine keeps those imap folders open.  The down side of this 
> method is the following situation:
>
>   * You open a folder in an IMAP server,
>   * You (believe that you) close that folder
>   * While the folder is "closed", a new message arrives
>   * You quit Pine or at least 25 minutes have elapsed since the last time 
>     you closed this folder.
>
> Under this sequence of events, the next time (you open Pine and) you open 
> that IMAP folder, the "new" messages will be tagged UNSEEN, because they 
> are not recent anymore. A message can only be recent on one session, and 
> that one is the one that you thought you had closed, but Pine did not.
>
>   If you want to avoid this problem, set the variable 
> max-remote-connections to 0 (zero). The help text makes me believe that 
> this may not work fully, but I believe it will work if your inbox and this 
> folder are in different servers. The help text is not clear about how 
> setting the max-remoe-connection value to zero may fail in this situation.
>
>   Does this help?
>   
Hmm, not sure I understand the explanation in the Help at all and it 
seems to imply that I should let it set to its default of 2. The Help 
also mentions Stay-Open-Folders. Should I make all my Inboxes 
Stay-Open-Folders so that pine never closes the connection for the 
Inboxes? Will this help pine correctly identify recent messages or is 
the opposite that I want (i.e. I want pine to actually close the folder)?

I have pine set to check for new mail every 30 sec. (I really wish it 
supported the IMAP IDLE command like Thunderbird and other clients do) - 
does this impact in any way the identification of recent messages?

Sorry, but I'm still confused as to what pine considers a recent message 
and why it can't keep some state/snapshot of the state of each Inbox 
when pine has last seen it.

Thanks for your help.

Tim

_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info