What's coming in 6.0 (take 2)

[girish]

@avatar1024 Yes, that's the idea. The ownership will be dynamic.

That said, the initial outlook for the feature is not looking so good. There are two issues that need to be sorted out (suggestions/ideas welcome):

• Apps like SOGo show the "display name" of the user in the main UI. With a shared mailbox, it's not clear where this name should come from. With a single user, we give SOGo, the user's name. With multiple users, it's not clear what this should be.

• The authentication (from a user's point of view) is a bit confusing. Or maybe it's not, I would welcome some feedback here. You have to authenticate with the user's username/password but use the shared mailbox as the mailbox name. In some ways, this is the case already, when you use a different mailbox name with a different username.

[avatar1024]

@girish thanks for the reply.

Perhaps there are a few things I do not understand about the technical implementation of such a feature but I will still try to give my opinion. As you describe in the first post on this thread the idea is, rather that a "shared mailbox" as such, to have a single mailbox with multiple owners, so:

• for point 1) I suppose you mean that the name of the "owner" is fed to the app when the owner is assigned to the mailbox rather than when the user logs in? If so, would it possible to feed the name of the user that logs in into that (which will be recognised through its unique pair of credential: mailbox name + its unique password). If not then I'd say, as a first implementation of this feature (which could be improved later), then the name of the mailbox (as in the prefix before the @) should be fed to the app as the Display Name, when more than one owner are set to that mailbox

• for point 2, then yes, as you say the username (for login) should just remain the full mailbox email address (just that in the case of a shared one, one username will but associated to multiple passwords as valid login credentials).

[avatar1024]

@girish Or as I suggested in my previous post, if we could assign a "group" as the owner of a mailbox, then group name could be fed as the Display Name (for point 1) and you potentially use the group name for the login username (for point 2).

@avatar1024 said in What's coming in 6.0 (take 2):

...be possible to have the option to set a group as the owner...

[girish]

@avatar1024 said in What's coming in 6.0 (take 2):

@girish Or as I suggested in my previous post, if we could assign a "group" as the owner of a mailbox, then group name could be fed as the Display Name (for point 1) and you potentially use the group name for the login username (for point 2).

Making shared mailbox feature work only with groups is an excellent idea! I have to try this out and get back on how well this works.

[Lonkle]

@moocloud_matt said in What's coming in 6.0 (take 2):

@jimcavoli
i think that's possible with nginx too, the ldap backend for auth.
Custom Template for nginx config, will be the best i think, especially for performance optimization.

But this Kong proxy is interesting i will ask to my team, if they have use it.

Should we branch this topic off into its own thread about centralized authentication? It seems like an important aspect to discuss but this thread is about 6.0, which this couldn't be a part of, right? This would be further down the road? @girish @nebulon

[avatar1024]

@girish Glad it was at least a useful suggestion. Let's see if it works in practice

[girish]

@avatar1024 That worked out quite nicely. You can now select a group as owner of a mailbox. founders and sales-team are groups in the screenshot below.

[marcusquinn]

@girish Will each person's password work for IMAP/SMTP? (users in the group)

[girish]

@marcusquinn Yes, that's the idea. Each user can use their own password for sending/receiving with same mailbox.

[A Former User]

@girish Just a suggestion, but IMO it should have two dropdowns like the access section for apps. One for users and one for groups. Unsure of the implementation details but that just stood out to me.

[girish]

@atrilahiji Currently, one can only choose a user or a group. This was just the initial UI anyway for testing the backend. I think we probably need select box with groups like

[marcusquinn]

@girish makes sense. Be good as an input-select box, so you can partial-type what you're looking for in the case of long lists.

[girish]

@atrilahiji That was easy.

@marcusquinn Yes, it's searchable like the one in user's/group's view. The search only appears with more than 5 users.

[ei8fdb]

@girish said in What's coming in 6.0 (take 2):

There is a section overload in the app configure view We are looking to reducing the list of sections in the left pane. It's making things hard to find.

Hi @girish I'd like to help with this if you're interested.

[ei8fdb]

@girish said in What's coming in 6.0 (take 2):

We haven't decided on the naming yet, but maybe Volumes can be instead renamed to External Media or something, if it clarifies things. Open to other suggestions as well.

External media makes sense to me. Until the point Cloudron is able to backup these up (if that's something that will happen), I'd also have a tooltip saying 'External media is not included in Cloudron backups'.

[ei8fdb]

This post is deleted!

[girish]

@ei8fdb said in What's coming in 6.0 (take 2):

Hi @girish I'd like to help with this if you're interested.

Thanks for opening that gitlab issue! We won't do it for the current release atleast since there is massive UI surgery going on already for translations. Let's pick this one up after Cloudron 6 release in a separate thread.

[girish]

An update on this. The i18n is going along well, I think @nebulon is ~80% done. Once we are almost there, we will let you guys know in the translations thread. There is a large number of strings to be translated. We plan to ship Cloudron 6 with the code being translatable while the actual translations will be made available whenever they get ready.

Email container now has solr integration! While search is fast and I can search body (and maybe in future release attachments as well), there is something strange about how IMAP searches work. It seems it will search only under INBOX without the mail client having support for ESEARCH IMAP extension. I am also trying to figure how various mail clients behave here. Hopefully, should get sorted out this week.

Other features are done.

[jdaviescoates]

@girish said in What's coming in 6.0 (take 2):

An update on this. The i18n is going along well, I think @nebulon is ~80% done.

Excellent and important work!

Once we are almost there, we will let you guys know in the translations thread. There is a large number of strings to be translated. We plan to ship Cloudron 6 with the code being translatable while the actual translations will be made available whenever they get ready.

Good plan

Email container now has solr integration!

Amazing!

While search is fast and I can search body (and maybe in future release attachments as well),

Attachments too would be excellent!

there is something strange about how IMAP searches work. It seems it will search only under INBOX without the mail client having support for ESEARCH IMAP extension. I am also trying to figure how various mail clients behave here. Hopefully, should get sorted out this week.

I could be way off mark here, but I've noticed in the past that lots of IMAP providers seem to put Sent and other folders as effectively subfolders of the inbox. Perhaps something to do with that?

Other features are done.

You're underselling yourself (tbf, that's always a good look).

Personally I am very exciting about these "other features"!

• Volumes!
• Mailbox sharing!
• Faster Nextcloud and WordPress!
• Ubuntu 20.04 support! (Edit: tbh not particularly excited by this, because I'm more excited about having BBB on Cloudron and that isnt' even compatible with 18.04 yet!)

These are all fantastic new features!

[MooCloud_Matt]

@jdaviescoates said in What's coming in 6.0 (take 2):

Faster Nextcloud and WordPress!

We have some test image with Nginx + WP, that i have already shared with @girish, in the next few day we will work with him on some special feature to make the manifest compatible with OLS base image that we have pretty much ready, and later we will work on WP and NextCloud performance boost.

Probably next week, we will post some performance benchmarks of the new WP image, for both Nginx and OLS base image.