4
Global SmarterMail Spam Solution
Idea shared by John Marx - 9/11/2021 at 11:29 AM
Proposed
SmarterMail is in a unique position. They have complete control over their product. They could make an API available to their customers (free of charge) that when someone reports SPAM (via a spam button everyone wants). This reporting could then handle things locally like we're all asking but ALSO have the ability for the domain, and/or server, sending the email/domain (not the actual email) to make a global anti-spam network. 

I understand some people could abuse and make a domain or email always as spam but with the right code could provide additional filtering. Almost like a spam network list.

This is to start the conversation and open it up. If anything if SmartMail could make it available for us users/admins/developres access to that magical spam button and have it save to whatever spam API network we wanted.

1 Reply

Reply to Thread
1
Inbound throttling based on IP/Domain reputation would be the better option, essentially creating a reputation system like Microsoft/Google have that looks at volume patterns. You would feed in the data from SM installs around the world (opt-in of course) then build up a database.

At the moment I don't believe SM records enough statistical data about the source of email/connection which is where the problem is. If they added the stats data we could write something that would essentially populate a rbldnsd dataset then just use that as a RBL in SM.

If they were really smart :) they would have the SM installs pushing the local volume stats data to a central system via an API, process it and update their own central database then push it out to multiple rbldnsd instances at frequent intervals e.g. every hour or so. Just requires a good level of design especially when it comes to processing large amounts of data. When the SM instance is pushing stats data to SM’s API it would only push stats data accumulated after the last time it sent data to SM to keep the requests small. SM installs could then use the RBL/URIBL’s created by SM to apply to inbound connections/emails.

You want stats like connection volume within x period, how many unknown users; you need to look at IP level and CIDR, IPv6 support along with sending domain etc


Reply to Thread