Closed nalipaz closed 3 years ago
I dont think sendmail
works currently. Sort of complicated to get into the container with all of the right options. The mailgun
or sns
drivers are all that I have tested with.
Is there a list of supported mail drivers for Cachet Docker? I'm trying to use smtp
with Amazon's Simple Email Service and it doesn't appear to be working. But I'm also having trouble narrowing down the problem.
Anyone get this working in Docker? I can subscribe, but my gmail account never receives the email. Tried manual smtp commands from within the container using telnet, targeting the same host/port that I'm using in my config and I verified I can receive that email. Is there logging or a way to debug mail in cachet? Note I'm NOT seeing the python exception that @nalipaz mentioned and I'm running APP_DEBUG="true"
as you can see in my (redacted) /var/www/html/.env
file below.
I'm running docker image: cachethq/docker:2.3.13
APP_ENV="development"
APP_DEBUG="true"
APP_URL="http://localhost"
APP_LOG="errorlog"
APP_KEY="base64:[REDACTED]"
DB_DRIVER="pgsql"
DB_HOST="[REDACTED]"
DB_DATABASE="postgres"
DB_USERNAME="[REDACTED]"
DB_PASSWORD="[REDACTED]"
DB_PORT="5432"
DB_PREFIX=""
DOCKER=true
CACHE_DRIVER="apc"
SESSION_DRIVER="cookie"
SESSION_DOMAIN="{{SESSION_DOMAIN:-$APP_URL}}"
SESSION_SECURE_COOKIE="false"
QUEUE_DRIVER="database"
CACHET_EMOJI="false"
CACHET_BEACON="true"
CACHET_AUTO_TWITTER="true"
MAIL_DRIVER="smtp"
MAIL_HOST="[REDACTED]"
MAIL_PORT="25"
MAIL_USERNAME="null"
MAIL_PASSWORD="null"
MAIL_ADDRESS="status@[REDACTED].com"
MAIL_NAME="Status"
MAIL_ENCRYPTION="null"
REDIS_HOST="null"
REDIS_DATABASE="null"
REDIS_PORT="null"
REDIS_PASSWORD="null"
GITHUB_TOKEN="null"
NEXMO_KEY="null"
NEXMO_SECRET="null"
NEXMO_SMS_FROM="Cachet"
Ok update. Strangely without changing anything config-wise, I tried manually adding a subscriber on the subscribers tab in the dashboard and I got that confirmation email. I deleted it and then tried again from the front end by clicking the Subscribe button and it magically started working. Maybe an intermittent issue? I'll report back if it happens again.
Just wanted to add the setup that worked for me using Docker and Mailgun. Please bear in mind that unless you are verified by Mailgun and your MX records are propagated, no email will go through.
All the following data are stored in docker-compose.yml
and have no quotes.
MAIL_DRIVER=smtp
MAIL_HOST=smtp.mailgun.org
MAIL_PORT=587
MAIL_USERNAME=postmaster@mail.website.io
MAIL_PASSWORD=<DEFAULT_PASSWORD_PROVIDED_BY_MAILGUN>
MAIL_ADDRESS=postmaster@mail.website.io
MAIL_NAME=Status
MAIL_ENCRYPTION=null
Currently, the application is on http
and we want to migrate it to https
but it's able to send emails on http
. The MAIL_NAME
is one word but might be able to support spaces, we will see if it requires quotes (e.g. Status Report Page
) or escaped spaces (e.g. Status\sReport\sPage
). Finally, whether instead of using the default password by Mailgun we can replace it by an API_KEY
.
To test this setup I tried to invite myself to the ”Team” section of the application, and within 30 secs the email arrived with the log Processed: mailer@handleQueuedMessage
showing in the console. I'll continue a couple tests and document them within this thread.
For me (necroposting in a very important thread), I get an error 500 whenever I try to even send a test e-mail. I tried the method @jjperezaguinaga posted above, albeit with Office365, and no success. I even have the log-to-terminal up and I don't even get a python error, just an error 500 on POST.
I have attempted most everything to get email subscriptions working in the Docker image. I am able to sign-up for subscriptions however I don't receive the verification email or any of the notification emails. Is there anything wrong in my docker-compose?
I receive the following errors when I add a subscriber: