Cloudron Forum

So i found the error, it is because Hetzner close the port 25 by default on new dedicater server, so you just have to ask them to open it. Bisous les copains

@girish Thanks, that makes sense. Have setup external monitoring for port 25. Appreciate the speedy response as always.

@taowang note that your IP is actually leaked. If you follow the MX record of your domain, you will find your server IP in the DNS. I think this is what the Cloudflare doc is trying to tell you.

@dsp76 said in Easy way to handle mail forwarding without setting up accounts for each?: individual "mailing list" for each receiver Yes, exactly.

@girish great, thank you. I plan to move all my e-mail accounts to my cloudron server

@darsh_parsana /home/yellowtent/box/setup/start/cloudron-firewall.sh is on the root system, not inside any container. You can just edit the file directly via ssh.

@girish Would be amazing to have this feature yes

@girish Perfect, that solved it. Thanks!

Fixed in https://git.cloudron.io/cloudron/box/-/commit/ce426808889cb4c3dee8b64f6964311bce964cfa

@aqeelzakir-com said in SPF DNS record (TXT) did not match.: Relay error: Connect to port25check.cloudron.io timed out. Check if port 25 (outbound) is blocked Email Status is checked every 30 minutes. See the troubleshooting docs for more information. See https://docs.cloudron.io/email/#outbound-ports . Basically, your server is unable to send mail because outbound port 25 is blocked. You have to either get it unblocked by talking to your VPS provider or you can set up a relay. Expected: v=spf1 a:my.example.company include:_spf.google.com ~all Actual: v=spf1 include:_spf.google.com ~all If you are going to use a relay, the error above will go away automatically. Otherwise , you have to add a:my.example.company into the SPF record in the DNS.

@girish said in Improved global E-Mail signatures: Is the idea to extend our current global signature to use template/variables (from the authenticated user sending the mail)? Practically, yes that would be amazing! Variables I would like to be able to use: First Name Last Name Email Company (Could come from the cloudron branding name) Job Titles (This would require an addition to the user database Profile Photo or image url for static images like logos etc.

Just a quick note here. Route53 supports TLSA records now.

@girish Ah okay... Thanks.

For a start, does sending test mail work - https://docs.cloudron.io/email/#send-test-email ?

There are some hard coded rate limits - https://docs.cloudron.io/security/#rate-limits

@ccfu The quarantine plugin only dumps the messages into a directory which is not overly useful because there is no UI to manage the quarantine. because Cloudron does not provide a way to block or quarantine mails altogether based on central SPAMAssassin rules or sender addresses, as this can only be done using filters on individual mailboxes We have global SpamAssassin rules - https://docs.cloudron.io/email/#custom-spam-filtering-rules . I want to understand the use case better though. Is the issue here that spam is slipping through the SA filters?

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