I have done some more experimentation and see that your statements are correct (I guess I should have done this before I sent off that message;-).
BUT... I still don't always get new messages using bincimap (that I do get using Courier;-).
After some more experimentation, I think that I have found that bincimap only checks the currently selected folder, not all folders for a STATUS. My latest experiment was done as follows:
1. I have a separate Maildir configured for Courier and an IMAPdir configured for bincimap, with all messages being delivered to both.
2. I updated to the latest version of bincimap (but I have bothered to see which version of Courier is in use)
3. I updated to the latest version of Opera v 7.20b7
4. I shutdown Opera
5. I sent a test message to myself
6. I moved the message out of "new" (both bin in the Maildir and the IMAPdir)
7. I shutdown qmail-send
8. I started up Opera and read all my messages (all actions in Opera are for both bincimap and courier)
9. I turned off automatic fetch in Opera
10. I shutdown Opera
11. I removed Opera's log files
12. I started up Opera
13. I did a manual message fetch of all messages
14. I made sure everything looked as expected
15. I selected my bincIMAP folder
16. I more manual message fetchs at 19:00 & 19:01 to make sure everything was stabalized
17. I moved the test messages back into the "new" folders
18. I did a manual fetch of messages at 19:02 - Courier found the new message (in the STATUS query), but not bincimap
19. I did more manual fetches at 19:03 and 19:09 to give bincimap time to find the new message, but it did not
20. I selected the INBOX in Opera at 19:10 which caused bincimap to report the new message
21. I shutdown Opera
22. I restarted qmail-send
23. I posted the log files to http://www.instantiated.ca/download/bincimap-opera-2003-08-29.log and http://www.instantiated.ca/download/courier-opera-2003-08-29.log
24. I posted this message
25. I went for dinner;-)
Side note: The IMAP RFC suggests that the NOOP command be used to check for new messages. Does bincimap report new messages (or any other change of status) when it gets a NOOP?
Regards
Henry
On Thu, 28 Aug 2003 07:25:34 +0200 (CEST), Andreas Aardal Hanssen <[EMAIL PROTECTED]> wrote:
On Wed, 27 Aug 2003, Henry Baragar wrote:Actually, it means that Opera has only asked for the number of messages,So, Opera sends a "STATUS INBOX (MESSAGES UIDNEXT RECENT)". Should it send
the next UID value and the number of recent messages. Opera can also ask
for UNSEEN, but it doesn't.
a "STATUS INBOX (MESSAGES UIDNEXT RECENT UNSEEN)"? Is there something else
it should send (in your opinion)?
It shouldn't need to ask for more - UIDNEXT is enough to check if there have been deliveries to the mailbox - MESSAGES and RECENT are probably to know how many messages to report.
Actually, the '1 RECENT' means that one message has arrived in theEr, except that Opera does not mark a message read until the user
mailbox
that Opera has never seen before. It denotes a recent delivery, and most
email clients use this (and a changed MESSAGES or UNSEEN) to report a
recent delivery.
explicitly marks the message as being read. The '1 recent' refered to a
message that Opera downloaded and that I saw (ok read) but did not actually
If Opera did not have the folder selected, then the RECENT 1 means that Opera has never seen it before. Once the folder is selected, the RECENT flag remains throughout the session and is removed when the folder is closed again. So it's not persistent.
The \Seen flag means wether you as the user have actually downloaded the message and read at least part of it. So a message being unseen does not necessarily mean that it just got delivered.
name. In this case, there was one unread message in "cur" and another unread message in "new" that was also unseen.
The message in new/ was the message that STATUS reported as RECENT 1. This
is the message that should have triggered a recent delivery in Opera.
Now I realize that Binc may not update UIDNEXT with the STATUS command. So it can report 1 RECENT but then, logically, UIDNEXT should have increased by one value. I will look more into this, but if this is the case then the missing delivery notification may well be a bug in Binc.
Andy :-)
-- Henry Baragar Principal, Technical Architecture 416-453-5626 Instantiated Software Inc. http://www.instantiated.ca
