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
I have problems with DIGEST-MD5 since I remember, but never tracked it down
like you did.
We accept only SSL connections and so used plaintext password as workaround.
Am 03.10.2014 um 12:33 schrieb NSS Ltd nss...@networksystemssolutions.co.uk:
. . .
Oct 3 10:08:51 messaging Archiveopteryx:
Hi Axel,
I didn't have the luxury of switching; I'm going to look at the aox code
in the next few days as this has a knock on effect on a project I have
so I need to fix it.
Thanks for confirming you'd had issues as it lets me know it's not just
some quirk I have.
Jim
On 03/10/2014 12:52, Axel
I had a look at RFCs 3501 and 4422 now, and as far as I can see those quote
characters sent by mailkit are unambiguously illegal in IMAP and SASL.
They are, however, almost legal in base64. The base64 spec says that
decoders should/may discard any characters outside the defined set.
OK - I'd downloaded from https://github.com/jstedfast
The client side is a .NET 4 application speaking to the aox server.
It may well be that the clients are not formatting correctly but it may
be helpful to have an option to permit it and certainly a log message to
say it is happening ? (It
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
On Friday, October 3, 2014 2:45:45 PM CEST, NSS Ltd wrote:
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 :
I think the guiding principle here is that things are either
