Cloudron Forum

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

@girish said: @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. Thanks Girish, and yes a mailing list feature will be useful for some of my use case. I guess the point here is that it's a shame there isn't a way to use an external relay as a blanket replacement (i.e. covering all email features including forwarding) to the built-in SMTP server cause those services have added features to ensure reliable delivery (say when the server has a bad IP rep and gets regularly blocked notably by Microsoft stupid IP range blacklist approach).

Hello @webliska After our private chat and the suggestion to add IPv6 is this still an issue, or can I mark this topic as solved?

Yeah can confirm, and thanks for the help diagnosing. I wasn't given any advanced notice of the SMTP block, it was hidden in release notes somewhere. This is now unblocked.

@BrutalBirdie Ok fixed. The Cloudron did not even show me that. I have fixed the issue now.

@wmlutz said in Outbound SMTP (Transactional Email) Stopped Working - Invalid login: 535 Authentication failed: @jdaviescoates got it! It was the IP allowlist. Glad to be of assistance @wmlutz said in Outbound SMTP (Transactional Email) Stopped Working - Invalid login: 535 Authentication failed: mailgun's transactional email cost which is cents/mo. I don't think I've ever paid anything yet as I've not yet gone over the 1000 free messages a month or whatever it is...

@jdaviescoates I am interesting to figure out the workaround if I could just define the new SMRP port in the server configuration. Alternatively, Is it possible to implement some kind of port forwarding rule that can circumvent the port 25 block?

Ah the Cloudron is on version 7.5.2 which had a bug here. This is fixed with v8.0 already

Yes, you’re correct! If you’ve configured Mailgun as a relay on Cloudron, you should use port 587 with STARTTLS for secure email sending. If you're looking for alternatives, I recommend SMTPget and iDealSMTP. Both offer reliable services and can also be easily configured for your email needs.

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

@Lanhild I sent a reply to them again. They've finally opened the port.

I have the solution, VPS is blocked SMTP , now is open now is working

@JUVOJustin said in Send email with brevo relay: I have a sender configured for my-domain.com, while the server has cloudron01.my-domain.com . How can i solve this? Just to double check - on Cloudron, the relay system requires "domain" level relaying . Meaning, it requires a relay that can send with FROM address like <anything>@domain.com , as opposed to specific-address@domain.com . Can you confirm this? I think the easiest would be to allow changing the "From" domain in case a relay is used, since the sending domain will most likely be handled by the relay provider. You can change the From Email address of an app in the Email section of the app - https://docs.cloudron.io/apps/#mail-from-address . If you want my-domain.com , then add this in the Domains view. It will then appear in the dropdown of the Email domain selector as well. Then, Email -> my-domain.com -> Configure Outbound as brevo.

@q__nt_n The VPS blocks port outbound 25. You have to reach out to contabo again and tell them that you can't connect with the above command.

@jdaviescoates totally confusing for sure. Not cloudron's fault completely as TLS is just an update to SSL. The problem comes from old software I think where SSL (the verb) is still being used where TLS should be. Both are technically the same, one is just newer. Or at least that is what google would suggest lol. Either way, you can never have too many docs so an update to specifically call this out when working with SMTP ports would be useful.

@girish with help from vps and hosting it is been solved. thank you for replying here

What @d19dotca mentioned is correct, the next release will solve this issue and the current warning can be safely ignored for now.

@girish Thanks for a quick fix, It's now working

@girish Wow that worked perfectly, thank you so much!