Had this happen as well. Thanks for fixing in future versions.

I have opened https://git.cloudron.io/cloudron/box/issues/622

Fixed it for next release.

@girish Thankyou, will give it a go.

@subven yes, the file exists. These are the permissions: drwxr-xr-x 2 yellowtent yellowtent 4096 May 10 10:33 ./ drwxr-xr-x 4 yellowtent yellowtent 4096 May 10 11:27 ../ -rw------- 1 yellowtent yellowtent 887 May 10 10:33 private -rw-r--r-- 1 yellowtent yellowtent 272 May 10 10:33 public -rw-r--r-- 1 yellowtent yellowtent 8 May 10 10:33 selector The DKIM-signing works after a chmod 777 private but I don't think that 's a sustainable solution. The 'renew all certs'-button does not seem te renew my certificates. My DNS-setup is 'wildcard', so I don't think it 's possible to re-setup dns? I just added an extra domain (with cloudron 4.0.3) and it results in the same permissions: drwxr-xr-x 2 yellowtent yellowtent 4096 May 17 06:54 ./ drwxr-xr-x 5 yellowtent yellowtent 4096 May 17 06:54 ../ -rw------- 1 yellowtent yellowtent 887 May 17 06:54 private -rw-r--r-- 1 yellowtent yellowtent 272 May 17 06:54 public -rw-r--r-- 1 yellowtent yellowtent 8 May 17 06:54 selector

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

Hi @girish. Yes, I confirm that everything's green. It works after a permission change on the /home/yellowtent/boxdata/mail/dkim/mydomain.com (600 to 644) With this change, I don't have no more the DKIM error. Now, I'm trying to setup calendar with Lightning. Everything's fine but the invitations sent by Lightning; the organizer mail value is always (null) Here is the Vcalendar event : ORGANIZER;RSVP=TRUE;ROLE=CHAIR;PARTSTAT=ACCEPTED:mailto:(null) I can't find any clue in the logs

@nebulon ok thanks for the reply. I didn't think so but wanted to check. Would be cool if somehow the aliases you added in cloudron admin area show up as a from address automatically in sogo. Thanks again.

thanks @girish and @msbt for chiming in here. I cant see rainloop settings that support a single inbox over multi domains (but i do see how you can setup two or more accounts and simply switch between accounts) the feature in G SUITE i am aiming to reproduce here, is to have one inbox, that multiple domains are associated with, so emails to any of the domains end up in the single inbox, and upon reply, i can choose which email to reply with. In G Suite you add domains to the domain list, then under the user you can setup an email alias that span across any domain in your domain list. this is why i originly figured this was a feature that maybe cloudron would offer, but i see your point that maybe this is app level feature (just not seeing that feature in either rainloop or sogo, will try nextcloud now)

@nebulon ok thanks for the info, appreciate it.

@jagan is this still an issue for you? Did you confirm that email sending from Cloudron works generally?

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.

Also, it is safe to disable encryption since the communication is internal to the VM.

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