mailing list archives

meli community discussions

⚠️ if something does not work as intended when interracting with the mailing lists,
reach out Github mirror Gitea repo @epilys:matrix.org

E-mail headers
From: Timo Sirainen <tss@iki.fi>
To: imap-protocol@u.washington.edu
Date: Fri, 08 Jun 2018 12:34:50 -0000
Message-ID: 2A78534C-8CFD-42D5-BC70-6C54A92FDF16@iki.fi permalink / raw / eml / mbox
In-Reply-To: 201303052001.r25K1hGk022426@mxout14.cac.washington.edu
References: 201303052001.r25K1hGk022426@mxout14.cac.washington.edu
On 5.3.2013, at 22.01, Pete Maclean <imap@maclean.com> wrote:

> Section 3.3.2 of RFC 4551 states:
> 
>   Once the client specified the MODSEQ message data item in a FETCH
>   request, the server MUST include the MODSEQ fetch response data items
>   in all subsequent unsolicited FETCH responses.
> 
> I wonder how specific this is intended to be.  If I simply have my server include a MODSEQ on all subsequent unsolicited FETCH responses once CONDSTORE has been enabled (which a FETCH with a MODSEQ implicitly serves to do) would that be wrong?  Be wasteful?  Break clients left and right?

Aren't you saying here exactly the same thing as the RFC? Or did you mean that all subsequent untagged FETCH responses, unsolicited and solicited? Anyway I doubt it would break anything if all FETCH responses had MODSEQs other than possibly being a little bit wasteful.
Reply