Cloudron Forum

@AartJansen are you settings the spam rules via the UI at https://docs.cloudron.io/email/#custom-spam-filtering-rules ? Do not edit the files on the server directly since they won't restart SA and related services. Otherwise, the filters look correct to me. Have you checked the Email headers?

@CRBear said in Mail server: IP address verification?:

Am I correct in understanding that the email server checks from which IP address a connection is established to send an email and by default, it verifies against the Spamhaus blacklist?

The mail server does not make any check for outbound email. The various checks you see in the Email Status tab are purely diagnostic. The idea is if one or more checks are failing there, most likely the email won't be delivered.

The Spamhaus is checked for inbound emails though. The DNSBL zone against which it checks is configurable at https://docs.cloudron.io/email/#dnsbl

Interesting.
I contacted the provider and told about the problem. They wanted screenshots. After another test all works fine again.
Thanks for your help!

That probably works for those apps yes, still a proper relay is recommended.

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.

@girish Thanks!!

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