Cloudron Forum

Thanks for the report. I have fixed this with 1cd0140808ccaadc665e9f06b3910a8abbbdc167

@d43m0n1k_sek Should this post be deleted or should we answer this? The original post is still deleted. Should I restore it? edit: i restored it right now, but unclear if I should be deleting the entire topic.

Could you please check whether this applies to the PTR4 record as well? As I hadn’t configured it on the Cloudron – since I was using a relay – I experienced issues with incoming email delivery until I configured it. I then configured the PTR4 record and everything was solved. I know that PTR4 record is related only to outbound, but I want to figure out if there is some relationship on what happened. Thanks a lot

@avatar1024 said: Does that means one cannot use an external relay to replace the built in SMTP server if we use mailing lists (or the mailbox + forward implementation in Cloudron 10) - given most likely senders and mailing lists members with use random email providers? Yes, with a typical smart host / relay you cannot keep the original sender on list/forward delivery to Gmail/Posteo/etc. I want to mention that this is for the forwarding feature. Forwarding requires From address to be preserved. A mailing list behaves differently. It rewrites From/Reply-To etc and makes itself the originator of the email. This feature was never implemented in Cloudron. The forwarding feature was incorrectly labeled as mailing list and this misnaming is fixed in Cloudron 10. I guess we have to look into Distribution lists/mailing lists for the next releases, if you are interested in this. But the From address will change, not sure if it will work for your use case. It's usually meant for group@example.com or list@example.com style workflows.

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

@gerard thanks for testing. A fix for this is coming next release. The issue is fairly recent. SpamHaus made some policy change when requests come from IPv6 addresses.