<?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[Subscriber sign up mail issue for Ghost 3.0 instances on a sub domain]]></title><description><![CDATA[<p dir="auto">Seems to be an issue with a Ghost 3.0 instance sending subscriber magic link emails to users when signing up on a Ghost instance on a Cloudron sub domain.  Ghost assumes the domain it should be sending from should include the sub domain e.g. <a href="mailto:noreply@demo.mydomain.com" target="_blank" rel="noopener noreferrer nofollow ugc">noreply@demo.mydomain.com</a>, when the blog is at <a href="https://demo.mydomain.com" target="_blank" rel="noopener noreferrer nofollow ugc">https://demo.mydomain.com</a>.</p>
<p dir="auto">The sign up form returns "Please enter a valid email address!" but the logs show the following:</p>
<p dir="auto">"Failed to send email. Reason: Mail from command failed - 550 Authenticated user <a href="mailto:demo.app@mydomain.com" target="_blank" rel="noopener noreferrer nofollow ugc">demo.app@mydomain.com</a> cannot send mail as <a href="mailto:noreply@demo.mydomain.com" target="_blank" rel="noopener noreferrer nofollow ugc">noreply@demo.mydomain.com</a>."</p>
<p dir="auto">Having Email Masquerading enabled for <a href="http://mydomain.com" target="_blank" rel="noopener noreferrer nofollow ugc">mydomain.com</a> doesn't make any difference.  Sending a test email from the Ghost UI works fine as the email comes from <a href="mailto:demo.app@mydomain.com" target="_blank" rel="noopener noreferrer nofollow ugc">demo.app@mydomain.com</a> and I'm guessing doesn't encounter the authentication error.</p>
<p dir="auto">The Ghost UI doesn't offer the ability to alter the domain part of the sending email address.  Is this something that can be modified within the Ghost package for updating / new installations?  Also what would be the best temporary solution?</p>
]]></description><link>https://forum.cloudron.io/topic/1990/subscriber-sign-up-mail-issue-for-ghost-3-0-instances-on-a-sub-domain</link><generator>RSS for Node</generator><lastBuildDate>Thu, 16 Apr 2026 14:37:03 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/1990.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 13 Nov 2019 10:04:17 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Subscriber sign up mail issue for Ghost 3.0 instances on a sub domain on Fri, 24 Jul 2020 22:15:01 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/girish" aria-label="Profile: girish">@<bdi>girish</bdi></a> Just tested this workaround and it works!</p>
<p dir="auto">(I set DNS to Manual to save creating another API key and DNS records since the sub-domain is only for development).</p>
<p dir="auto">There seems to be some typos in the instructions above though between <code>demo.domain.com</code> and <code>domain.com</code> that might be worth fixing to help anyone else searching for a solution on the same too.</p>
]]></description><link>https://forum.cloudron.io/post/11401</link><guid isPermaLink="true">https://forum.cloudron.io/post/11401</guid><dc:creator><![CDATA[marcusquinn]]></dc:creator><pubDate>Fri, 24 Jul 2020 22:15:01 GMT</pubDate></item><item><title><![CDATA[Reply to Subscriber sign up mail issue for Ghost 3.0 instances on a sub domain on Thu, 30 Apr 2020 17:08:40 GMT]]></title><description><![CDATA[<p dir="auto">A late note but in recent releases you can now have the email set to a different domain from where ghost is hosted.</p>
]]></description><link>https://forum.cloudron.io/post/7904</link><guid isPermaLink="true">https://forum.cloudron.io/post/7904</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Thu, 30 Apr 2020 17:08:40 GMT</pubDate></item><item><title><![CDATA[Reply to Subscriber sign up mail issue for Ghost 3.0 instances on a sub domain on Thu, 14 Nov 2019 04:12:16 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/tkd" aria-label="Profile: tkd">@<bdi>tkd</bdi></a> Sorry. forgot to give the workaround. I have given explanation of the workaround below.</p>
<p dir="auto">Workaround:</p>
<ul>
<li>Add a Domain called <code>demo.mydomain.com</code> in the Cloudron Domains view. This can have the same DNS settings as <code>mydomain.com</code>.</li>
<li>Now go to Email view and enable masquerading for <code>demo.mydomain.com</code>.</li>
<li>Then change the domain of your existing app installed at <code>demo.mydomain.com</code> i.e in configure UI -&gt; Location and then in the drop down select <code>demo.mydomain.com</code> and leave the location field empty. Effectively, the app remains at <code>demo.mydomain.com</code> but is using the settings of the Cloudron's <code>demo.mydomain.com</code></li>
</ul>
<p dir="auto">Explanation:<br />
On Cloudron, we don't allow apps to send email with arbitrary addresses across domains. So, if an app has to send emails as <a href="http://demo.mydomain.com" target="_blank" rel="noopener noreferrer nofollow ugc">demo.mydomain.com</a> then it has to be installed under that domain.</p>
<p dir="auto">Side effect:<br />
Now your invite emails will also go from <a href="mailto:demo.app@demo.mydomain.com" target="_blank" rel="noopener noreferrer nofollow ugc">demo.app@demo.mydomain.com</a>. Hope this is OK. BTW, you can change this "demo.app" in the Email section of the app's configure UI.</p>
]]></description><link>https://forum.cloudron.io/post/4850</link><guid isPermaLink="true">https://forum.cloudron.io/post/4850</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Thu, 14 Nov 2019 04:12:16 GMT</pubDate></item><item><title><![CDATA[Reply to Subscriber sign up mail issue for Ghost 3.0 instances on a sub domain on Thu, 14 Nov 2019 04:01:24 GMT]]></title><description><![CDATA[<p dir="auto">I am able to reproduce the above. It seems that the <code>demo.mydomain.com</code> part is hardcoded at <a href="https://github.com/TryGhost/Ghost-Admin/blob/18605d9d05d09d8f0ca6e918cd49b9703ed050c4/app/templates/components/gh-members-lab-setting.hbs#L184" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/TryGhost/Ghost-Admin/blob/18605d9d05d09d8f0ca6e918cd49b9703ed050c4/app/templates/components/gh-members-lab-setting.hbs#L184</a> which is in turn computed from the location where ghost is installed <a href="https://github.com/TryGhost/Ghost-Admin/blob/a5c69cc86d5cfefa702400fc7b03454f37f6d2d5/app/services/config.js#L62" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/TryGhost/Ghost-Admin/blob/a5c69cc86d5cfefa702400fc7b03454f37f6d2d5/app/services/config.js#L62</a></p>
<p dir="auto">I am not sure what the fix is. Do you know why Ghost is not using the mail settings it already has in it's config? (Sending normal member invitations works as expected).</p>
]]></description><link>https://forum.cloudron.io/post/4849</link><guid isPermaLink="true">https://forum.cloudron.io/post/4849</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Thu, 14 Nov 2019 04:01:24 GMT</pubDate></item><item><title><![CDATA[Reply to Subscriber sign up mail issue for Ghost 3.0 instances on a sub domain on Wed, 13 Nov 2019 22:02:30 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/tkd" aria-label="Profile: tkd">@<bdi>tkd</bdi></a> Maybe this is a bug in the packaging. Ideally, the Ghost app should know out of the box from which domain it's sending emails from. Let me investigate and get back on this.</p>
]]></description><link>https://forum.cloudron.io/post/4845</link><guid isPermaLink="true">https://forum.cloudron.io/post/4845</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Wed, 13 Nov 2019 22:02:30 GMT</pubDate></item></channel></rss>