Lighthouse Spam Issues

9:01 AM PST (the next day)

I deployed some code late last night that should make the spam handling more tolerant (hello, http timeouts!). I also changed the default behavior for failed API calls to leave the ticket in the current state, rather than marking it spam. Please let us know if there's something we can do to resolve any spam fires, or if you're still seeing issues.

We've gotten some requests over the last month to allow projects to disable spam tracking. We'll cautiously provide this, but I'm thinking some of you don't remember the dark spam-filled early days of Lighthouse. We have a ridiculous tar pit system that I hope is keeping a lot of the riff raff out.

6:57 PM PST

I recently heard from Defensio. They are in the process of restoring their service, in the mean time we'll be working on a fix on our end to ensure we'll be able to handle this scenario in the future.

2:58 PST

It looks as if an Amazon EC2 is the cause of the problem. Defensio is twittering their status that you can follow here.

2:52 PM PST

Just a quick post to let everyone know we started experiencing high levels of false positives for spam. It appears our filter Defensio is down at the moment. We're getting in touch with them and I'll update this post as soon as I know something further.