Hi, I've been having problems using submission on port 587.
Clients like Thunderbird, Outlook etc. all seem to work OK (Good !). However, trying to get a .NET server application to send mail by authentication keeps failing with user "" failed authentication errors. At first, it looked like .NET uses some Exchange specific communications so I switched to a different mail library (MailKit in this case - which was a good choice as I'll explain). The problems persisted and MailKit also failed to send and had similar errors. Turning up the logging to debug, I then got some useful hints : Oct 3 09:18:48 messaging Archiveopteryx: 7591/6/5/4/1 Full DIGEST-MD5 response was: <<username="***@***.com",realm="messaging",nonce="aF0MT/XIkgtng/BtwJy9p2W1b3uZFo1w8wXVGTO2gdkp4x6RDA8rbZ4HPnh6NoON",cnonce="3K1cVYpZJt23KJOyP0ee",nc=00000001,qop="auth",digest-uri="smtp/messaging",response="9a1f7dc3781c28a0071f0bd520661d55",algorithm="md5-sess">> And : Oct 3 10:08:51 messaging Archiveopteryx: 7591/6/8/4/1 resp <<"9e5ee49ef8d07b875d7fff80274b8c73">> has length 34 (not 32) in DIGEST-MD5 response Which indicated the parsing of the MD5 auth response did not like the quoting of the response element - the quotes add 2 characters giving 34 instead of expected 32. As I had the source code to MailKit, I was able to alter the relevant section to remove the quotations, firstly from just the response element but that still failed. I then altered it so quoting was removed from qop, response and algorithm and then I could authenticate. (The benefits of open source!) However, this looks like an interoperability issue on the Archiveopteryx side. As I've been working on this other project and not had much time recently, it looks like I need to come back round to aox and look at that auth code as it should permit some additional quotation by the looks of things. Any thoughts/comments ? Jim
