[TASK] RECENT value on NOOP new-message path may be inaccurate

[Aravinda-HWK]

What needs to be done?

• When the message count increases, the server sends RECENT based on the count delta, not the actual recent count from storage.
• The code does fetch the actual recent count, but does not use it in that path.
• Not necessarily fatal for all clients, but can produce misleading untagged RECENT responses in edge cases.

[prdai]

hi @Aravinda-HWK, i would be intrested to take this up issue, or if there is any other issue that you recommend within LSF that i can look into? pl do let me know thanks!

[silverbotlsf]

Hi @prdai, thanks for joining the conversation. Our maintainers will be here soon to help you get started.

Useful links, if you're new to the project:

• Contributing guide
• Code of conduct

Glad to have you here.

[maneesha-xyz]

Hi @prdai this issue can be taken. I have assigned it to you.

[prdai]

@maneeshaxyz could you provide any more context regarding this issue if possible so its easier for me to get started? tnx

[Aravinda-HWK]

@maneeshaxyz could you provide any more context regarding this issue if possible so its easier for me to get started? tnx

@prdai The issue is that on the NOOP/new-message path, the server sends the RECENT count based on the increase in EXISTS instead of the actual RECENT count from storage. The actual count is already being fetched, but it isn't used in that code path. You should be able to trace where the NOOP response is generated and compare it with the mailbox select/status path.