Cypht - Lightweight open source webmail application written in PHP and JavaScript
-
I am currently testing different projects that implement the EWS protocol and came across cypht. I have created a community app to easily install it on cloudron: https://ca.cloudron.io/app/cypht
I am currently testing different projects that implement the EWS protocol and came across cypht. I have created a community app to easily install it on cloudron: https://ca.cloudron.io/app/cypht
Great!
From the instructions: „Log in with your full Cloudron email address and your mailbox password.“
Which one is the mailbox password? An app password for mail clients doesn’t work. -
I am currently testing different projects that implement the EWS protocol and came across cypht. I have created a community app to easily install it on cloudron: https://ca.cloudron.io/app/cypht
Great!
From the instructions: „Log in with your full Cloudron email address and your mailbox password.“
Which one is the mailbox password? An app password for mail clients doesn’t work. -
An app password for mail clients doesn’t work
Hmm.. I cannot reproduce this. For me the login works with my users password or an app password with the mail client scope.
@fbartels
When setting up the app password, expiry was set to immediately. I can’t explain why…
-
@fbartels
When setting up the app password, expiry was set to immediately. I can’t explain why…
-
Changelog: Enable the fancy login page and allow loading images from external sources by default.
I can't find where the option to enable external sources is enabled.
But I'd also prefer it to be how most clients seem to do it: each message having the option to enable images
-
Changelog: Enable the fancy login page and allow loading images from external sources by default.
I can't find where the option to enable external sources is enabled.
But I'd also prefer it to be how most clients seem to do it: each message having the option to enable images
@jdaviescoates This is something you can configure inside
/app/data/.env.Overall, Cypht is definitely built for power users and strictly prioritizes security over out-of-the-box convenience. For example, responses are plain text by default, the timezone defaults to UTC, and settings have to be explicitly saved by re-entering your user password (otherwise they revert on your next login). While they recently launched a very shiny new website, the underlying documentation is still a bit sparse.
Because of this "security first" design, Cypht intentionally blocks all external images by default. To change this behavior so that you at least get prompted to load them per email, you need to toggle the image loading setting.
For context, you can see how this restriction is explicitly handled in the source code here:
cypht-org/cypht - app.php lines 555-570Keep in mind that the code change linked above only alters the default behavior for fresh installations. If you upgraded from a previous version, your user profile will still carry over the old, stricter setting, so you'll want to manually update it in your configuration.
-
@jdaviescoates This is something you can configure inside
/app/data/.env.Overall, Cypht is definitely built for power users and strictly prioritizes security over out-of-the-box convenience. For example, responses are plain text by default, the timezone defaults to UTC, and settings have to be explicitly saved by re-entering your user password (otherwise they revert on your next login). While they recently launched a very shiny new website, the underlying documentation is still a bit sparse.
Because of this "security first" design, Cypht intentionally blocks all external images by default. To change this behavior so that you at least get prompted to load them per email, you need to toggle the image loading setting.
For context, you can see how this restriction is explicitly handled in the source code here:
cypht-org/cypht - app.php lines 555-570Keep in mind that the code change linked above only alters the default behavior for fresh installations. If you upgraded from a previous version, your user profile will still carry over the old, stricter setting, so you'll want to manually update it in your configuration.
@fbartels thanks, will give it a try.
-
Attention: I have made a few tweaks to my release pipeline and as a result of that the url of the CloudronVersions.json has changed. The shop listing has the updated url, but I don´t think there is an automated upgrade so the app needs to be removed and reinstalled.
-
@fbartels fyi, I am getting some Cypht error messages, which my impression started after the latest Community App version, but I may have ignored them from earlier.
cURL error: Failed to connect to localhost port 5232 after 0 ms: Couldn't connect to serverAny idea?
Not critical - app continues to work.My research :
When you run Cypht behind a web server (e.g., Nginx), the front‑end talks to a small daemon that talks to your actual IMAP servers. That daemon listens on port 5232, so the web‑UI can reach it via http://localhost:5232/ (or the equivalent Unix socket) without exposing the real IMAP ports to the public Internet. In short, port 5232 is the bridge between the Cypht web interface and the IMAP backend.
-
Yes, I have seen that as well. This comes from the cypht cardav client. Wenn that one is enabled it looks for a server at that address by default. So to get rid of the error either remove the carddav part from CYPHT_MODULES in .env or add the address of a carddav server.
PS: i have removed the module from the default configuration for the next release
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login