<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with outbound]]></title><description><![CDATA[A list of topics that have been tagged with outbound]]></description><link>https://forum.cloudron.io/tags/outbound</link><generator>RSS for Node</generator><lastBuildDate>Wed, 09 Sep 2026 00:19:17 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/tags/outbound.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 17 Mar 2025 19:31:16 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Use floating IP address only for outbound Cloudron Docker container communication]]></title><description><![CDATA[@girish , is this perhaps something we can consider adding in one of the next updates? This would be greatly beneficial to be able to specify the IP address for outbound traffic in Cloudron (at least for the mail container but maybe all containers in one setting might be better for some people, not too sure what the best approach is).
I found a couple of other related topics so it seems like there is a need for this. I think my solution should still work but likely just needs to be adapted by Cloudron to be more built-in with a GUI to set the outbound traffic IP (or maybe just have it default to the IP set in the Network page by default as I suspect the DNS record IP would be the same IP outbound traffic would be desired).
Other related topics I found:

https://forum.cloudron.io/post/108717 (Haraka config for controlling outbound SMTP interface)
https://forum.cloudron.io/post/81114 (SMTP using wrong IP address on interface with multiple addresses) (admittedly this one is a post I made myself before, lol)

]]></description><link>https://forum.cloudron.io/topic/13458/use-floating-ip-address-only-for-outbound-cloudron-docker-container-communication</link><guid isPermaLink="true">https://forum.cloudron.io/topic/13458/use-floating-ip-address-only-for-outbound-cloudron-docker-container-communication</guid><dc:creator><![CDATA[d19dotca]]></dc:creator><pubDate>Mon, 17 Mar 2025 19:31:16 GMT</pubDate></item><item><title><![CDATA[How can I set up the custom SMTP port for relay]]></title><description><![CDATA[@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?
]]></description><link>https://forum.cloudron.io/topic/12698/how-can-i-set-up-the-custom-smtp-port-for-relay</link><guid isPermaLink="true">https://forum.cloudron.io/topic/12698/how-can-i-set-up-the-custom-smtp-port-for-relay</guid><dc:creator><![CDATA[ugacomp]]></dc:creator><pubDate>Fri, 25 Oct 2024 23:38:16 GMT</pubDate></item><item><title><![CDATA[Email healthcheck notification: "Relay error: Connect to smtp.live.com timed out"]]></title><description><![CDATA[Strange indeed, but I blocked the VPS Port 25.  Whilst blocked, I restarted Kuma and Tiny but to no avail.
All up and running now with 25 unblocked.
]]></description><link>https://forum.cloudron.io/topic/6405/email-healthcheck-notification-relay-error-connect-to-smtp-live-com-timed-out</link><guid isPermaLink="true">https://forum.cloudron.io/topic/6405/email-healthcheck-notification-relay-error-connect-to-smtp-live-com-timed-out</guid><dc:creator><![CDATA[RoundHouse1924]]></dc:creator><pubDate>Sun, 30 Jan 2022 05:59:56 GMT</pubDate></item><item><title><![CDATA[SMTP error with smtp.mail.yahoo.com, but I don't use this?]]></title><description><![CDATA[@jdaviescoates Yeah, removed it from our code for the next release. 5.5 should be out next week.
]]></description><link>https://forum.cloudron.io/topic/2955/smtp-error-with-smtp-mail-yahoo-com-but-i-don-t-use-this</link><guid isPermaLink="true">https://forum.cloudron.io/topic/2955/smtp-error-with-smtp-mail-yahoo-com-but-i-don-t-use-this</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Wed, 29 Jul 2020 06:53:38 GMT</pubDate></item></channel></rss>