Cloudron Forum

Closed due to inactivity

@qwinter Yep, I understood that. But, what DNS settings in the end worked?

@TechoutDev To debug, open the mail logs window. Mail -> Logs button in top right. And then there is another logs button inside it. Keep that browser window open. Then, use the send test mail button - https://docs.cloudron.io/email/#send-test-email . Can you please post what's in the logs?

@scooke Hi, sorry for the delay. Yeah, @girish was able to solve the problem, which was not a technical one, as usually is the case with these things, heh. The email she uses is an alias, and not <username>@<mydomain>, and she hadn't used it in a while. We're both pretty sure she used to be able to log in with either username only (no '@domain'), or with her aliased email <alias>@<mydomain>, but it seems we're both wrong on this. So I tried to log into her email with <username>@<mydomain> and, lo and behold, it worked. She doesn't use this email at all, so I'm talking to her and seeing if we change her username, since there's only a few apps and email will be the most important one from now on. Thanks everyone for the help!

@msbt It's intentional that only superadmins can see it. It won't be good for privacy if an admin could see all the emails being sent. It's OK for superadmins to see this because it's assumed they have SSH access. I have added a note in https://docs.cloudron.io/email/#event-log and fixed the UI to hide the button for non-superadmins.

@jdaviescoates Yes, cron not working is a symptom of docker not working (stuck in configuring)

@savity Indeed, there is no event log entry, I will add it.

@7dowWilkes sorry for answering that late. You need to have app that serves the file at the expected URL. You need to set up surfer app (this is the webserver you are looking for) at mta-sts.YOURDOMAIN.TLD (YOURDOMAIN= is your domain... TLD=Top Level Domain e.g. .com, .org...) inside surfer app you need to create .well-known folder inside folder public and then place the mta-sts file as described earlier there... I hope this clarifies it for you ...and yes it is still working. @james I think it would be awesome to somehow implement it into cloudron for the ease of use mail setup. As long as it is not implemented maybe a notice in the mail section of cloudron might work.

Oh cool thanks for pointing that out, I hadn't noticed before. I guess the downsides don't really apply to me right now, but I'm not sure I'd want to enable arbitrary masquerading if there were a bunch of other people on this cloudron. I still think it's reasonable for users to be able to send with a subaddress of any of their aliases, without opening the floodgates and allowing them to send from any address at all.

@WiseMetalhead yep, that's exactly what I was looking for, thanks! I thought I typically keep up with recent posts on the forums but somehow missed that one. Looks like all is well and will be resolved with the next Cloudron release!

Strange indeed, but I blocked the VPS Port 25. Whilst blocked, I restarted Kuma and Tiny but to no avail. All up and running now with 25 unblocked.

I will move this to Feature request then.

@mehdi good catch, will fix!

@jdaviescoates ah yes then this most likely was the issue with the unbound anchor file. See https://docs.cloudron.io/troubleshooting/#recovery-after-disk-full

@girish Unfortunately, I don't know how to find out... but I'll keep an eye on it and update when I find out! Thanks!

It's going well so far in my testing. Updated about 6 domains with the newer DKIM selector today. It'd definitely be nice to have this configurable though in the UI so we can change it in one sweep to a new DKIM selector of our choosing.

@girish Thanks for a quick fix, It's now working

We didn't get to the bottom of this but the user solved it by moving to sendgrid.

@girish thanks for the support. Some mails arrive in spam. I will check DKIM, SPF, DMARC, PTR records. but that's my problem