@fbartels Much appreciated. After your explanation (and watching what is going on with SoGo workers and how many workers are needed), my next Cloudron will not use SoGo EAS simply because it consumes too many resources. For a limited set of users (< 30), I can afford the extra resources. But if I was providing email for 200+ users, I think Sogo EAS would crash and burn.

I also hadn't thought about the consequences of having 5 email accounts on 3 different devices. While all of them may not be "active" at the same time, the load is much greater than the number of email accounts.

Added to docs, thanks @True and @BrutalBirdie

@nebulon Could the groups ACL currently built into Cloudron be extended into SoGo calendar? It is possible to limit apps to certain groups. Can multiple Sogo instances be added so that Group X has access to its own Sogo and Group Y has access to its own Sogo and the address book while global is confined to just the group?

@AartJansen said in vacation message not ending:

Does that bottom row of "Enable autoreply on these days" overwrite the schedule ?

Good question, your guess is as good as mine 🙂

@fbartels Thank you very much! It’s great to understand why things don’t work as expected!

I would have switched dns provider a long time ago if it wasn’t for the fact that they are basically the only provider that offers domains from my country (and for a reasonable price).

I’ll try autodiscover and if that doesn’t work, I’ll try a secondary domain name for my email.

https://docs.cloudron.io/apps/sogo/#disabling-activesync

An Microsoft 365 Outlook can still be the old Outlook. Its just that Microsoft prefers selling it as a subscription instead of a one time fee.

This page has screenshots of the new Outlook: https://www.microsoft.com/en-ca/microsoft-365/outlook/email-and-calendar-software-microsoft-outlook

While the old one looks more like this:

image.png

But as I said in https://forum.cloudron.io/post/86789 Outlook with ActiveSync does not really make for happy end users. ActiveSync is just not a protocol for desktop applications.

https://www.mail-archive.com/users%40sogo.nu/msg33275.html is the thread for future viewers.

@girish Thank you for exploring this. The more apps we can connect to Cloudron OIDC the better!

@nebulon Makes sense, just wanted to make sure 🙂

MySQL container being down is the issue. Try restarting it or check the logs as to why it's down.

Looks like SOGoTimeZone has to be set in sogo.conf per https://www.sogo.nu/files/docs/SOGoInstallationGuide.html#_general_preferences

@laurent ha ha, scrolling in context menu is not the best UI, agreed.

Are there any errors in the browser console or the app logs when this happens? Something so we can hopefully work with to better diagnose the issue.

Time flies 🙂 I can't believe this year is (finally) coming to a close. Glad you find my post useful.

@RokeJulianLockha I think the mailing list is the only channel. The mailing list archive is here - https://www.mail-archive.com/users%40sogo.nu/maillist.html . It seems active, if you can figure how to mail it 🙂

@True said in SOGo - Modifiable shared calendar doesn't update:

Recently I am looking to create a shared calendar resource in SOGo. The idea would be that customers (or 3rd parties who don't possess cloudron mailbox in my infra) could get authenticated access and create calendar events over outlook or some other mail client via .ics or some other method.

For 3rd parties this may not be possible, as SOGo on Cloudron only works with authenticated users for a Cloudron local mailbox.

SOLVED:
I wasn't using my Cloudron instance as mail server. I have some ISP issues with inbound email so I try to avoid cloudron mailbox for now. The good news is that for the SoGO login doesn't need a fully working mailbox just an existing one. The domain mentioned in the manual is the dns domain(!!)

Anyways the steps which fixed the issue:

For this example let's assume your domain is hostedservice.page and we will create a mailbox james@hostedservice.page

Go to Cloudron Dashboard Under profile select "Email" Edit the domain of your choice which in our case is hostedservice.page, where you want to host the mailbox. You'll find it under Domains → Domain → Actions → Edit Under Email configuration hostedservice.page you'll find Mailboxes Click on Add and select a name like "james" and assign a cloudron "owner" as the Cloudron dashboard user account who will own the mailbox. Click on the created mailbox and you will see something like james@hostedservice.page Go back to SoGO and use the mailbox username james@hostedservice.page and the cloudron user password You are in. That's all.

Thanks for the help!

Yes, I think so, too. For me the problem is solved. Maybe this thread will help someone with the same issue later to understand more 🙂