Cloudron Forum

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

@artd2019 Currently Cloudron does not offer (a documented) "whitelist" / "allow list" function, so there is no way to guarantee deliverability of an incoming email. There is a feature request for it already that I'd encourage you to upvote. Version 6.3 coming in the not too distant future is supposed to deliver on many of the email improvements users have been clamouring for (including myself). One thing you can do if you're not already is making sure to remove those emails from the Junk / Spam folder in order for SpamAssassin to unlearn the message as spam. Eventually after a sufficient number of them, it'll learn that those emails are not spam and will decrease the BAYES probability of it being spam. On a related topic, you may want to consider enhancing your SpamAssassin rules list from the defaults, specifically in your case the BAYES_## rules perhaps as I have offered previously in this forum.

@girish Cool, thank you kindly. It's just for incoming mail to those addresses for the time being, but I may add auto-responders from them as well at some point. For interest, I'm setting up all sorts of automations in EspoCRM, so tasks@domain.com will create a Task record and auto-reply to confirm it's been created. Doing similar for other data objects to.

What I would like to do is that if I try to login to a new WP installation with the cloudron super-administrator user, an administrator user will be automatically generated in WP with my Cloudron access data. And if I enter as a common Cloudron user in WP, a user will be generated with their Cloudron access data with the role that I configure in the ldap plugin. In this way, if I also changed my login details in Cloudron, it would also change on all WP sites. This would also be good with the rest of the applications. It would simplify things a lot. This is possible?

@girish I think that would be a good change. I also think I should have gone through the Troubleshooting document sooner : https://docs.cloudron.io/troubleshooting/ Thanks!

@subtlecourage said in Outbound SMTP not working on my External Relay: It says it should be coming from noreplay@domain.com, but instead it is coming from imanalias@domain.com Can you clarify what you mean by "it says"? Is there some error/warning somewhere? Also, I assume that you have put a custom domain in fastmail and also fastmail is able to relay mail as any email address i.e <anything>@domain.com ?

@d19dotca Sadly, they do match. I'm guessing it's something with my current setup that's acting funny. I'll ignore it for now since I plan on migrating either to the new Contabo server that I got or upgrading my current one at DO to Ubuntu 20.04. I just thought it was a wrong setting on my part. Thank you for looking into this and for sharing the custom spam rules! I know you've put a lot of time into that [image: 1620396102638-2443c4d7-ec13-4149-add3-28e1e7ad48ed-image.png]

@d19dotca Perhaps even a per-app option, as in "Check for spam sent from this app."

@girish said in Email into apps - DNS/MX/CNAME/TXT: You have to setup the CNAME/TXT for the root domain and not for my.example.com. You don't have to set it up for each app individually Thank you. That was my main issue.