Unable to get the verification email

Installation
1

Hello guys, after three hours I don’t know what more to test.
I have re-installed many but anything is working properly.

I have checked my SMTP configuration with an external site and is working fine.

My domain provider is using 465 SSL required.
Right now all emails are arriving correctly from external sites (and as said with the tool).

I have configured my discourse setup with SSL.
The site works correctly, it opens the page and auto-https://, but when I fill the first-step information the confirmation email never arrives.

My app.yml config:

## BE *VERY* CAREFUL WHEN EDITING!
## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT!
## visit http://www.yamllint.com/ to validate this file as needed

templates:
  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/web.template.yml"
  - "templates/web.ratelimited.template.yml"
## Uncomment these two lines if you wish to add Lets Encrypt (https)
  - "templates/web.ssl.template.yml"
  - "templates/web.letsencrypt.ssl.template.yml"

## which TCP/IP ports should this container expose?
## If you want Discourse to share a port with another webserver like Apache or nginx,
## see https://meta.discourse.org/t/17247 for details
expose:
  - "80:80"   # http
  - "443:443" # https

params:
  db_default_text_search_config: "pg_catalog.english"

  ## Set db_shared_buffers to a max of 25% of the total memory.
  ## will be set automatically by bootstrap based on detected RAM, or you can override
  db_shared_buffers: "128MB"

  ## can improve sorting performance, but adds memory usage per-connection
  #db_work_mem: "40MB"

  ## Which Git revision should this container use? (default: tests-passed)
  #version: tests-passed

env:
  LANG: en_US.UTF-8
  # DISCOURSE_DEFAULT_LOCALE: en

  ## How many concurrent web requests are supported? Depends on memory and CPU cores.
  ## will be set automatically by bootstrap based on detected CPUs, or you can override
  UNICORN_WORKERS: 2

  ## TODO: The domain name this Discourse instance will respond to
  ## Required. Discourse will not work with a bare IP number.
  DISCOURSE_HOSTNAME: *HIDDEN*.com
 ## Uncomment if you want the container to be started with the same
  ## hostname (-h option) as specified above (default "$hostname-$config")
  #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: 'info@*HIDDEN*.com'

  ## TODO: The SMTP mail server used to validate new accounts and send notifications
  # SMTP ADDRESS, username, and password are required
  # WARNING the char '#' in SMTP password can cause problems!
  DISCOURSE_SMTP_ADDRESS: smtp.buzondecorreo.com
  DISCOURSE_SMTP_PORT: 465
  DISCOURSE_SMTP_USER_NAME: info@*HIDDEN*.com
  DISCOURSE_SMTP_PASSWORD: "*HIDDEN*"
  DISCOURSE_SMTP_ENABLE_START_TLS: true
  # (optional, default true)

  ## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate
  LETSENCRYPT_ACCOUNT_EMAIL: info@*HIDDEN*.com

  ## The http or https CDN address for this Discourse instance (configured to pull)
  ## see https://meta.discourse.org/t/14857 for details
  #DISCOURSE_CDN_URL: https://discourse-cdn.example.com

## The Docker container is stateless; all data is stored in /shared
volumes:
  - volume:
      host: /var/discourse/shared/standalone
      guest: /shared
  - volume:
      host: /var/discourse/shared/standalone/log/var-log
      guest: /var/log

## Plugins go here
## see https://meta.discourse.org/t/19157 for details
hooks:
  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - git clone https://github.com/discourse/docker_manager.git

## Any custom commands to run after building
run:
  - exec: echo "Beginning of custom commands"
  ## If you want to set the 'From' email address for your first registration, uncomment and change:
  ## After getting the first signup email, re-comment the line. It only needs to run once.
  #- exec: rails r "SiteSetting.notification_email='info@unconfigured.discourse.org'"

Piece of production.log

 Started POST "/finish-installation/register" for 93.176.189.249 at 2019-10-24 13:02:12 +0000
 Processing by FinishInstallationController#register as HTML
   Parameters: {"utf8"=>"✓", "authenticity_token"=>"JDM8SDZMVZwNxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxuVRChib7+aXhsrYN5gmszmPNF00QpzRduSzYY0g==", "email"=>"info@*HIDDEN*.com", "username"=>"Administradora", "password"=>"[FILTERED]", "commit"=>"Register"}
 Redirected to https://*HIDDEN*.com/finish-installation/confirm-email
 Completed 302 Found in 36ms (ActiveRecord: 0.0ms | Allocations: 2434)
   Rendering layouts/email_template.html.erb
   Rendered layouts/email_template.html.erb (Duration: 0.6ms | Allocations: 139)
 Started GET "/finish-installation/confirm-email" for 93.176.189.249 at 2019-10-24 13:02:12 +0000
 Processing by FinishInstallationController#confirm_email as HTML
   Rendering finish_installation/confirm_email.html.erb within layouts/finish_installation
   Rendered finish_installation/confirm_email.html.erb within layouts/finish_installation (Duration: 1.6ms | Allocations: 357)
   Rendered layouts/_head.html.erb (Duration: 6.5ms | Allocations: 228)
 Completed 200 OK in 14ms (Views: 9.8ms | ActiveRecord: 0.0ms | Allocations: 1277)
 Delivered mail a492e5f7-2935-4776-b453-1593fadc5e6e@*HIDDEN*.com (60080.7ms)
 Job exception: end of file reached
2 Likes
2

It appears like you’re trying to use a user webmail service in place of an app mail service like Mailgun. Is there any reason you’re not using Mailgun or an equivalent provider?

4 Likes
3

@justin I’m not comfortable with Mailgun. I have configured now the email with sendinblue but not sure if it’s a good option because it limits to 40/hour emails.

3 Likes