What's coming in 10.1
-
We will be working on the following for 10.1:
- VPN protection - extend feature to select specific domains or paths. Also protect ports
- Mail: Split domain routing -https://git.cloudron.io/platform/box/-/work_items/908
- Mail: Distribution/group lists
- Add "external user" concept. Currently, when a user is added, they are given access to "everything". The idea here is to create the concept of a sandboxed user who has to be given access to apps explicitly despite apps allowing "all users" as the access control.
- Consider moving box code MySQL to sqlite. This will help us reduce a big dependency on the box side.
- anubis/hecapte integration
- New base image based on Ubuntu 26.04
- This will bump postgres to 17, dovecot among other things
- Investigate https://forum.cloudron.io/topic/15818/define-custom-well-known-entries-via-cloudronmanifest.json
-
G girish pinned this topic
-
We will be working on the following for 10.1:
- VPN protection - extend feature to select specific domains or paths. Also protect ports
- Mail: Split domain routing -https://git.cloudron.io/platform/box/-/work_items/908
- Mail: Distribution/group lists
- Add "external user" concept. Currently, when a user is added, they are given access to "everything". The idea here is to create the concept of a sandboxed user who has to be given access to apps explicitly despite apps allowing "all users" as the access control.
- Consider moving box code MySQL to sqlite. This will help us reduce a big dependency on the box side.
- anubis/hecapte integration
- New base image based on Ubuntu 26.04
- This will bump postgres to 17, dovecot among other things
- Investigate https://forum.cloudron.io/topic/15818/define-custom-well-known-entries-via-cloudronmanifest.json
-
We will be working on the following for 10.1:
- VPN protection - extend feature to select specific domains or paths. Also protect ports
- Mail: Split domain routing -https://git.cloudron.io/platform/box/-/work_items/908
- Mail: Distribution/group lists
- Add "external user" concept. Currently, when a user is added, they are given access to "everything". The idea here is to create the concept of a sandboxed user who has to be given access to apps explicitly despite apps allowing "all users" as the access control.
- Consider moving box code MySQL to sqlite. This will help us reduce a big dependency on the box side.
- anubis/hecapte integration
- New base image based on Ubuntu 26.04
- This will bump postgres to 17, dovecot among other things
- Investigate https://forum.cloudron.io/topic/15818/define-custom-well-known-entries-via-cloudronmanifest.json
anubis/hecapte integration
What!?
I'm interested, can we learn more about this and what will it look like? I'm currently hosting Anubis on a separate VPS which has costs on top of a VPS dedicated to my Cloudron server.
Managing Anubis separate from Cloudron is a pain and error prone. So I hope Cloudron can sort of fix this chore work / struggle

-
anubis/hecapte integration
What!?
I'm interested, can we learn more about this and what will it look like? I'm currently hosting Anubis on a separate VPS which has costs on top of a VPS dedicated to my Cloudron server.
Managing Anubis separate from Cloudron is a pain and error prone. So I hope Cloudron can sort of fix this chore work / struggle

-
@jdaviescoates It's not completely fleshed out yet. The options are - We can map Cloudron group to a mailing list. Another option is to have something like Google groups. Third option is something like a mailing list (the traditional one with unsubscribe links). This last one, I am not sure if anyone uses it anymore (outside of newsletters).
-
anubis/hecapte integration
What!?
I'm interested, can we learn more about this and what will it look like? I'm currently hosting Anubis on a separate VPS which has costs on top of a VPS dedicated to my Cloudron server.
Managing Anubis separate from Cloudron is a pain and error prone. So I hope Cloudron can sort of fix this chore work / struggle

@SansGuidon we are currently using Anubis for git.cloudron.io . It's made a massive difference. They have an unbranded version called Botstopper . Do you know of any other alternatives in this market?
-
G girish referenced this topic
-
@jdaviescoates It's not completely fleshed out yet. The options are - We can map Cloudron group to a mailing list. Another option is to have something like Google groups. Third option is something like a mailing list (the traditional one with unsubscribe links). This last one, I am not sure if anyone uses it anymore (outside of newsletters).
-
@jdaviescoates It's not completely fleshed out yet. The options are - We can map Cloudron group to a mailing list. Another option is to have something like Google groups. Third option is something like a mailing list (the traditional one with unsubscribe links). This last one, I am not sure if anyone uses it anymore (outside of newsletters).
-
@jdaviescoates It's not completely fleshed out yet. The options are - We can map Cloudron group to a mailing list. Another option is to have something like Google groups. Third option is something like a mailing list (the traditional one with unsubscribe links). This last one, I am not sure if anyone uses it anymore (outside of newsletters).
@girish Great to hear regarding a group mailing list feature. I have mentioned it quite a few times on here (again in what's coming in Cloudron 10 thread), and group mapping between cloudron groups and a mailing list would be super useful so people get added / removed automatically from the list as they get added / removed from a group.
Though I'm not sure what the difference is between that and a Google Group (i.e. between your option 1 and 2)?
-
@jdaviescoates It's not completely fleshed out yet. The options are - We can map Cloudron group to a mailing list. Another option is to have something like Google groups. Third option is something like a mailing list (the traditional one with unsubscribe links). This last one, I am not sure if anyone uses it anymore (outside of newsletters).
@jdaviescoates It's not completely fleshed out yet. The options are - We can map Cloudron group to a mailing list. Another option is to have something like Google groups. Third option is something like a mailing list (the traditional one with unsubscribe links). This last one, I am not sure if anyone uses it anymore (outside of newsletters).
Would it be greedy to maybe have the 3 options to choose from at the mailing list creation time?

I can easily see use cases for the 3.
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