Emails not working

Product Support

AI-generated summary

Rafael_Goncalves is experiencing email issues with their Discourse forum hosted on Digital Ocean. They are not receiving backup emails and need to change the SMTP port from 587 to 2525 for Brevo or switch to Mailgun. Ethsim2 confirmed that changing the port in app.yml and rebuilding fixed the email issue. They also provided a detailed guide for downloading forum backups via the console Ethsim2 and shared plans to create a community wiki on third-party email providers. NateDhaliwal suggested that switching to Mailgun involves updating the SMTP username and password in the app.yml file after setting up Mailgun.

1

In first place I would like to know, how I can download a backup of my forum through console in digital ocean, cause I don’t receive the mail of the backup.

In second place, I already found the problem of the forum not sending emails, the port beeing at 587. So what I’m asking is how can I change to the port 2525 in brevo to put my emails to work again, cause I don’t find that options.
Another option would be to switch to mailgun free plan, but I also don’t know how to change from brevo to mailgun in my discourse forum.

2

Hi @Rafael_Goncalves ,

I have done a test install this afternoon - Digital Ocean like yourself

.\discourse-doctor alerted to issue with port 587, connecting to Brevo

on change from port 587 to 2525 in app.yml and rebuild, email worked​:+1:

3

i did a Windows 11 screen recording of the full successful install, that involved many changes particularly with outbound email (third-party) providers Brevo or MailGun. Hoping to land it in the #community-wiki:sysadmins category tommorow​:slightly_smiling_face: (as in United Kingdom’s tommorow)

4

i think you would

snap install aws-cli --classic

aws configure

cd /var/discourse

.\launcher enter app

rails c

Discourse.enable_readonly_mode(Discourse::USER_READONLY_MODE_KEY)

exit

discourse backup

docker cp “app:/var/www/discourse/public/backups/default/your-site-2006-01-02-150405-v20200101150405.tar.gz “ “root@[server_ip_address]:/var/discourse/shared/standalone/backups/default/your-site-2006-01-02-150405-v20200101150405.tar.gz“

this step might be Unnecessary anyway, because /shared is bind-mounted to the host already ??

exit

aws s3 cp “/var/discourse/shared/standalone/backups/default/your-site-2006-01-02-150405-v20200101150405.tar.gz“ “myBucket://your-site-2006-01-02-150405-v20200101150405.tar.gz“

please note i haven’t tested these commands at all

5

@Rafael_Goncalves

You can set everything up in the Mailgun side of things, then change the SMTP username and password in your app.yml file.