[
https://issues.apache.org/jira/browse/ROL-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza resolved ROL-1327.
-----------------------------
Resolution: Won't Fix
I'm not sure I like this idea, as it would allow a spammer to create a blog and
test his spam comments to find out which terms make the blacklists. Also,
blacklists should be maintained at an admin-level instead of having each user
manually maintain their own set of terms (which would highly duplicate each
other: viagra, handbags, etc. and cause the user not to contact the blog admin,
resulting in other blog owners having the same problem.) Instead, if there's a
spam term showing up in a lot of spam comments, the blog writer should contact
the admin with the term, for the admin to add to the site-wide blacklist so
everyone is saved from it.
> Provide blacklist keyword to the blog owner if a comment is marked as spam
> for this reason
> ------------------------------------------------------------------------------------------
>
> Key: ROL-1327
> URL: https://issues.apache.org/jira/browse/ROL-1327
> Project: Roller
> Issue Type: Improvement
> Reporter: linda skrocki
> Assignee: Roller Unassigned
>
> Provide blacklist keyword to the blog owner if a comment is marked as spam
> for this reason. Knowing the exact term that caused the comment to be marked
> as spam will help determine if the keyword should be removed from the
> blacklist.
> In addition to providing the blacklisted keyword, also note which of the
> three blacklists it belongs to (static roller blacklist, site-wide blacklist,
> individual weblog blacklist).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
