אימיילים לא נשלחים

תמיכה התקנה

סיכום מבוסס בינה מלאכותית

The user Amadov is seeking help with email not being sent on their self-hosted Discourse instance, despite trying various solutions. They provided their app.yml configuration, which includes SMTP settings for smtp.beget.com. pfaffman responds by asking if email ever worked and recommends checking the troubleshooting guide Troubleshooting email on a new Discourse install. They also suggest verifying that the notification email is set to an address that beget.com allows sending from and recommend running discourse-doctor to check for errors. Amadov shares their configuration, and pfaffman advises checking logs and ensuring proper setup with the email provider.

1

I ask for help, sending letters to the mail does not work, what should I do?
Already tried everything, nothing helps

image
image1920×1080 151 KB

2

Welcome @Amadov. Sorry you’re having trouble. Email is hard.

DId the everything that you tried include Troubleshooting email on a new Discourse install?

Things that would make it possible for people to help would include what mail service you’re using and if it’s ever worked before.

3

containers/app.yml

DISCOURSE_HOSTNAME: 'newstory.host'
  #DOCKER_USE_HOSTNAME: true

  ## TODO: List of comma delimited emails that will be made admin and developer
  ## on initial signup example 'user1@example.com,user2@example.com'
  DISCOURSE_DEVELOPER_EMAILS: 'support@newstory.host'

 ## TODO: The SMTP mail server used to validate new accounts and send notifica>
  # SMTP ADDRESS, username, and password are required
  # WARNING the char '#' in SMTP password can cause problems!
  DISCOURSE_SMTP_ADDRESS: smtp.beget.com
  DISCOURSE_SMTP_PORT: 587
  DISCOURSE_SMTP_USER_NAME: support@newstory.host
  DISCOURSE_SMTP_PASSWORD: ***********
  DISCOURSE_SMTP_ENABLE_START_TLS: false
  #DISCOURSE_SMTP_AUTHENTICATION: none
  #DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: none
  #DISCOURSE_SMTP_DOMAIN: smtp.beget.com
  #DISCOURSE_NOTIFICATION_EMAIL: support@newstory.host

  LETSENCRYPT_ACCOUNT_EMAIL: su**d@*k.**
4

DId it ever work? Did you follow the steps in the troubleshooting guide?

You need to see that the notification email is set to an address that beget.com will send from.

You can try running discourse-doctor; it can sometimes give more helpful messages, but I’m not familiar with beget.com. You should see if anything is in the logs there.