DownloadBackupEmail and CriticalUserEmail fail

Product Support Self-hosting
,

AI-generated summary

In a discussion about email-related failures in a Bitnami Helm chart deployment of Discourse — specifically DownloadBackupEmail and CriticalUserEmail — oleksii notes that while Bitnami Helm charts are unsupported by the community, they’ve encountered issues with MailJet SMTP configuration. Despite using the same MailJet service successfully in an official Discourse cloud deployment, their Bitnami instance fails to send functional emails, likely due to MailJet rewriting URLs for click tracking, as pfaffman suggests. pfaffman also notes that backups can be downloaded manually, though the location in Bitnami deployments is unclear. oleksii initially suspected misconfigured admin credentials but later resolved the issue by updating the SMTP host to in-v3.mailjet.com as shown here, indicating the problem was related to SMTP endpoint configuration rather than credentials or core functionality. This highlights a configuration nuance specific to Bitnami’s Discourse Helm chart when integrating with MailJet, especially around SMTP host selection.

1

I know that bitnami helm chart isn’t supported deployment by this community.
I’ve asked this question in bitnami, but I haven’t got any reply.
Maybe you can limit a scope of my research or provide some hints please.

My customization of value file:

auth:
   email: my@email.com
   username: superAdmin
   password: "password"
smtp:
   enabled: true
   host: "mailjet"
   port: "587"
   user: "user"
   password: "password"
   protocol: ""
   auth: ""
   existingSecret: ""

I got DownloadBackupEmail fail when tried to download backup.
I got CriticalUserEmail fail when tried to change password through the forgot button.

2

My guess is that mail jet is rewriting the urls when it sends mail so that it can do click tracking and it isn’t working.

Best is to tell mail jet not to do link click processing.

You can download the backup file directly, but I don’t know where Bitnami puts it.

3

Thanks for reply.
Hmmm, I’m confused.

I have another instance that I deployed according to the official deployment instructions. Both I use MailJet

I was thinking that my helm chart didn’t properly populate admin credentials into the application.

4

To fix it I set “in-v3.mailjet.com” into smtp.host: