I followed this guide and can partially confirm that it solves the problem. Emails to logged in users or agents are now handled and delivered correctly.

Unfortunately, the problem still exists for external users. When Chatwoot is embedded on the website, visitors can leave their email address before the conversation starts. This will additionally send replies to the visitor via email in case the visitor leaves the site in the meantime. These emails will still be sent from the wrong email address. This is clearly evident from the Cloudron email log.

As a result, the problem unfortunately persists. Is there a solution for this?

There is a new patch release coming up, so maybe that brings in some fixes.

@mdreira Don't know about facebook, but we did manage to configure telegram with chatwoot just the other day.

I remember that first time we set it up things didn't work. Then we re-setup the channel in botfather and it started working. You can also check the chatwoot logs which shows some activity. There is also a telegram bot command which shows that chatwoot has "registered" as a web hook. @nebulon probably remembers the command.

@luckow not sure I like the sound of 'surprise' but could be good !

@roofboard Please open a new topic instead of necro bumping old topics with semi related answers.

Now to your question.
Right now there is no official way of doing this.
And also I would not recommend of doing this.

Do not expect support for the following.

But against my advice, and now this is theoretical, I have not tried it but in theory it should work.
Yes you could do that even, semi permanent.

You could edit the image of the app on the server and commit the changes.

If you know there is a problem AND you know how to fix it, why don't you commit your change?
Here is the repo: https://git.cloudron.io/cloudron/n8n-app
Please, if you know of a problem submit a PR.

Now waiting for my application to access Twitter Business APIs to be (hopefully) approved...

@MooCloud_Matt Do you think you can ask them what is the best way to increase the polling interval here - https://github.com/chatwoot/chatwoot/discussions ? We can of course make schedule.yml editable on the Cloudron side but the changes will need to be then merged across upgrades. So, would be best to ask this upstream first.

@yairShiloach this seems like an app issue. Maybe you can check in https://github.com/chatwoot/chatwoot/discussions or https://discord.gg/cJXdrwS

@yairShiloach We will have a 7.1.4 later this week or early next week.

@jan-reinhardt that would be difficult for us to maintain. I think best approach is to fork the existing package and create a custom build. Code is at https://git.cloudron.io/cloudron/chatwoot-app

@sparkwise

This is nice but not strictly necessary.

It is very nice indeed but being necessary or not is relative to how much features one wants to make life easier and getting nearer to what's offered by Big techs and SaaS in the like.

So, if that specific function can be fixed for that app I'd say it should be. Of course nothing is absolute lol 😆

@imc67 are you referring to the chatwoot nokogiri security issue bullet point? The upstream project has provided no information on how severe it is. I couldn't find nokogiri in the diffs either, would appreciate any info on this. They have no info on their blog either.

As for AdGuard, it has already been updated to support ipv6 (which is not backward compatible tested with 7.0). Also, the security issues from what I see are Go related things which are kinda unlikely because AdGuard is not exposed to the world.

In contrast, for clear security posts like https://about.gitlab.com/releases/2022/02/25/critical-security-release-gitlab-14-8-2-released/ , we make it available asap for 7.0.

The latest package fixes this. Docs are at https://docs.cloudron.io/apps/chatwoot/#rails-console

@apoim You can place custom environment variables in /app/data/env file https://docs.cloudron.io/apps/chatwoot/#custom-config . Essentially you set the config variables that are listed in https://www.chatwoot.com/docs/self-hosted/configuration/features/integrations/facebook-channel-setup#configuring-the-environment-variables-in-chatwoot in that file.

@imc67 Awesome and happy to hear that.

PS: I know that feeling - a fellow FF user.

@girish in my understanding, yes. Taken from here https://www.chatwoot.com/docs/self-hosted/telemetry

@imc67 I have not found anything about LDAP in the documentation. https://www.chatwoot.com/docs/self-hosted
There is a GitHub issue about "Oauth integration". https://github.com/chatwoot/chatwoot/issues/1318 Let's see.

@ianhyzy this sounds more like an upstream app bug. Do you see any errors in the app or browser logs which might lead to this?