The server is reachable but is blocking cross-origin requests. Check your JMAP server’s CORS settings and allow this domain.
what do i have to set in stalwart 0.16.6 to solve this problem?
on
You need to enable the usePermissiveCors setting on the HTTP server. This tells Stalwart to return the appropriate CORS headers that allow browsers (like the one running Bulwark) to make cross-origin JMAP requests.
How to enable it:
In the Stalwart WebUI, go to Settings › Network › HTTP › Security and set usePermissiveCors to true.
Security note: This is the broadest possible CORS setting – it allows requests from any origin. Make sure all sensitive endpoints remain protected by proper authentication and authorization, as browsers will no longer restrict cross-origin access.
More details in the docs: HTTP Security - Permissive CORS Policy
This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong.
This was not the solution. it doesn’t work.!
Please help.
Getting the two to work together can be a little fussy, but you’ll definitely need to set the CORS policy in Stalwart - have you checked that? Could you post a screenshot of your settings? Here’s what a successful set-up looks like;
Once you’ve flipped that button, you have to hit “save” at the bottom of the page. Then Stalwart is ready for Bulwark. If you’re still not connecting to the JMAP server, look at your logs and maybe debug your Bulwark settings.
Thank you, I have that setting enabled.
I found the solution now, i had a wrong http listener for port 8080.
a related question: how can I set up the default language for bulwark?
i tried to find the option somewhere in the bulwark admin panel, but i found nothing. Can i influence this with a stalwart setting perhaps? if yes, where can i find the setting?
Well, I dunno about Bulwark - you’ll have to ask them directly.
Stalwart changes language settings via “locales”. Locales are a more low-level setting because they are responsible for which character set you use, e.g. Cyrillic, Latin, POSIX, et. al.
You can configure locales per user in the account settings. I haven’t tested this much however and I’d be careful as sometimes different webmail clients can choke on locale settings that are unexpected.
Could you elaborate on your solution? I am getting the same error between Bulwark and Stalwart. I have Permissive CORS policy enabled. I am proxying my https://mail.exam.ple through Pangolin/Traefik to Stalwart against an http listener on port 8080.
What did you change to make this work for you?
I have apache2, not sure if it helps you when I post it here.
Any solution on your side? I have the same issue than you. I have set on the CORS permissive parameter and added bypass rule to the public ressource in pangolin.
I think that could be linked to something related to headers
Ok question sent too fast. I had to reload the stalwart configuration from the WebUI and I was able to login
If you need it, to summarize to get access to Bulwark using Stawart throught Pangolin:
When all is done, go in Stalwart > Management > Actions and click on Server Settings in the Reload section
