Hello @bmann
@bmann said in Mail problems on Ghost:
bump on this
Sorry that this topic did not get any traction for almost a week!
@bmann said in Mail problems on Ghost:
"Do not configure app's mail delivery settings
The app's mail delivery settings is left alone. You can configure it inside the app."
Where did you find this text? I could not find it in the documentation, the app package or anywhere.
Would like to know where this came from since this might be misleading.
@bmann said in Mail problems on Ghost:
Going to try it! Wish me luck!
If you want to tinker with apps, always create an app backup first or even clone the app so you can take a shotgun approach to the clone.
There are certain settings for each app that Cloudron will override on every app restart.
I know @BrutalBirdie submitted a PR yesterday about this => https://git.cloudron.io/docs/docs/-/merge_requests/75/diffs
According to the app startup https://git.cloudron.io/packages/ghost-app/-/blob/master/start.sh?ref_type=heads#L39
If CLOUDRON_MAIL_SMTP_SERVER is not empty it will set up the mail config on every app restart:
if [[ -n "${CLOUDRON_MAIL_SMTP_SERVER:-}" ]]; then
json -I -f /app/data/config.production.json \
-e "this.mail.from = \"${CLOUDRON_MAIL_FROM_DISPLAY_NAME:-Ghost} <${CLOUDRON_MAIL_FROM}>\"" \
-e "this.mail.options.host = '${CLOUDRON_MAIL_SMTP_SERVER}'" \
-e "this.mail.options.port = '${CLOUDRON_MAIL_SMTP_PORT}'" \
-e "this.mail.options.auth.user = '${CLOUDRON_MAIL_SMTP_USERNAME}'" \
-e "this.mail.options.auth.pass = '${CLOUDRON_MAIL_SMTP_PASSWORD}'"
fi
You may want to disable the mail config for the app to avoid this. See => https://docs.cloudron.io/apps/#disable-email-configuration
Well, apparently the only way to "fix" this, is to docker stop the yellow services Mail / Mongo / Postgres / MySQL and then restart them in the dashboard and they start up succesfully, and then you can start other apps that have been stopped.
@bmann said in Github Actions documentation/example for Surfer:
/website/*
This is a bit weird. In the output above it complains that it cannot find /website/, while in your yaml you are passing website/. The first one would be no surprise if it does not work, the second one however should work as ci tools usually open a shell where you will be directly in your git checkout.
I would try to debug this with inserting a few ls and pwd into your yaml to see where you actually are and if this might be a permission issue of some kind.
@bmann said in Standard package formats:
Effectively: what is the difference between some-form-of-buildpacks and Cloudron's current packaging format?
Good question. You should find the information you need in https://docs.cloudron.io/packaging/manifest/
@LoudLemur _DNSLink is a feature of the IPFS protocol that you map a TXT record of the hash of the root of your published website or app and then CNAME at a single IPFS gateway. This means you don’t need to run a gateway for each domain.
Setting up the sieve rule means I have to have the password and set all of that up.
Using the "mailing list" settings means I don't have to do any of that, don't need to create an inbox, and it doesn't need to be owned by any accounts (and cloudron users with email admin / admin / superadmin can modify as needed).
[image: 1702689032849-screen-shot-2023-12-15-at-5.08.26-pm-resized.png]
So I guess I answered my own question I'll write it up. for people who ask in the future. "How do I set up email forwarding to external accounts without having to provision Cloudron accounts" == mailing list.
@luckow thanks for the SoGo -- looks like that does take care of everything.
Yeah, the access key is what is going to check if the domain is there. I think "Skip nameserver validation for custom Route53 NS names" would get me there
And all of the DNS and Email stuff...I totally understand how difficult it is to give less technical users the ability to even USE this stuff, as well as support slightly more advanced users. You're doing a great job!
OK, I finally worked on this AGAIN and remembered how messed up this is conceptually.
username: groupname@domain
password: (any one of the passwords of the people that have access)
This is also makes Freescout work for me https://forum.cloudron.io/topic/12976/connection-could-not-be-established-with-host-mail-domain-com-connection-timed-out-110/43
A single "username" having multiple passwords is what messes me up every time.
@bmann said in WordPress Migrate Feedback, SMTP Mailer Instructions:
This is a restriction in the All-in-One WP plugin
Like @scooke says, if we're talking about the same plugin, it isn't. As I said, I recently did one over 1GB.
B
