Live Chat issue with email replies

[jfrere]

@girish ok got it. Will try. What would be best, creating an alias reply@my-domain.com for chatwoot.app@my-domain.com or changing chatwoot.app with reply?

[jfrere]

@girish said in Live Chat issue with email replies:

@jfrere Did you adjust export MAILER_INBOUND_EMAIL_DOMAIN="see-docs.cloudron.io" in /app/data/env.sh ? Important: the export keyword in the front. Also, you should restart the app after making the change. Atleast , that should get the mydomain.com part sorted out. Not sure where reply+xx comes from. Maybe it's hardcoded in chatwoot ? Or maybe it's part of live chat configuration ?

So just to let you know, it seems that adding export MAILER_INBOUND_EMAIL_DOMAIN=my-domain.com doesn't work. We might have a bug here.

[girish]

@jfrere Can confirm that it doesn't work for me either.

[jfrere]

@girish you should fill a bug report, I don't know where to do that.

[jfrere]

@girish I've added an reply@my-domain.com alias to the chatwoot.app@my-domain.com mailbox.

If you reply to the email with the provided reply+randomhex@my-domain.com, then the email goes into the Cloudron email inbox in Chatwoot, but is not appended to the actual Live Chat conversation. So it's useless.

[girish]

@jfrere said in Live Chat issue with email replies:

@girish you should fill a bug report, I don't know where to do that.

I found the issue here. If you recreate the Inbox inside chatwoot, it works. Not great but atleast it works. I will put this in our docs.

[girish]

@jfrere said in Live Chat issue with email replies:

@girish thank you. It's not necessary to configure cloud storage?

I was confused why you said this. I now understand what you meant . In their docs it says "Conversation Continuity requires your chatwoot installation to have a cloud storage configured" at https://www.chatwoot.com/docs/self-hosted/configuration/features/email-channel/conversation-continuity#configuring-inbound-reply-emails . I have no idea why. You will have to ask them if how these are all related.

After that, it seems you need getmail6 and run it as cronjob and feed it through some curl call. This all seems unnecessarily complex to setup and will break

[whitespace]

@jfrere As I am facing the same issue. Has this not been resolved yet?

[jfrere]

@whitespace I don't think so.

[girish]

@jfrere Did you ask in the upstream issue tracker or forum about this? The docs are a bit lacking/suspect here for us to debug this.