Technical difficulties
Our server has been locking up repeatedly over the past few days, apparently because our spam filter was consuming an obscene amount of memory. I have (probably) fixed the problem, and if it weren’t less than an hour before sunset on Friday, I would have an extensive and geeky rant about what happened, but instead I will just provide a user-friendly public-service announcement:
If you have sent email to us in the past few days and you have not received a bounce message from your Internet service provider, we will (probably) get it Real Soon Now. If you did receive a bounce message, it is now (probably) safe to resend the message. If you have been treating email as a communications medium that is generally guaranteed to reach its destination in a matter of hours, please adjust your expectations… it usually works that way, but nothing in the perverse architecture of the Internet really guarantees that it will do so.
We apologize for the inconvenience. Unless, of course, you are a spammer.
commenting closed for this article
Bad advice costs nothing, and it’s worth the price We are of mediocre screenwriting. Always.
Sounds like you should consider bogofilter instead of dspam.
I’ve used both bogofilter and dspam in the past, and felt that dspam did a better job… well, it did a better job until it brought the server to its knees.
(And it ran with the mysql backend all through Shabbat and the server’s still up, so that looks like it did the trick, although it seems I had to do one more database tweak to make it actually do something with the tokens imported into the mysql database.)