Today I would like to give you an idea on how to implement a spam system that can reduce some kind of spam.
- These people probably will have issues removing a person from a mailing list, therefore they will tend not doing it, unless they have an advantage.
- Is really annoying sending an e-mail to 10 contacts and receive 8 mail-delivery-subsystem errors.
My approach is dividable in two directions that have to be implemented as features from the e-mail provider:
- Be able to filter out all e-mails from a specific account or domain (and a lot of mail-provider already implement this, ie: gmail with filters)
- Be able to set a “fake” mail-delivery-subsystem error (and this is the innovative part of my idea)
The “fake” mail-delivery-subsystem error
The e-mail server of the user will have to check the user’s “blacklist” before declaring the user as existent. If the user has put the sender e-mail address in the blacklist, the e-mail server will have to decline the e-mail with an error.
Why will this work
This approach will work for multiple reasons:
- If the e-mails are sent directly by an operator, he will receive the error and she will understand that something is not right.
- If the e-mails are sent directly by an operator, she will be bothered by the amount of mail-delivery-subsystem error he will receive and will try to stop sending e-mails that are bounced back
- If the e-mails are sent by an operator using a mailing-list program, probably the program itself will remove the addresses that return a mail-delivery-subsystem error
I think it does. We have an overhead for each mail received (and probably this overhead could be reduced due to optimizations) but, in the long run, way less spam e-mails will be sent, so the servers will be less busy parsing spam e-mails.