Great ! Some elements do need quotes but some others don't - I found
that out when I changed the code initially to remove all quoting and
got these helpful hints from aox :
ct 3 10:16:18 messaging Archiveopteryx: 7591/6/7/4/1 user is not quoted
in DIGEST-MD5 response
Oct 3 10:16:18 messaging Archiveopteryx: 7591/6/7/4/1 realm is not
quoted in DIGEST-MD5 response
Oct 3 10:16:18 messaging Archiveopteryx: 7591/6/7/4/1 nonce is not
quoted in DIGEST-MD5 response
Oct 3 10:16:18 messaging Archiveopteryx: 7591/6/7/4/1 cnonce is not
quoted in DIGEST-MD5 response
Oct 3 10:16:18 messaging Archiveopteryx: 7591/6/7/4/1 uri is not quoted
in DIGEST-MD5 response
The digest-md5 is picked by MailKit because of this :
public static readonly string[] AuthMechanismRank = {
"SCRAM-SHA-1", "NTLM", "DIGEST-MD5", "CRAM-MD5", "XOAUTH2",
"PLAIN", "LOGIN"
};
DIGEST-MD5 is the first (and MailKit thinks most secure) option which
matches capabilities between client and server.
This could easily be re-ordered to something else, especially if it's
not really the most secure or preferable option.
What would you suggest ? I can just make the change since I've already
made a few !
The .NET client is using LOGIN I think but I've not had time to try to
debug that; I suspect it may also be mis-matching the protocol since
everything I found said I was doing it right in theory and the MailKit
experience essentially confirms that. I'll fire up my aox development
environment again and add some additional debug info to see if I can
track that.
Jim
On 03/10/2014 13:34, Arnt Gulbrandsen wrote:
> He answered already and will remove the quote characters from Mailkit.
> Which solves half the problem, but it sounds like at least one other
> windows client might have the same problem?
>
> Arnt
>
