Active
Project:
Crew Connect
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
24 May 2012 at 20:42 UTC
Updated:
30 Nov 2012 at 23:19 UTC
Jump to comment: Most recent file
Comments
Comment #1
kreynen commentedWhat do you think about tracking both the user sending the email and the users receiving the email in CiviCRM as an Activity Type and base the sending quota on that? Then you'd have that information available fo reporting.
Comment #2
soniat commentedWe like the idea of being able to track users sending crew connect emails and those receiving it. Having the data for reporting purposes is also a plus. Why would a sending quota be necessary? How would an acceptable quota be determined.
Sonia
Comment #3
kreynen commentedInitially was thinking it would be an optional variable like Drupal.org's contact tab. I think you can only send 10 emails using the contact form to other Drupal users per hour. This is to limit the impact of spammers when they actually go through the trouble of signing up for an account. Usually by hour 2, the account is disabled. The needs is a little different here, but the goal is basically the same. Don't allow one user to annoy all the people who've volunteered with dozens of requests each week.
The admin form would be have a field for X number of bulk requests to volunteers and select list per hour|day|week|month. Leaving it blank would keep everything working the way it does now.
This feature would be added as part of an optional submodule so that the main Crew Connect functionality would still work without CiviCRM.