Cit?t Joseph Tam <jtam.home at gmail.com>:
> azurit at pobox.sk and Tom Sommer asks:
>
>> How this ID extension can be enabled in Dovecot? From which version is
>> it supported?
>
> Accordind to Dovecot CAPA's response, it is already enabled
>
> * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID
> ENABLE IDLE STARTTLS LOGINDISABLED] Ready.
>
> However, as a previous poster noted, Dovecot doesn't do anything with
> it other than to log it. The client can elect to ignore it or send an
> ID string. The ID extension is documented here
>
> https://www.ietf.org/rfc/rfc2971.txt
>
> I speculated it could be used as a client-side CAPA info so that an IMAP
> server can modify it's behaviour knowing it's dealing with a
certain
> client, but that is flatly forbidden by RFC
>
> (Quoting from RFC)
> The sole purpose of the ID extension is to enable clients and
> servers to exchange information on their implementations for
> the purposes of statistical analysis and problem determination.
>
> ...
>
> Implementations MUST NOT make operational changes based on the
> data sent as part of the ID command or response. The ID command
> is for human consumption only, and is not to be used in improving
> the performance of clients or servers.
>
> Joseph Tam <jtam.home at gmail.com>
Thank you for info. Well, i understand that clients are not forced to
send the info but, in my logs, there's no single ID info. Do i need to
enable logging of it or something?