What's coming in Cloudron 10

[humpty]

@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]

@girish said:

@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.

[humpty]

@girish I was able to forward mail from Gmail to my CR mail server/mailboxes. Was this support added in 9.1.7 or something?

[mononym]

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

[james]

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.

[robi]

@james @mononym unless chatmail can delegate and use Haraka instead?

[sponch]

would it -theoretically- be possible to and an alias service (like simplelogin.io or addy.io)?

[andreasdueren]

@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

[joseph]

For external software (unsupported), you have to explicitly unblock ports - https://docs.cloudron.io/network/#whitelist-ports

[andreasdueren]

@Joseph No, the problem here is that to receive mail, I need to be able to route Port 25 to the app. But I think it's always reserved by the internal mail server?

[joseph]

@andreasdueren you are right, it is a reserved port .

[adhodgson]

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.

[girish]

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.

[sponch]

So new mail features are coming in 10 or 9.2 - I'm a bit confused

[nebulon]

Initially we thought of 9.2 having those but since we wanted to release some things earlier, 9.2 was released with different features, so this thread shifted essentially to v10 now

[girish]

girish said:

mail: admin notes field for mailboxes and lists

This is implemented. There is a notes field for each mailbox and list.

[girish]

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.

[sponch]

any ETA?

[girish]

@sponch still a long way out since we are just implementing the features. I can provide a date, when we are at least done implementing them But we are moving very quickly

[crazybrad]

@girish Since V10 is focused on email, wondering if this feature would be possible: Spam Assassin rules by domain.

Due to AI-driven email spam, I need to manually add about 10 domains to the global block list almost on a daily basis . It's a battle I can't win and huge waste of time.

I'd like to change Spam Assassin rules to deposit all email in the spam folder, except for known contacts and vendors I allow through. But this needs to be on a per domain basis
as every domain would have a different "allow list". It is also possible that some domains would not want this "spam as default" behavior.

Does Cloudron support something like this already, or could this capability be added to the V10 email upgrade the team is working on?