Skip to content
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

Open
billwambua opened this issue Oct 5, 2017 · 4 comments
Open

Feature Request: SPAM List(BlackList) #122

billwambua opened this issue Oct 5, 2017 · 4 comments

Comments

@billwambua
Copy link
Member

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

@alxndrsn
Copy link
Contributor

alxndrsn commented Nov 1, 2017

Proposed solutions

1. Automatically ignore:

  • messages from shortcodes (e.g. 60396)
  • messages from non-numeric senders (e.g. TELKOMSEL, one2one)

Drawbacks

  • other messages form the operator may be ignored by mistake, e.g.
You are low on credit, please top up.

2. Manually-configured ignore list

On a per-installation basis, configure medic-gateway to ignore numbers in a list configured on the handset.

Drawbacks

  • need to make a UI for maintaining the list

3. Synched ignore list

Synchronise a list of numbers to ignore for incoming messages between medic-gateway and its associated server.

Advantages

  • can view and manage the ignore list on the server

Drawbacks

  • have to introduce handling for ignore lists into the protocol
  • have to decide how often to download ignore list from the server

4. Per-operator ignore list

  • maintain lists of numbers to ignore for different mobile operators around the world
  • either
    • detect the mobile operator at startup, and maintain an in-memory ignore list
    • detect the mobile operator at install, and add associated numbers to the manually-configured ignore list

Ignored?

A simple fix right now would be to add a new Status for WtMessages called IGNORED. Messages which are ignored would appear on the handset, but not be forwarded to the server.

Extensions

  • context menu item to forward an IGNORED message to the server
  • context menu don't ignore messages from this number
  • context menu ignore messages from this number

@garethbowen
Copy link
Member

Related: medic/cht-core#3675

@lexycullen
Copy link

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.

@ranjuts
Copy link

ranjuts commented Jan 24, 2018

FYI @mukesh2006 @ashish-medic @binokaryg

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

5 participants