Cloudron Forum

@alexm said in Spamhouse blacklist: I am kind of struggle to understand is it the problem of OVH or the way Cloudron uses this Spamhous open relays? VPS providers have a block of IP addresses and they cycle these IP addresses across their customers as VMs keep getting created and destroyed. This means that your IP was used by someone else previously and maybe they sent a lot of spam (an unfortunately common situation). When this happens, spam watchlists like SpamHaus place the IP address in their email blocklist . In some cases, people will wholesale block the entire VPS provider IP address range since the VPS provider is not responding to spam appropriately. There is a lot of unknowns here since all this handling is not "transparent" - an email receiver can use all sorts of blocklist providers and unknown criteria to determine if your email is "spam" or not. They might even block emails by domain name etc. Your best bet for reliable email is to sign up and use a relay - https://docs.cloudron.io/email/#relay-outbound-mails . If you don't want to use a relay, you have to be "patient" to give your IP and domain a good reputation . You have to also get your IP/domain whitelisted from the various email block list providers. Most of the email blocklist providers have an online form that you can fill up to prove your reputation.

Thank you @laurent I'll try something like that.

@necrevistonnezr said in MXtoolbox: Which site? Sorry, I forgot to include the link. I have updated the post now. mxtoolbox

Setting up the sieve rule means I have to have the password and set all of that up. Using the "mailing list" settings means I don't have to do any of that, don't need to create an inbox, and it doesn't need to be owned by any accounts (and cloudron users with email admin / admin / superadmin can modify as needed). [image: 1702689032849-screen-shot-2023-12-15-at-5.08.26-pm-resized.png] So I guess I answered my own question I'll write it up. for people who ask in the future. "How do I set up email forwarding to external accounts without having to provision Cloudron accounts" == mailing list. @luckow thanks for the SoGo -- looks like that does take care of everything.

@cylon usually, you can request your VPS provider to open that port and they might if they trust to now spam Alternative is to setup a relay - https://docs.cloudron.io/email/#relay-outbound-mails

@foliovision it's in https://docs.cloudron.io/apps/#email See the note. But to be fair, it's hard to read through all the docs in detail.

OK, I finally worked on this AGAIN and remembered how messed up this is conceptually. username: groupname@domain password: (any one of the passwords of the people that have access) This is also makes Freescout work for me https://forum.cloudron.io/topic/12976/connection-could-not-be-established-with-host-mail-domain-com-connection-timed-out-110/43 A single "username" having multiple passwords is what messes me up every time.

Thank you, gentlemen! This worked. I hope that a summary of this explanation is included in the documentation.

I will mark this as solved but feel free to open a feature request post.

@eddowding this is a feature request I don't think you're the first to say it either.

If you want to receive email, you have unblock incoming port 25. If you just want to send emails, then use a relay as @jdaviescoates suggested.

You can always receive locally from apps.

@saikarthik said in Incoming email not being received: I had to re-add the entry for netlify load balancer in my DNS. Maybe next time lead with that. The use of „netlify load balancer“ seems to be some vital information while people are trying to guess-troubleshoot your DNS problems….

@mario Be interesting to see if the community can pick it up and maintain or fork.

@girish oh my! The memory is not what it used to be I guest there is not much demand for this feature

@nebulon the doc might need to be updated systemctl stop|start docker docker.socket postgresql mysql nginx for the services. rsync --archive /mnt/old_root/home/yellowtent/boxdata /mnt/data/cloudron-mail/ for copying the data (mv when fails produce a whole set of problems to be resolved and can't be resumed). and the following commands to verify: find /home/yellowtent/boxdata/ -type f -printf "." | wc -c find /mnt/data/cloudron-mail/boxdata/ -type f -printf "." | wc -c diff -r -q /home/yellowtent/boxdata /mnt/data/cloudron-mail/boxdata

@LoudLemur (Going by the topic subject), if the error is related to PTR record, then the solution is not correct. The PTR record is set by your VPS provider and not by your DNS provider PTR record goes by many names - Reverse DNS, rDNS, PTR. Unlike "forward" DNS which looks up something based on the domain name, a "reverse" DNS looks up based on the IP address. And who owns the IP address? The VPS provider. So, you have to change it there. This means that to fix PTR record issue, you have to fix this in SSDnodes and not in Porkbun or whatever name server you have. If SSDnodes, does not let you set PTR record, you have to ask them by raising a support ticket. More information at https://docs.cloudron.io/email/#ptr-record

@girish

You can also try to use some of the other DNSBL listed here - https://docs.cloudron.io/email/#dnsbl

@pschuele said in tine groupware: https://github.com/tine20/tine20 The correct repo is now https://github.com/tine-groupware/tine Their primary website (in German) is: https://www.tine-groupware.de/