29 lines
1.2 KiB
Plaintext
29 lines
1.2 KiB
Plaintext
MBOX-Line: From arnt at gulbrandsen.priv.no Tue May 22 10:12:05 2007
|
|
To: imap-protocol@u.washington.edu
|
|
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
|
|
Date: Fri Jun 8 12:34:39 2018
|
|
Subject: [Imap-protocol] IMAP ID Extension
|
|
In-Reply-To: <5253.1179845809.680684@peirce.dave.cridland.net>
|
|
References: <fc2c80ae0705220733m29c6b341pe4f51cd7e2c059b5@mail.gmail.com>
|
|
<46530072.1020500@aol.com>
|
|
<5253.1179845809.680684@peirce.dave.cridland.net>
|
|
Message-ID: <J/jdB9mRGei+OhDY58O9xA.md5@libertango.oryx.com>
|
|
|
|
Dave Cridland writes:
|
|
> On Tue May 22 15:38:42 2007, John Snow wrote:
|
|
>> If not the ID command, is there another way to get client information?
|
|
>
|
|
> You could try a fingerprinting technique, I suppose - I'm pretty sure
|
|
> that nearly every client (or at least, IMAP library) out there uses
|
|
> slightly different techniques. I've never looked at doing that, but
|
|
> I'd have thought it'd be possible.
|
|
|
|
It is. Combining the format of the tags with the first few commands
|
|
gives a very fair idea of which client is being used. The only reason I
|
|
haven't written code to do it is that I don't have much need for the
|
|
resulting data (gathering load data is my only reason so far, and
|
|
that's not urgent).
|
|
|
|
Arnt
|
|
|