The Doctor

Results 345 comments of The Doctor

What about building the message body piecewise? ``` ... "body": "{% credential foo %} lkjl;kj lk;jl;kjl {% credential bar %} {% credential baz %} l;kajsdl;kfjds...." ... ``` It would be...

That is Cloudflare getting in your way. You might have to look intoi something like phantomJS to handle the bot-blocking for you, or find another way around it.

I think pushing to both is a good idea. A lot of folks have already cut over entirely, and there's no telling if they'll try it again a few months...

I'm seeing it as well on one of my nodes. I'm not sure which one yet, but it's impacting a third to a half of my outbound email alerts.

@dsander Did that today (commit 1c18d3b0227184f9af9354bb7ecfb2b60bcc41de). Still getting it on one of my nodes. Edit: Isolated to my primary public facing node, which ironically is configured to connect to localhost....

I shut down the job workers on all of my boxen this morning and traced through this entire thread, trying everything one by one. No dice here, too. Same errors...

> ``` > SMTP_ENABLE_STARTTLS_AUTO=true > SMTP_SSL=true > ``` Just tried that. No soap. Incidentally, this happens both when I use a self-signed certificate for Postfix (the default Snakeoil cert) or...

This might be worth investigating: https://stackoverflow.com/questions/71202804/why-isnt-a-self-signed-smtp-certificate-ignored-by-rails-actionmailer-6-1-rub

Unfortunately, I tried rolling back to Ruby v2.7.2 and the latest Gemfile isn't having any of it. The breaking changes in net-smtp are what's doing it, and I'm not entirely...

@dsander Yes, I am, across three servers. I tried the fix in the Stackoverflow answer and it did not work. It just changed the error I was getting. Incidentally, I...