New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: SPAM List(BlackList) #122
Comments
Proposed solutions1. Automatically ignore:
Drawbacks
2. Manually-configured ignore listOn a per-installation basis, configure medic-gateway to ignore numbers in a list configured on the handset. Drawbacks
3. Synched ignore listSynchronise a list of numbers to ignore for incoming messages between Advantages
Drawbacks
4. Per-operator ignore list
Ignored?A simple fix right now would be to add a new Extensions
|
Related: medic/cht-core#3675 |
Hi Alex! We are running into a lot of issues and looping messages here in Indonesia, even though we've added numbers to the black list. I really think option number one (automatically ignore) is the best option. Our partner specifically requested this. I see your drawback in being that they may miss a message about the low credit. Wouldn't the partner still see this message on their phone? In the platform there is so much spam that it's not helpful viewing a "low credit" message in the application. Most messages aren't even viewed/clicked on by the team because everything is buried in spam messages. |
FYI @mukesh2006 @ashish-medic @binokaryg |
In the case of message loops, if they are caught soon after they start and the offending number added on the
Outgoing Deny List
in the webapp, it can be contained.But in the case of when the problem is not noticed until some time after, even after employing the
Outgoing Deny List
, the SMSs from the provider takes some time to stop: 3-4 days(in some projects they don't and necessitate changing of the SIM card).I think a blacklist would act well to be a first line measure against these message loops and as a measure to stop the residual incoming messages from the provider after employing the
Deny List
on the webapp.We may not be able to implement this in cases where the gateway is in the partners possession well sometimes, but we could always guide them on how to do it. I think it is more advantageous than not, to have this feature.
cc @alxndrsn @ngamita
The text was updated successfully, but these errors were encountered: