Cloudron Forum

@mattcazz yes, definitely . In hindsight, we should have maybe package the mail server more like an "app" . And then just like other apps, it would have gained all the customization of Cloudron apps. The email configuration could then have been inside this "mail server" app. We want to rework mail server to an app after Cloudron 9.

See: https://forum.cloudron.io/post/52997

@nostrdev So glad you listened when we chatted about that too! Welcome.

Thank you all! the issue was the unbound service not working and also my email delivery issue too.

Hi @James - Many thanks for this. The changes already looks great and promising. May I make a suggestion ? I think, in this case, Freescout approach offers a greater granularity between email notification and in-app notification, with potential for further development based on the communication channel (Mobile if ever, API ? etc..), leaving the end admin users decide what works best for them Here is the screen I am referring to in Freescout. [image: 1753778253533-e6ab2fb5-e080-4b2e-8443-adde0ee3d332-64145699-7f368480-ce22-11e9-9ead-1ac3ef29ba9b-resized.png] If it is not too late in the development of this, maybe it might be worth considering?

I've also tried to create a mailbox (test@mydomain.coop) and set-up a redirect with roundcube to three "external" email addressed (@gmail / @posteo), delivery fails with all of them. So it is not specifically with Cloudron mailing lists but a bigger issue with redirects in general. @staff any clues?

What is the use case to prevent internal routing? But if you set up an external MX record and add that MX host to your SPF also (so Cloudron will accept incoming), then I think it does what you want?

@girish Thanks for this - This is a great workaround and fit the bill perfectly for us.

Unfortunately I can't tell you preciesly. Once, I did reset the all the users preferences via the console: https://meta.discourse.org/t/reset-default-categories-watching-setting/244930/8 But there was no error message in the dashboard. Otherwise, I didn't do anything of importance. For updates, I think the error message appeared not before 3.4.3 or 3.4.4… Sorry for the vagueness.

Thank you @james, that is great news.

TTL issue ? I mean, this symptom lasted a very long time (a full year I'd say). Not seen since early June though. Maybe the "odd DNS issue" then. I guess this can be closed.

@james Yes it’s technically a feature request. I only threw it in here since it seemed like Girish was already making adjustments to the filtering in the mail event log viewer. If you’re okay forking it to a feature request, that’s totally fine.

Hello @tadeas Is this still an issue or can this topic be marked as solved?

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

Hi @fbartels You're right, double checked and it always defaults to smtp. instead of .my When manually changing on both PC and Mobile, the SMTP accounts can be added without the certificate error! Thanks Everyone!

@mrhakash said in Outbound Emails Queued — NXDOMAIN Error and Local DNS Resolution Issue: dig @127.0.0.1 gmail.com mx returns: connection refused You have to check host -t MX gmail.com 127.0.0.150 . Can you also run cloudron-support --troubleshoot for hints?

@mmtrade the image looks correct . the issue is something else then . if you write to support@cloudron.io, then we have to debug this again .

@avatar1024 said in Email search not working properly: What's tika? tika is this - https://tika.apache.org/ . it converts the pdf/docs attachments in emails to text to make them searchable

Here the issue was that the e-mails have been moved to the new cloudron server only partially, and the new folder wasn't created in this case, so when I tried to move this in Thunderbird, it failed. So, this is solved now