When people are subscribed to be notified of new comments on a thread -- if a post is unpublished by the spam.module the subscription notices that a new post occured are still sent out. This causes people to go the the page expecting a new post only to find nothing has changed.

Is there anyway you could change things so that if a post is marked as spam people on the subscirption list are not notified that a post has been made?

Also is there anyway you could make it to where the spam could be bulk deleted? Perhaps check all and then read through the list and uncheck those that are not spam and a button that deletes all checked?

BTW I love the module. Great job.

Keith Daniels
Web Coordinator
Linux Journal
keith@ssc.com

Comments

jeremy’s picture

jeremy commented

The current design is such that the comment is published, and then it is filtered and determined to be spam. That is why the subscription module is sending out notification, even though the content is ultimately being filtered.

For performance reasons I'd like to look at a more efficient way to do this, but it's not currently something I'm working on.

jeremy’s picture

jeremy commented
Status: Active » Fixed

Your request should be filed with the subscription module, not the spam module.

The best that the spam module can offer is with the rewritten version known spammer IP's are blocked before the user even posts anything into the database.

osherl’s picture

osherl commented
Anonymous’s picture

(not verified) commented
jeremy’s picture

jeremy commented
Version: » 4.6.x-1.x-dev
Status: Fixed » Closed (fixed)

Closing manually. (I think the project module is broken, it keeps marking them updated when they should be closed.)