You're getting a 301 because the JMAP endpoint is actually /jmap/ and
not /jmap (note the trailing '/'). I'm not sure why our implementation
requires this. That would be a question for Robert S.
This request works fine on my laptop using the current Cyrus code from Git:
curl --verbose
Set the 'debug' option in imapd.conf to 'on' and make sure that your
syslog config is logging 'local6' at the debug level.
On 05/22/2018 10:49 AM, Zhivko Vasilev wrote:
Hello Bron, Ken,
To clarify, that I do not use official FastMail server.
I've built Cyrus sever from
Hello Bron, Ken,
To clarify, that I do not use official FastMail server.
I've built Cyrus sever from https://github.com/cyrusimap/cyrus-imapd
With JMAP and HTTP/2 support enabled. Assume this is the closest
implementation to the JMAP RFC?
Seem the problem is with HTTP/2 settings frame. Client
I am just back home after a holiday. I will look into this sometime
today or tomorrow after I catch up on other items.
On 05/21/2018 01:47 PM, Zhivko Vasilev wrote:
Hello Everyone,
I hope you can help me.
I'm implementing a JMAP client and try to use Cyrus as reference server.
Send and
Hi,
I'm really sorry you've had such difficulty! We're using Cyrus with
http/1.1 at FastMail, so I don't have any direct experience with http/2.
We're also not using TLS directly in Cyrus, because we use an nginx
proxy in front which terminates the TLS connections.
You can enable regular
Hello Everyone,
I hope you can help me.
I'm implementing a JMAP client and try to use Cyrus as reference server.Send
and Receive via IMAP/SMTP work fine.
But when I try to connect via HTTP/2 , connection is reset by HTTP/2
reset stream command.
imapd.log file show only "starttls: TLSv1.2 with
