Cloudron Forum

DMARC is about email security. Traditionally this was about inbound protection, where DMARC can be used. Though, DMARC is more about outbound email protection.

Sogo login issues Some users have reported issues with logging into SOGo even when using the Cloudron email after the update. This is most likely because you are using an older version of SOGo. The old SOGo app was deprecated ~6 months ago as part of the 2.3 release and is not supported. Please move to the new SOGo immediately. Install the latest version of the SOGo app (from the appstore) in another location/subdomain. You should see your email when logging in with email now. If you use calendar/contacts in old SOGo, you can migrate it to the new SOGo using the guide at https://cloudron.io/blog/2018-12-05-carddav-caldav-migration.html If everything is satisfactory, you can just uninstall the old SOGo.

This was a bug in our UI code. This is fixed in 3.5

@christiaan oh super cool! Never heard of JMAP before, that looks great.

@3246 There was a bug in the ldap code. See the fix in https://forum.cloudron.io/topic/2733/aliases-seem-misconfigured-in-sogo/4

I am trying to achieve unified inbox in SnappyMail and posted some questions here https://forum.cloudron.io/post/52418

@girish I seeeeee

A bit of thread necro, but I had the same problem. It appears that NodeBB is correctly configured, BUT in the Cloudron portal, by default, the "custom mailbox name" flag in the advanced app configuration settings is set to off. Thus, the email credentials correctly entered into NodeBB led to an account that, by default, was deactivated in Cloudron's mail server. For others who stumble here: From your Cloudron control panel, click the Configure tool (the pencil overlay over the app icon). In the Advanced tab of the pop-up, ensure that Custom Mailbox Name is checked, and that the name matches the name as configured in NodeBB's email control panel. By default, it's nodebb.app@. Problem solved, although whether it immediately resolved or whether it fixed when I rebooted Cloudron to install security updates about three seconds later, well ....

Just to conclude this thread. Mostly restarting the mail container will bring back the email server. As mentioned by @alexy this is done via docker restart mail

Is there any more information on this? For me all my clients I use, have the option to display folders as threaded or not, they also have then different sorting means depending on threaded or not.

In case, you find this post by search, there is doc on how to set this up here - https://cloudron.io/documentation/apps/nextcloud/#email

Yep! I am on a Lightsail instance and simply needed to open up port 25 for traffic. Thanks!