Implement Spam Prevention Mechanism in JSM Customer Portal for Open Projects

XMLWordPrintable

    • 5
    • 5

      Issue Summary

      Currently, there is no mechanism available to safeguard JSM Open Projects from Spammers. We would like to bring to your attention a few use cases where we’ll need Spam Prevention Mechanism - via Customer Portal, Email Requests and API. 

      1. JSM should allow blocking specific email addresses, if they’re found to be spammers. Also, JSM should be able to identify the aliases and block them, if the same user tries to use an alias of the same mail address and tries to create a portal account. 

      2. There should be a throttling mechanism for the number of comments that can be added to a ticket - via API, Email and Customer Portal. 

      3. There should be restriction for the number of attachments, based on both the number of attachments and the total size of attachments in a ticket. 

       

              Assignee:
              Unassigned
              Reporter:
              Makesh Sundar
              Votes:
              7 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: