1. Would it be a big feature request to add group name parsing into the mailing list input box? E.g. instead of (or in addition to) a list of email addresses it could take something like "group:foo" and then this would dynamically pull in the email addresses of all users in group foo as needed.

2. Is there a way that cloudron user group info could be pulled in @roundcube (or another mail system), so that instead of setting up forwarding rules that go to a list of emails it could go to "group:foo".

3. Is there a way that we could run a cron job (or similar) which could hackily create either of the above functionalities by generating and inserting the lists (rather than these lists being dynamically generated), with the downside that this would only ever be as up-to-date as the frequency with which the cron job runs.

@james said:

If you find such errors with applications provided by Cloudron, please always report them in the forum so just in case if there is something wrong with the application, we can have a look and find a solution.
Or at least, we can explain why it is behaving in a certain way.

Will do!

@da5nsy said:

but moved away from it because they couldn't get it to send emails reliably.

Just as a cautious note.
Freescout sends mails on a cron based task scheduler.
Same with getting mails from the configured mailbox.
This can be noticed as a failure to send or receive mails, but also enabled the feature of unsend mail because if you'd send right away there is no unsend mail in the mail protocol.

If you find such errors with applications provided by Cloudron, please always report them in the forum so just in case if there is something wrong with the application, we can have a look and find a solution.
Or at least, we can explain why it is behaving in a certain way.

@james said:

Correct me if I am wrong but, I have this feeling that you are using group owned mailboxes to solve a need for something that should be handled by a mailing / ticketing system like @freescout or @chatwoot.
Using such an application would resolve almost all the points you have brought up.

Hmm, that's an interesting point. You may well be right. I'll have a think about whether that might work for us. My initial reaction is that it wouldn't go down well because unless the email integration was simple and rock solid we'd need to ask users to get to know a new tool. And currently the work of updating email lists is a hidden admin chore, and so there's not much argument for changing things from the user perspective.

One of the groups was using Freescout until recently, but moved away from it because they couldn't get it to send emails reliably. They've now transitioned to using the kanban board feature of NextCloud (Deck) instead.

@da5nsy said:

As far as I can see the mailing list only takes email addresses as input. If it can take a group name as an input that would be amazing, but seems to be undocumented if so.

Since the group owns a mailbox e.g.: group_one@domain.tld you can add the mailbox in the mailing list.
But since you want to add all the users from a group and not the group owned mailbox, I can see what you are trying to do here and why it fails.

Correct me if I am wrong but, I have this feeling that you are using group owned mailboxes to solve a need for something that should be handled by a mailing / ticketing system like @freescout or @chatwoot.
Using such an application would resolve almost all the points you have brought up.

Thanks @james. We use @roundcube currently. I probably should've mentioned this, but I think I didn't because I have some intuition that this should be handled at the cloudron level, but perhaps this is an incorrect intuition.

I don't think we're particularly wedded to @roundcube.

Automating the manual parts would be API based, triggered in your workflow, no?

Train an agent?

I don't really know what this means.

What part of the platform would you have do such updates?

@robi I think what @murgero suggested is the way I'd imagined this would work - set up a mailing list where the email is automatically forwarded to all members of a group (members at time of receipt)

I found this same request while searching around: https://forum.cloudron.io/post/85331

@da5nsy said in Email group forwarding:

Currently, we need to go into the mailbox and manually set up the email forwarding.

"The mailbox" is the client I assume, so either @sogo, @roundcube, @snappymail or some other client like thunderbird.

If you are using @sogo you could use the sogo-tool to update user preferences like forwarding with automation.
But since you did not share what mail client you are using, this is just one example.

Train an agent?

What part of the platform would you have do such updates?