Hi, all! Our web client is calling auth.sendVerificationEmail() via the Nhost Client. We use Postmark internally so we set our SMTP settings to smtp.postmarkapp.com and port 2525 and the CRAM-MD5 auth method. (We also tried TLS.) Additionally, we have all the default email templates ready as well. We're getting 500 errors back like { "latencyInNs": 62000000, "level": "error", "message": "POST /user/email/send-verification-email 500 62ms", "method": "POST", "statusCode": 500, "url": "/user/email/send-verification-email" } but it's hard to discern what part of our settings we should modify? Postmark's help site says we should try ports 25, 2525, or 587. Likewise they say they support auth methods of TLS, CRAM-MD5, or Plain text. (We'd love to avoid sending in plaintext, tho.)
Last active 3 months ago
9 replies
9 views
- MA
Hi, all! Our web client is calling auth.sendVerificationEmail() via the Nhost Client. We use Postmark internally so we set our SMTP settings to smtp.postmarkapp.com and port 2525 and the CRAM-MD5 auth method. (We also tried TLS.)
Additionally, we have all the default email templates ready as well.
We're getting 500 errors back like
{
"latencyInNs": 62000000,
"level": "error",
"message": "POST /user/email/send-verification-email 500 62ms",
"method": "POST",
"statusCode": 500,
"url": "/user/email/send-verification-email"
}
but it's hard to discern what part of our settings we should modify? Postmark's help site says we should try ports 25, 2525, or 587. Likewise they say they support auth methods of TLS, CRAM-MD5, or Plain text. (We'd love to avoid sending in plaintext, tho.) - SH
we also tried removing all the custom settings to go back to the nhost defaults, but that's still giving 500 errors. is there any way to see more detailed logs from the mailer? it looks like the auth logs only show a 500 with no other details.
- SH
(btw, the default Nhost SMTP settings were sending all our emails to spam and being marked as gmail as dangerous with the link removed)
- MA
Had success with smtp.postmarkapp.com and port 2525 and the CRAM-MD5 so long as the "secure" setting is "false" which seems like something we'd like to avoid, too. (Maybe this is due to the port? I can try other port values accepted by Postmark to see if we can use a secure connection.)
- EL
Oups, missed this one. Glad you got it to work. If you want, you can post your findings in GitHub so others can find the info more easily: https://github.com/nhost/nhost/discussions/new under "Tips and Tricks"
Let us know if you find anything more from Postmark.
- EL
Btw @Nuno Pato , we're using Postmark too if I'm not mistaken. What port/secure settings do we use for Nhost?
- SH
we still don't have it working with secure = true (so far we only found settings that work with secure set to false)
- TA
I’m about to set up postmark, so this thread is super helpful.
- SH
would love to know if you figure out settings that allow secure set to true!
Last active 3 months ago
9 replies
9 views