What's coming in Cloudron 10
-
Appreciate that mail is the focus of 9.2, but maybe you can sneak in a minor enhancement to Notifications :
From :
'Grafana at grafana.appx.uk updated to package version 2.5.1'
To :
'UPDATED Grafana at grafana.appx.uk to package version 2.5.1'
Speeds user review of notifications -
@timconsidine I have to check which is better. But https://git.cloudron.io/platform/box/-/blob/master/dashboard/src/utils.js?ref_type=heads#L58 has a whole bunch of messages. They use the same styling right now but maybe it should be changed to "Installed ..." , "Backed up...", " Updated ..." etc
-
@timconsidine I have to check which is better. But https://git.cloudron.io/platform/box/-/blob/master/dashboard/src/utils.js?ref_type=heads#L58 has a whole bunch of messages. They use the same styling right now but maybe it should be changed to "Installed ..." , "Backed up...", " Updated ..." etc
@girish also color coding the initial wording would help e.g. update = green, backup failed = red, anything that requires attention = yellow
or..
break up messages into status groups:
RED (failed, errors, etc.)
- app x failed
- app y down
Yellow (user action required)
- app x requires manual update
- server reboot required
Green (all good messages)
- app M updated
-
@imc67 yes, that's part of the plan
@girish Would it be feasible to change the current methodology from text lists to database records for all block/allow-lists (mail, IP)? I manage the IP blocklist, via API, with around 90k rows and update it every hour with new and it takes about 2-3 minutes for each Cloudron-server to "handle" this. Better would be to have an API functionality with "list, add, remove"-commands.
-
As this is about email, I wonder if there's a way to have a chatmail relay. Kind of "batteries included" for the couldron email addresses or so. But I guess that's out of scope. Just came across that project again because it got some larger grant: https://www.sovereign.tech/tech/chatmail
c.f. https://forum.cloudron.io/topic/13952/chatmail -
As this is about email, I wonder if there's a way to have a chatmail relay. Kind of "batteries included" for the couldron email addresses or so. But I guess that's out of scope. Just came across that project again because it got some larger grant: https://www.sovereign.tech/tech/chatmail
c.f. https://forum.cloudron.io/topic/13952/chatmail -
Hello @mononym
From just a quick read of the description of the repository I would lean towards no.
Cloudron uses haraka as the underlying Mailserver which we also contribute to regularly and Chatmail is a full Mailserver which would be conflicting. -
would it -theoretically- be possible to and an alias service (like simplelogin.io or addy.io)?
@sponch I don't think so. Looks like cloudron is blocking Port 25 which is needed for receiving mail. Running into the same issues with my attempt at packaging stalwart
-
For external software (unsupported), you have to explicitly unblock ports - https://docs.cloudron.io/network/#whitelist-ports
-
The ability to delegate a subdomain out to an SMTP server hosted by an app has been discussed several times before. I'd quite like to package Mailman for Cloudron, but need a way of getting mail into Mailman itself. Mailman processes incoming mail via LMTP, but we could run an MTA on the app container if the app didn't support native SMTP. If we went that route I think it would be essential for Haraka to call forward to the SMTP server running in the container to avoid backscatter. I do run Mailman on my Cloudron instance for now in a completely unsupported manor and allow incoming SMTP via the Cloudron firewall as a custom port. This is working fine with Exim installed natively on the host, and I have a script to ensure the Nginx config for Mailman is in place. I really wouldn't recommend doing this yourself though and I'm also thinking of offloading the mailing lists to a third party provider at this point for various reasons.
-
We will be working on the following for Cloudron 10. mail server needs a bunch of housekeeping and fixes and will be the focus for this release.
Mail related:
- mail: allow cloudron email to be used as a mail relay. this will allow one cloudron to relay emails via another cloudron without having to disable mail from validation.
- mail: fix mail forwarding. there's been lots of bug reports on this feature. have to investigate the root cause
- mail: admin notes field for mailboxes and lists
- mail: housekeeping task. we want to move away from usage of ldap for auth entirely. many of the node ldap modules have become unmaintained
- mail: housekeeping task. the mail database is partly in box code and partly in mail server. have to move everything into mail server. this will help us implement backup/restore of mail nicely as well.
- mail: expose mailbox indexing and spam learning status in the UI
Non-mail related:
- Ubuntu 26.04 support
- Improved progress reporting - show percentage complete and elapsed/estimated time for backups and app installations
- Convert backup site creation dialog to a view
- Policy change: self updating ubuntu packages will be permitted i.e apt update and apt upgrade is allowed.
- Personal access tokens will be renamed to API tokens.
girish said:
Ubuntu 26.04 support
This is now implemented in master. Required very minimal changes, mostly to the installation script and also fixing up the docker version.
Ubuntu 26.04 is slowly appearing in many VPS providers (linode, vultr, upcloud) but not in DigitalOcean yet. So, haven't tested it extensively.
-
T Teiluj referenced this topic on
-
We will be working on the following for Cloudron 10. mail server needs a bunch of housekeeping and fixes and will be the focus for this release.
Mail related:
- mail: allow cloudron email to be used as a mail relay. this will allow one cloudron to relay emails via another cloudron without having to disable mail from validation.
- mail: fix mail forwarding. there's been lots of bug reports on this feature. have to investigate the root cause
- mail: admin notes field for mailboxes and lists
- mail: housekeeping task. we want to move away from usage of ldap for auth entirely. many of the node ldap modules have become unmaintained
- mail: housekeeping task. the mail database is partly in box code and partly in mail server. have to move everything into mail server. this will help us implement backup/restore of mail nicely as well.
- mail: expose mailbox indexing and spam learning status in the UI
Non-mail related:
- Ubuntu 26.04 support
- Improved progress reporting - show percentage complete and elapsed/estimated time for backups and app installations
- Convert backup site creation dialog to a view
- Policy change: self updating ubuntu packages will be permitted i.e apt update and apt upgrade is allowed.
- Personal access tokens will be renamed to API tokens.
-
We will be working on the following for Cloudron 10. mail server needs a bunch of housekeeping and fixes and will be the focus for this release.
Mail related:
- mail: allow cloudron email to be used as a mail relay. this will allow one cloudron to relay emails via another cloudron without having to disable mail from validation.
- mail: fix mail forwarding. there's been lots of bug reports on this feature. have to investigate the root cause
- mail: admin notes field for mailboxes and lists
- mail: housekeeping task. we want to move away from usage of ldap for auth entirely. many of the node ldap modules have become unmaintained
- mail: housekeeping task. the mail database is partly in box code and partly in mail server. have to move everything into mail server. this will help us implement backup/restore of mail nicely as well.
- mail: expose mailbox indexing and spam learning status in the UI
Non-mail related:
- Ubuntu 26.04 support
- Improved progress reporting - show percentage complete and elapsed/estimated time for backups and app installations
- Convert backup site creation dialog to a view
- Policy change: self updating ubuntu packages will be permitted i.e apt update and apt upgrade is allowed.
- Personal access tokens will be renamed to API tokens.
girish said:
mail: housekeeping task. we want to move away from usage of ldap for auth entirely. many of the node ldap modules have become unmaintained
mail: housekeeping task. the mail database is partly in box code and partly in mail server. have to move everything into mail server. this will help us implement backup/restore of mail nicely as well.Both done now
Got rid of LDAP entirely from the mail server.
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


