Big Oof: 2 instances reading the same email server

Greetings support-ists.

TLDR: We set up a dev server identical to the main (copied over everything) and changed a few settings like no outbound email. We didn’t disable inbound email polling, so the dev server has been slurping up about 50% of our prod email traffic for the last several MONTHS.

The logs are pretty comprehensive it seems…so the dead emails have ended up in

url:

/admin/email/rejected

Error:

Email::Receiver::BadDestinationAddress

Is there any way to wrap those error logs back up as inbound emails, and replay them back into the email parser for the prod server? It seems the logs have everything - reply key, subject, body text, etc.

Edit to add: shockingly, none of our hundreds of members noticed their replies were going to oblivion. The Email::Receiver::BadDestinationAddress error normally bounces an email warning back to them - but with dev outbound emails disabled, they were none the wiser.

Edit-2 to add: Is it even possible to insert topic replies after the fact out of order?

2 Likes