Re: [Imap-protocol] What is the current consensus on the Recent flag?

--===============1009404212594549631==
Content-Type: multipart/alternative; boundary=001a113e5798bf17ee054b2de0dd

--001a113e5798bf17ee054b2de0dd
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Awesome, thanks for the feedback! If \Recent in practice only matters for
the Dovecot ImapTest then I won't waste any time with it. The server I'm
building is a distributed one (run many instances, connect to any of these
(mailbox updates between server instances are propagated using a journal))
and ensuring \Recent to be seen by just a single session would mean some
kind of extra locking and extra overhead for no gains whatsoever.

Best regards,
Andris Reinman
http://wildduck.email/


On Tue, Mar 14, 2017 at 5:49 PM, Neil Jhaveri <[email protected]> wrote:

> I agree, and we aren=E2=80=99t using it in iOS/macOS Mail.  We=E2=80=99ve=
 thought about it
> several times, though=E2=80=A6 but every time, the semantics proved to no=
t be
> reliable enough.
>
> On Mar 10, 2017, at 1:42 PM, Andris Reinman <[email protected]>
> wrote:
>
> Hi all,
>
> I'm building a new open source IMAP server (https://github.com/wildduck-
> email/wildduck) and was wondering about the \Recent flag. Is it even
> needed today? I would like to keep my server as standards compliant as
> possible but the ephemeral nature of \Recent makes it a bit difficult to
> sync between sessions in multiple hosts. It would be doable but the
> complexity needed does not make it seem worth it.
>
> Is there even any major client using this flag in a sane way? I don't
> think I have even ever encountered it outside the RFCs.
>
> Best regards,
> Andris Reinman
> _______________________________________________
> Imap-protocol mailing list
> [email protected]
> http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol
>
>
>

--001a113e5798bf17ee054b2de0dd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Awesome, thanks for the feedback! If \Recent in practice o=
nly matters for the Dovecot ImapTest then I won&#39;t waste any time with i=
t. The server I&#39;m building is a distributed one (run many instances, co=
nnect to any of these (mailbox updates between server instances are propaga=
ted using a journal)) and ensuring \Recent to be seen by just a single sess=
ion would mean some kind of extra locking and extra overhead for no gains w=
hatsoever.<div><br></div><div>Best regards,</div><div>Andris Reinman<br><di=
v><a href=3D"http://wildduck.email/">http://wildduck.email/</a><br></div><d=
iv><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Ma=
r 14, 2017 at 5:49 PM, Neil Jhaveri <span dir=3D"ltr">&lt;<a href=3D"mailto=
:[email protected]" target=3D"_blank">[email protected]</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">



<div style=3D"word-wrap:break-word">
I agree, and we aren=E2=80=99t using it in iOS/macOS Mail.=C2=A0 We=E2=80=
=99ve thought about it several times, though=E2=80=A6 but every time, the s=
emantics proved to not be reliable enough.
<div>
<div>
<div>
<div><br>
<div>
<div>
<blockquote type=3D"cite"><div><div class=3D"gmail-h5">
<div>On Mar 10, 2017, at 1:42 PM, Andris Reinman &lt;<a href=3D"mailto:andr=
[email protected]" target=3D"_blank">[email protected]</a>&gt; wr=
ote:</div>
<br class=3D"gmail-m_-3718121291882000284Apple-interchange-newline">
</div></div><div><div><div class=3D"gmail-h5">
<div dir=3D"ltr">Hi all,
<div><br>
</div>
<div>I&#39;m building a new open source IMAP server (<a href=3D"https://git=
hub.com/wildduck-email/wildduck" target=3D"_blank">https://github.com/wildd=
uck-<wbr>email/wildduck</a>) and was wondering about the \Recent flag. Is i=
t even needed today? I would like to keep my
 server as standards compliant as possible but the ephemeral nature of \Rec=
ent makes it a bit difficult to sync between sessions in multiple hosts. It=
 would be doable but the complexity needed does not make it seem worth it.<=
/div>
<div><br>
</div>
<div>Is there even any major client using this flag in a sane way? I don&#3=
9;t think I have even ever encountered it outside the RFCs.</div>
<div><br>
</div>
<div>Best regards,</div>
<div>Andris Reinman</div>
</div></div></div><span class=3D"gmail-">
______________________________<wbr>_________________<br>
Imap-protocol mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">Imap-pr=
[email protected]</a><br>
<a href=3D"http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol=
" target=3D"_blank">http://mailman13.u.washington.<wbr>edu/mailman/listinfo=
/imap-<wbr>protocol</a></span></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>

</blockquote></div><br></div></div></div></div>

--001a113e5798bf17ee054b2de0dd--

--===============1009404212594549631==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Imap-protocol mailing list
[email protected]
http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol
--===============1009404212594549631==--