AWS SES Configuration Skipped Emails

[kuzeal]

Name and Version

bitnami/discourse:3.4.1

What architecture are you using?

None

What steps will reproduce the bug?

I deployed the helm chart and the containers are running fine. From the UI of discourse I am attempting to send a test email after logging in as the admin. I have also tried registering as a new user and it produces the same issue.

What is the expected behavior?

I would like an email to be sent.

What do you see instead?

When I send a test email or register a new user, I get the following error in the admin email configuration “skipped” section :

554 Transaction failed: Invalid domain name: '127.0.0.1'.

In the logs of the discourse container, I dont see any errors.

When I go to the admin > emails > settings page, the "domain" section is empty:

Additional information

Sensitive information such as user, password, and the values for the domain have been removed or replaced with example values.

I have configured other services to use SES and those are sending emails properly with the same credentials. So from my Alertmanager service I can currently send emails from [email protected] where exampledomain.com is a domain I have verified in SES.

I have ingress enabled and am able to access Discourse online discourse.subdomain.exampledomain.com.

Here are values relating to smtp and the extraEnvVars I have set for the containers based on the values here. I can provide more if needed but I was thinking that these would be the only ones relevant.

smtp:
  enabled: true
  host: "email-smtp.us-west-2.amazonaws.com"
  port: "587"
  user: "XXXXX"
  password: "XXXXX"
  protocol: "tls"
  auth: ""
  existingSecret: ""

sidekiq:
  extraEnvVars:
    - name: DISCOURSE_SMTP_DOMAIN
      value: exampledomain.com
    - name: DISCOURSE_NOTIFICATION_EMAIL
      value: [email protected]

discourse:
  extraEnvVars:
    - name: DISCOURSE_SMTP_DOMAIN
      value: exampledomain.com
    - name: DISCOURSE_NOTIFICATION_EMAIL
      value: [email protected]

Is the issue my discourse configuration?

[carrodher]

Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.

If you think that's not the case and would like to contribute a solution, we'd like to invite you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Please don't hesitate to contact us if you have any questions or need help.

Suppose you have questions about the application, customizing its content, or using technology and infrastructure. In that case, we strongly recommend that you consult the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.

[kuzeal]

I just wanted to drop in some further information in case it would give any other insight into the issue I am seeing.

There is no way to set the smtp_domain_name through the chart. Even when I put it in the extraEnvVars sections of both discourse and sidekiq, the discourse.conf file does not pick it up. I manually replaced the contents of the discourse.conf file to include the smtp_domain value which let me successfully send test emails, but when I try to send any other emails, like signing up for example, I get the same 554 Transaction failed: Invalid domain name: '127.0.0.1'. error.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.