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 is highlighted at debug level but perhaps it should also be at a lower log level like info) I had problems with multiple clients (including the built in .NET framework one) so it may be there is a widespread bad implementation of the protocol which aox needs to have the option to handle. I do agree that clients properly following the RFC would be better but it seems this is not so common. Jim On 03/10/2014 13:10, Arnt Gulbrandsen wrote: > 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. > AAAA encodes three null bytes. If a decoder skips unknown input, then > three null bytes can also be encoded as "AAAA" "AA"AA", "AAAA', and > even "AAAA½", because ", ½ and ' are not in the base64 set. > > I'll ask the mailkit author why mailkit sends quotes. > > Arnt >
