-
-
Notifications
You must be signed in to change notification settings - Fork 827
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for JMAP #1552
Comments
I've actually been thinking of doing this for the past year or so, it's just hard to find the time to work on it. I was also hoping to see if I could find a way to get Fastmail to pay me to write it :-) The amount of free time I have available has fallen dramatically over the past 2-3 years. |
Yea, so has mine since I have my own house. By the way I noticed your IMAP handling falls on its nose when the IMAP server writes utf8-responses WITH bom. ChatGPT says, on whether or not RFC 3501 says that the stream needs/can/mustn't have a Byte-Order-Mark:
So strictly speaking, while it was good for me to notice the "error" on my server, MailKit should also work if there is a BOM, which it currently doesn't (AFAIK - unless there are options and this is just the default). |
Can you get a protocol log and zip it up and send it to me? I need the BOMs to be in the log so that I can write up some unit tests that expose this issue and also so I can test that any fix I do works. If you can anonymize the content a bit, then feel free to do that - if not, I'll do it before adding it to the unit tests. What you might be able to do is create a new IMAP folder, add some test messages to it, then get a log of a FETCH request in that folder. I assume the BOMs are in each and every |
Also file a new bug report about that issue... |
I am implementing a JMAP-Server.
I should be able to test the JMAP-Server.
The POP3 Server i implemented, i tested with MailKit.
There is an existing libary (JMapNet), but it is not very pleasant to use.
Plus, if one were to write an email client with MailKit, it would be nice to have support for all email protocols.
The text was updated successfully, but these errors were encountered: