Re: [Imap-protocol] Is OpenEmailSurvey open to share method or code?

Another vote for clients using ID!

It's particularly bothersome with AWS or other cloud hosted email client 
implementations that don't use OAuth2. Only way to truly stop 
unrecognized access is to change password, but then you have to deal 
with repeated accesses that look like cloud originated password cracking 
attempts.

Stuart

On 3/24/15 7:28 PM, Brandon Long wrote:
>
>
> On Tue, Mar 24, 2015 at 4:15 PM, Bron Gondwana <[email protected] 
> <mailto:[email protected]>> wrote:
>
>     On Wed, Mar 25, 2015, at 10:05 AM, Gilles LAMIRAL wrote:
>     > Dear Joshua,
>     >
>     > > I don't know what options you're talking about, but it's worth
>     pointing out the Thunderbird autoconfiguration project
>     > >
>     (<https://developer.mozilla.org/en-US/docs/Mozilla/Thunderbird/Autoconfiguration>).
>     >
>     > I'll have a look at Thunderbird/Autoconfiguration,
>     > even if I go crazy when I configure a new account with Thunderbird,
>     > it is always irrelevant for what I do, the manual way is first
>     hidden,
>     > maybe presented at the end or after a failure, a headache each time.
>     >
>     > I won't start searching the imap hostname from the user login
>     parameter.
>     > I'll start by guessing server software name from the imap responses,
>     > not from a third party scan, and from hard coded rules if possible.
>
>     https://tools.ietf.org/html/rfc6186 might be your friend too.
>
>     > > If IMAP ID is supported, that is a useful command to use.
>     >
>     > A server that replied well to ID would have already announced itself
>     > in the first banner. So, for my purpose, ID looks useful when
>     useless.
>     >
>     > But thanks to mention ID, I'll add it in imapsync, this way Gmail
>     > and Outlook.com  will be able to know easily how many transfers
>     are made
>     > by imapsync each day (not difficult without ID anyway).
>
>     We like ID commands at FastMail too - we log them and it gives us
>     both an
>     idea of usage patterns, and the ability to give more accurate bug
>     reports if we
>     detect something weird.
>
>
> We also show it to users in their activity log, which is helpful so 
> they know what was connecting.
>
> Its also helpful when we need to track down a developer and have a 
> discussion about what they're doing.
>
>
>
> Brandon
>
>
>
> _______________________________________________
> Imap-protocol mailing list
> [email protected]
> http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol

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