Opened 3 years ago

Closed 3 years ago

#8283 enhancement closed duplicate (duplicate)

implement, imap NOOP return STATUS info

Reported by: burrows Owned by:
Priority: normal Milestone:
Component: mail Keywords:
Cc: Branch:


The IMAP rfc recommends the NOOP command should return status data when a mailbox is selected.

From 6.1.2,

Since any command can return a status update as untagged data, the NOOP command can be used as a periodic poll for new messages or message status updates during a period of inactivity (this is the preferred method to do this). The NOOP command can also be used to reset any inactivity autologout timer on the server.

And from 7,

An example of unilateral untagged server data occurs when the IMAP connection is in the selected state. In the selected state, the server checks the mailbox for new messages as part of command execution. Normally, this is part of the execution of every command; hence, a NOOP command suffices to check for new messages. If new messages are found, the server sends untagged EXISTS and RECENT responses reflecting the new size of the mailbox. Server implementations that offer multiple simultaneous access to the same mailbox SHOULD also send appropriate unilateral untagged FETCH and EXPUNGE responses if another agent changes the state of any message flags or expunges any messages.

My patch implements the EXISTS/RECENT behavior.

I tried writing a test, but I couldn't figure out what was going on in the imap test suites. It's only a four line change so maybe someone else can help me in writing the test.

Change History (1)

comment:1 Changed 3 years ago by burrows

Resolution: duplicate
Status: newclosed
Note: See TracTickets for help on using tickets.