Cloudron Forum

Same here (since sending through Brevo (Sendinblue)).

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.

What's strange about this to me is I seem to be unaffected (so far at least), and I'm looking in Cloudron mail pages quite frequently. Not sure why but I am throwing this out there in case it has something to do with the region IP of the Cloudron servers? I'm located in Canada, in case that matters at all. I just wonder if there's a pattern for this perhaps with certain countries affected more than others, etc. Though I guess ultimately if Cloudron isn't properly accounting for blocked connections to Spamhaus and seeing a blocked connection as a listing, then that should still be fixed in the code if that's true. Sorry, ignore me I think, as I misunderstood the problem. I thought this was around Cloudron detecting that the IP of Cloudron was on the blocklist, but that would have no bearing on rejecting emails so I think I misunderstood. Sorry about that.

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

@scooke said in Every Cloudron instance sets a DKIM entry. Is this good or bad or necessary?: why use ai when we already have Real Intelligence here. Limited time and resources of humans?

@jdaviescoates said in URGENT: In a post on an originally unrelated thread about IPv6 issues @Gengar posted this link https://www.spamhaus.com/resource-center/successfully-accessing-spamhauss-free-block-lists-using-a-public-dns/ which I think explains what's going on with all these false positive spamhaus issues people are having: The TL;DR seems to be: fill in this form https://www.spamhaus.com/free-trial/sign-up-for-a-free-data-query-service-account/

@jdaviescoates said in Cloudron seems to have changed to set-up ?all SPF records instead of ~all - why?: whereas only my newer ones have ?all I checked some domains on my Cloudron and noticed one has -all where all others have ~all. Then I realised that one was a recently transferred domain that was already 'working' and obviously the previous hoster had it like this, Cloudron didn't touch it when "importing" it.

A homemade problem. We have refactored our Ansible role. It has installed an MTA that was previously started as Cloudron's mail service. After uninstalling the MTA, everything works as expected.

I remove the user from the group and add the user again to the group.

https://github.com/haraka/haraka-plugin-dns-list/pull/11/commits should fix it