Cloudron Forum

@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.

@m-si Sweet! Thanks a lot for sharing this workaround. It works perfectly and helps me to cover the time until true MTA-STS + DANE support from Cloudron. E-Mail reputation is really crucial these days.

Just one remark for other readers: If you are doing this for the first time, you should probably start with mode: testing.
Once you have successfully established MTA-STS (no errors), you should change to "mode: enforce" and increase the max_age value. Many senders expect it to be at least several weeks.

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!

@jdaviescoates right, unfortunately, it was not prioritized/implemented.

@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 😉

Sorry to resurrect an old thread. Was recently struggling with migrating (using imapsync) an Office365 account, and it seems to do with Microsoft deprecating Basic Auth method for authentication so there's a whole set of hoops to run through to publish an application in Microsft Azure and get an OAuth access token and what-not to use in the imapsync. It's an over-complicated process.

The workaround I chose since it was thankfully only one mailbox was to setup my local Apple Mail.app with the Exchange account, and waited for everything to download locally. I then used it to export the the mailbox folders which it only does in mbox format. This is where our use-cases align I believe as I was wondering how to import this since Cloudron's mail server uses maildir instead of mbox.

I then learned that Roundcube imports mbox data directly, so simply imported through the app interface and it worked well. Just thought I'd add this as an alternative solution for anyone who comes across this in the future. Turns out Microsoft made the whole imapsync process nearly impossible to use due to their deprecation of Basic Auth just recently in October 2022.

@luckow Thanks! didn't know SoGo can too, updated my post! 🙏

It would be an interesting feature to have the mailserver for a domain be able to recognize that a mailbox it is receiving for is elsewhere and redirects the connection there.

This would be at a higher level than where forwarding happens.

Just like when one moves IRL and tells the Post Office the new address.

Similar to 301/302 HTTP redirects.