Mark Crispin napsal/wrote, On 09/07/08 19:42:
The whole point of RO access, and the EXAMINE command, is to "make no changes".
Snarfing is a change.
But not on behalf of the EXAMINE command. The snarf will not run
"because EXAMINE issued" but "because there is new mail in
/var/mail/<...> and we are running"
So, although EXAMINE command mean "no changes", the changes in the
mailbox content caused by external event (e.g. new mail arrival) shall
not be ignored.
As a convenience (and a convenience only), the STATUS command reports what
would happen if RW access were to happen, since the most common use of STATUS
is to probe to see if there is new mail in a non-open mailbox.
From the view of the mailbox client, there is only one INBOX. The
implementation store it's data in two files, but it is internal
implementation of the driver.
It's external event that changed the the content of INBOX, the "snarf"
is internal implementation handling such external event - not the
EXAMINE command.
The "bugfix" would be to remove that convenience from STATUS.
Not my opinion. STATUS (and all other commands) shall return the data
related to INBOX content, despite the internal implementation details
(e.g. number of files or other data structures holding it's data).
Just my $0.02 ...
Dan
P.S. Please note the english is not my native language, so if something
sounds so strong or as an offence it's unintentional.
In the fact, there are 5 messages in MBX ~/INBOX and one in
/var/mail/
The STATUS command is based on results of mbx_status() function which
count messages in both ~/INBOX and /var/mail/... mailboxes.
The NOOP do nothing, because the folder is opened read-only.
The EXAMINE return data from ~/INBOX only (opened RO).
As a result the client write "You have 6 messages; Displaying 1..5 of 5
_______________________________________________
Imap-uw mailing list
[email protected]
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
