What's coming in Cloudron 6.3

[d19dotca]

@girish I agree that the spam filtering needs to be improved and in most cases it'd be fine to block spam to mailing lists (I basically wrote those feature requests after all haha), but that's part of the issue here too... in order for that new feature of not forwarding spam on to mailing lists to be effective and non-problematic (keyword there), we need those extra controls around identifying spam and setting all the different SpamAssassin options and such.

Until those extra controls arrive (it's understandable that'll take a while), the new feature can cause some unintended consequences for some since it didn't come with the ability to at least disallow spam filtering on a mailing list. There will certainly be cases where the spam filtering should be done on the recipients end, not Cloudron's end because at least if their spam filter catches it they can still see it in their junk box, but if the mailing list on Cloudron catches it then it's gone forever, so there's a bigger risk of Cloudron doing it for some types of accounts.

I would strongly encourage that ability to disallow spam filtering on mailing lists for those who need it at least until the better spam filtering is added to Cloudron along with all the other important mail features we've been clamouring for. Right now, that feature - while useful in probably 90-95% of cases - is also now a detriment to the remaining percentage without extra controls in place.

To be fair, maybe I'm misusing mailing lists though. I used them because it was much easier to manage for accounts which need to simply forward on to a different mailing address. Maybe I always should have been using mailboxes for that use-case? So I'll admit maybe part of the issue here is more the way I'm using it, but I still stand by the fact that the feature is a bit "half baked" without the ability to disallow spam filtering on them for sensitive accounts, and I hope that will be fixed until the time that the spam features are added down the road.

[girish]

@d19dotca I understand the impact of the change. Let me see if we have a few more hit this before making changes. It requires another full release cycle (a new mail container, new translations, new ui elements etc).

[d19dotca]

@girish Okay, thanks Girish for understanding. In the meantime I'm using the mailbox route again for the few addresses where I don't want to be doing spam filtering / preventing the recipient from receiving spam messages.

Relevant thread spin-off: https://forum.cloudron.io/topic/5277/spam-messages-forwarding-correctly-via-forwarding-sieve-rule/1

[nebulon]

@atridad said in What's coming in Cloudron 6.3:

FYI it looks like, at least in Firefox, the update button might be inside the <a> tag for the app itself? It always opens the app in a new tab in addition to taking me to the update page.

Actually I am seeing this issue now as well, not sure why it didn't happen when I tested this yesterday. Anyways I've pushed a fix for that now.

[luckow]

Something for the stats: 10 minutes for a Cloudron instance with 6 cores, 32 GB RAM, Ubuntu 18.04.2 LTS. 42 apps from Cloudron 6.2.8 to Cloudron 6.3.4

[subven]

@luckow exactly the same for me but with Ubuntu 20.04. No problems at all just a little waiting time. Watch the live logs to know what's going on during the upgrade.

[DanTheMan]

Problem for me after updating to v6.3.4 running on Ubuntu 18.04.4 LTS.
Matrix (Synapse server) seems to be running, but sending messages on Android and Windows not working anymore...

edit:
i moved this topic to https://forum.cloudron.io/topic/5291/problem-with-sending-and-receiving-message-s-android-windows

[nebulon]

@dantheman this maybe be better discussed in the matrix/synapse forum section as most likely this has nothing to do with the Cloudron update. If you have any further logs or error messages, please create a topic at https://forum.cloudron.io/category/50/matrix-synapse-element

[AmericanKulak]

This post is deleted!

[fbartels]

Hi,

a small ui glitch (at least it seems so to me) I just noticed in 6.3.4. When there is the update symbol for an app on the dashboard, clicking on it always brought you directly to the update screen in the past. In fact it still does, but additionally it now opens the app in a new tab.

[jdaviescoates]

@fbartels sounds similar/ the same as an issue @atridad had and I think @nebulon managed to track down

[girish]

@fbartels this is fixed but we have to make a new release.

[girish]

6.3 is now available to all. Please open a separate post in the appropriate forum section if you hit any issues.

[girish]

There will be a 6.3.6. It's going through the CI, it has many minor changes and also an important security fix (the last item)

[6.3.6]

• Fix broken reboot button
• app updated notification shown despite failure
• Update translation for sso login information
• Hide groups/tags/state filter in app listing for normal users
• filemanager: Ensure breadcrumbs and hash are correctly updated on folder navigation
• cloudron-setup: check if nginx/docker is already installed
• Use the addresses of all available interfaces for port 53 binding
• refresh config on appstore login
• password reset: check 2fa when enabled
• Fix crash due to wrong Spanish translation for invitation email

[mdreira]

@girish We did all the translation into Spanish. What was the problem and in what sentence?

[nebulon]

@mdreira there were just some syntax errors like extra whitespace for example:

<% = invite Link %>

a space between % and = as well as invite Link without the space
or

<%= inviteLink%>

and this also, where between inviteLink and % a whitespace was missing. Fixed version is now at https://translate.cloudron.io/translate/cloudron/dashboard/es/?offset=1&q=inviteLinkActionText&sort_by=-priority%2Cposition&checksum=

Most likely just autocorrect of your browser or copy and paste issue, so easy to fix once I found out. But would be nice if we could make weblate catch this somehow for us.

Ejs, which is the template engine we use here, is quite picky.

[mdreira]

@nebulon OK, I hope it is a specific error and not something general in the Spanish translation. We know that we have to copy exactly each code, without spaces.

As you say, it may be a copy paste error.

Thank you.

[girish]

We are rolling out 6.3.6.

[jdaviescoates]

@girish I've lost track, which of the features listed at the top of this thread are already done and included in 6.3.6? Could you perhaps update the OP to reflect current state of play? Many thanks!

[girish]

@jdaviescoates All the features listed on the top are part of 6.3.