Cloudron Forum

Hooray! Thank you, @girish !

@warg Haraka is not as widely used as Postfix but it is also hardly a niche product and has been around since 2011. If anything it is down to preference. Cloudron chose it because it is lightweight and efficient and presumably because it best fit their architecture. The IMAP server in Cloudron is Dovecot, which is also used in Plesk. What are your concerns? Yes, the best thing to do is just give it a go and see if it fits your needs.

@userino yeah, it's that way because IMAP/SMTP have no concept of sessions. This means that you might have to repeatedly enter 2FA token which would in turn make using mails clients quite unusable. I recommend generating an app password for Email (what I use personally) and using that as a "throwaway" password. It will work only for Email an won't let you login to other apps.

@girish can you just set them much lower like 20s?

@girish I tried it just with other Browser, it works. That was an stored browser data issue, sorry and thank you. Lukas

@girish oh, ok then sorry for this!

@girish Thanks for the clarification. I guess we can close this thread, since the solution will be troubleshooting the original unbound / DNS issue on my server (https://forum.cloudron.io/topic/8864/dns-resolving-problem). I have just replied to your e-mail. Right now, numerous DNS queries are failing again, which leads to many missing posts or media on my public Mastodon instance.

@girish ( ._.) I got servers with 100+ Mailboxes a global bcc all would be... better Also Cloudron is used by companies in Germany and they have to abide to the law of archiving business communication https://www.gesetze-im-internet.de/hgb/__257.html and a global BCC option would be very nice.

I figured out my issue. Turns out that even though I read the documentation I made one critical mistake right at the beginning. I had to create my email accounts and the addresses I wanted to work in Cloudron first. Then Install the Snappy mail client and set up the email accounts there second. Once I deleted the Snappy mail client and reinstalled it everything worked. I'm not sure how but this topic can be marked as resolved.

@Kubernetes lol, thanks, thats both useful, and a laugh at myself, at my new level of stupidity unlocked.

@opensourced yes, should be out next week along with 7.4

@Kubernetes that's correct.

@JOduMonT good idea. I think it would be nice if we had a "migrate domain" which "moves" everything - dashboard, MAIL FROM, mailboxes etc. All these are available individually but not as a single operation. Can you make a feature request?

have you stress test your mail server .. sending more emails to see its limits ( in 1 gb ram small vps) ?

@msbt said in Can't manage existing email address since v7.3.4 update: for debugging, lmk if needed Not needed. Just takes a really long time to fetch for domains with bigger maildata.

@girish thanks! It's working fine now. This is the reason why I love cloudroun

This is fixed for next release with https://git.cloudron.io/cloudron/box/-/commit/3477cf474f32a51c62aef65015e615db62bca4f7 For the other feature request about domains, please make a separate thread there, but I can already say that Cloudron is still designed to work for a setup of one Cloudron per organization and not many maintaining isolated organizations on one Cloudron. This will add all kinds of complexities for the 99% use-cases Cloudron is currently used for.

@YoMaCloud thank you for the correction / update, useful to know.

I have submitted a PR upstream as a temporary fix - https://github.com/haraka/Haraka/pull/3104

@girish Thanks for getting back. Yea I was able to sort this out. It appears it might have been related to the route I had established for internet traffic. Strange that it would only effect gmail, but this new route is simpler, and testing shows all mails being delivered without issue.