wasm-demo/demo/ermis-f/imap-protocol/cur/1600094981.22544.mbox:2,S

49 lines
1.8 KiB
Plaintext

MBOX-Line: From kmansoft at gmail.com Fri May 12 12:55:26 2017
To: imap-protocol@u.washington.edu
From: Kostya Vasilyev <kmansoft@gmail.com>
Date: Fri Jun 8 12:34:55 2018
Subject: [Imap-protocol] Authenticating with iCloud
In-Reply-To: <1494617162.302895.974862968.74D8B3D4@webmail.messagingengine.com>
References: <f5c54374-6858-92e3-3ea6-1b02c9df65f6@comaxis.com>
<1494617162.302895.974862968.74D8B3D4@webmail.messagingengine.com>
Message-ID: <CAN7dqjDDUnvX81RjY+pn1UcXA9Zhe8V6K9dX1nuOgFwamm9quw@mail.gmail.com>
Another potential reason:
The @mac.com / @me.com IMAP servers advertise SASL PLAIN but it
doesn't actually work with a full email address (user@mac.com or
user@me.com), only works with "user".
So two possible workarounds:
- Do not use SASL PLAIN for imap.mail.me.com / mac.com
- Or strip the domain part from the login
PS - at least the above was the case 2-3 years ago when we ran into
this with our email app and had to add a workaround.
-- K
2017-05-12 22:26 GMT+03:00 Dave Warren <davew@hireahit.com>:
> Two-factor authentication, perhaps requiring an App Specific password?
>
> On Fri, May 12, 2017, at 12:14, Jeff McKay wrote:
>> Does the server imap.mail.me.com not support a standard IMAP logon with
>> a user id and password? I use port 993,
>> just a simple login command: LOGIN "username@icloud.com" "password"
>> but get back "Authentication failed". My customer claims the user name
>> and password are valid.
>>
>> _______________________________________________
>> Imap-protocol mailing list
>> Imap-protocol@u.washington.edu
>> http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol
>>
>
> _______________________________________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu
> http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol