Replies: 2 comments
-
Figured it out. It's a TLS connection, not an SSL connection so the example port is wrong. I put in a PR to update it. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@BWStearns thanks for that! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to get my auth email/verification workflow working but running into a kind of silent failure.
This is my relevant Mailer config in
development.yaml
but when I sign up a user on local (usingcargo-watch -x check -s 'cargo loco start --server-and-worker'
to start my server) I don't get any error but I also never send an email. Is there some setup/config step that I'm missing? I notice that we don't explicitly start the mailer worker in App.rs. Does the MailerWorker not automatically get started with Loco?Update:
I've switched to using
BackgroundQueue
locally and confirmed that the AuthMailer does put an email on the queue to send.When I start up a worker with
cargo loco start --worker
the worker consumes the items inqueue:mailer
but it doesn't emit any errors and no emails get sent. Is there any way to make the mailer worker more verbose or is there something obviously wrong with my mailer config?Beta Was this translation helpful? Give feedback.
All reactions