Cloudron Forum

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

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.

@brutalbirdie ok, thank you - I've got the idea!

@girish Cloudron shows IP as present on Sorbs dnsbl blocklist, even though it isn't. [image: 1708555984912-2024-02-21_17-52-31.png] [image: 1708556022108-2024-02-21_17-53-31.png] Turns out I was too impatient, checks all green now.

@girish Wow that worked perfectly, thank you so much!

@nebulon Thanks for helping me work through this!

This got sorted out by @ntnsndr by contacting linode support. The VM had to be rebooted after linode unblocked port 25.

This is implemented in 7.3

@girish Hi there. Thanks for checking into this for me. I had a suspicion that the spam engine was verifying, since I did see those fields in the Spam results headers. However I think it's also useful to have Haraka add the headers as well. It would add very little overhead and will add additional detail that the spam header doesn't contain about the DKIM verification (such as which signature failed or passed, since an email can contain multiple). In regards to DMARC. I don't believe this would be risky at all if implemented in the following manner: No DMARC record found, take no action. DMARC found, DKIM/SPF aligned, take no action DMARC found, DKIM/SPF alignment fails, but p=none, take no action. DMARC found, DKIM/SPF alignment fails, but p=quarantine, move to spam folder DMARC found, DKIM/SPF alignment fails, p=reject, dev/null the mail. If you don't like the risk of this, push it to spam instead... or make it a cloudron option under Settings. Thanks for listening.

Problem solved by install all three instances into one and bought a license from cloudron. Now it works

@d19dotca thank you, I appreciate your quick response and correcting on the wrong topic! I did the search indeed, but I guess it was a wrong search query