Thanks to those who reported the duplicate sends of the M6 and M5 Ultra article. I’ve stopped it manually and will have to try to figure out what went wrong.
So far I’ve received more than 30 copies of the article and more are coming in every minute.
I’m sure it’s a glitch but I’ve received more than 25 emails about this TidBits article, they’re coming in faster than I can delete them. It’s not an email problem on my end, this is the only email this is happening with. Please check on the Tidbits end.
Thank you.
It’s now reached more than 100 copies of this email.
I got about 120 between 4:00 p.m Eastern and 4:12 and it now seems to have stopped for me. Don’t know where it’s stopped for others or just for me.
Yep, I got hit with the same avalanche of approximately 120 duplicate copies of the email message containing this TidBITS story.
Adam, there must be gremlins behind this technical deluge of duplication.
I agree. I can’t remember seeing anything like the torrent of about 120 copies of this single email article in a very long time. It’s the kind of thing that could have side effects, such as spam filters blocking delivery of the source of such torrents. If Adam has time to dig into what happened, it would be interesting to what happened and how wide its extent was. I note only a few of us have commented about the torrent in this thread, which makes me wonder if this effected everybody or just a few of us, perhaps from a few email servers. For the record, my email server is FastMail, and I’ve never seen anything like this from them.
I didn’t receive it at all. Now I think of it not sure when the last one was…
You’re set to receive only the full weekly issues, not articles shortly after they’re published. (Which you could do, as a TidBITS member. Look in your account.)
I’ve looked into what happened, and the answer is, I don’t know. However, there’s a new version of Sendy that has a note saying:
Improved Amazon SES Campaign Sending Resilience
Enhanced multithreaded Amazon SES sending to handle uncommon database or server interruptions more gracefully. Campaign delivery progress is now recorded transactionally, queue processing has stronger duplicate safeguards, interrupted sends can be identified and resumed safely, and parallel sending uses more efficient resource management, all while maintaining existing sending speeds and batch performance.
So I’ll try upgrading Sendy tomorrow.
Alright, Sendy is upgraded and passed a test send, so I’m going to push another article. Fingers crossed!
A few articles have flowed through now, so I’m going to declare this done but keep an eye on things.