News for hackers. Stuff that matters.
Re:Most of the Amazon SES IP blacklisted by SpamCannibal by ANTSANTS on Monday April 21, 2014 @11:05AM (#7621390)
If you were to remake email from the ground up, how would you solve the spam problem while keeping it as decentralized of a system as it is now?
Re:Most of the Amazon SES IP blacklisted by SpamCannibal by gabemart on Monday April 21, 2014 @11:30AM (#7621528)
Any such discussion will be well informed by https://craphound.com/spamsolutions.txt
Re:Most of the Amazon SES IP blacklisted by SpamCannibal by dredmorbius on Monday April 21, 2014 @11:23AM (#7621490)
Engineering in a lot of reputation management and metrics would help.

There are some interesting (I'm not sure "compelling" or "strong" is necessarily the case) arguments to be made for enabling open relays and other forms of unauthenticated messaging. John Gilmore of EFF has fought that battle for a long time, and still runs an open relay on toad.com.

Signing and authentication measures (particularly on header data) have to be both standard and quick to process.

Methods which increase the costs of delivery -- pacing receipt rates from a given IP or block, can help. Being able to specify receipt priorities: high for IPs and ranges with which frequent legitimate business is transacted, very slow for most others, would also be useful. Along with a lot of built-in support for this.

Killing :80 and moving to entirely secured ports wouldn't be a bad move either.

Re:Most of the Amazon SES IP blacklisted by SpamCannibal by phunehehe0 on Monday April 21, 2014 @11:32AM (#7621543)
Maybe you mean 25 or something else? Port 80 is for HTTP. And what does a secure port mean? If you want people to be able to talk through a port you have to open it. The number doesn't matter.
Re:Most of the Amazon SES IP blacklisted by SpamCannibal by dredmorbius on Monday April 21, 2014 @06:53PM (#7624518)
Doh! Yes. :25.

By "secure port", I mean forcing encryption of all over-the-wire traffic. It's happening now in many cases with STARTTLS (modulo utter brokenness of the CA and SSL/TLS systems), but that's still only opportunistic.

And of course, encrypting payloads would be vastly preferable. Headers as well other than absolutely required for delivery.

Re:Most of the Amazon SES IP blacklisted by SpamCannibal by drpancake on Monday April 21, 2014 @11:12AM (#7621432)
Require a small fee to send an email, e.g. $0.01. Small enough not to matter for legitimate users, large enough to make spam unprofitable.

Bitcoin or some other cryptocurrency would be ideal for facilitating micro-transactions like this. Interestingly, the Hashcash concept was originally designed to fight spam, and later became one of the important ideas that made the invention of Bitcoin possible: http://en.wikipedia.org/wiki/Hashcash

Re:Most of the Amazon SES IP blacklisted by SpamCannibal by okasaki on Monday April 21, 2014 @11:17AM (#7621458)
That wouldn't work for mailing lists.
Re:Most of the Amazon SES IP blacklisted by SpamCannibal by wpietri on Monday April 21, 2014 @11:35AM (#7621562)
One could add a proof of permission model to that to cover things like mailing lists and other regular sources of email. Something like:

I sign up for a mailing list.

The mailing list mail server contacts my mail server.

My mail server presents to me a request for free delivery.

I approve it.

My mail server gives the mailing list server a secret token.

Each mailing list message includes proof that the message has been blessed by the sender and that the sending server knows the token.

Re:Most of the Amazon SES IP blacklisted by SpamCannibal by jrockway on Tuesday April 22, 2014 @05:54AM (#7626697)
What stops this server from then using that token to spam you?
Re:Most of the Amazon SES IP blacklisted by SpamCannibal by wpietri on Tuesday April 22, 2014 @07:35PM (#7631168)
I'd do it with revocation.

Right now I give out tagged addresses to most vendors, and I know others do it for lists. When a tag goes bad, I just route any further mail to my spam trainer.

Re:Most of the Amazon SES IP blacklisted by SpamCannibal by jrockway on Tuesday April 22, 2014 @08:08PM (#7631279)
But that means for every legitimate mailing list you're on, you get one spam. And you lose the legitimate mailing list just because their token got compromised.

Dunno, I feel like we should just charge for mailing lists too. Or use usenet!

Re:Most of the Amazon SES IP blacklisted by SpamCannibal by wpietri on Thursday April 24, 2014 @02:18AM (#7638754)
If I can get it down to one spam each time a mailing list server is compromised, I'm ok with that.

Even with a charging scheme, some spam will still happen. Give the amount of BTC stolen so far, and given the number of compromised computers that could be used to generate cash, looks like there will be plenty of money to spend on sufficiently profitable spam.

Re:Most of the Amazon SES IP blacklisted by SpamCannibal by Simucal on Monday April 21, 2014 @11:36AM (#7621571)
I think the fee could be applied only to unsolicited emails. If I have a particular email address whitelisted then it will get through my gateway with no fee attached. However, if it is an unsolicited email from someone not on my whitelist it will be required to have some small fee attached to get past my filter.

I've seen some suggestions that instead of using money you could use some proof-of-work computation. This is something we could scale the difficulty factor of as computing power increased. Something that takes, say, an average computer 30 seconds (or longer) to calculate. It will attach this proof-of-work to the email.

Re:Most of the Amazon SES IP blacklisted by SpamCannibal by bluedino on Monday April 21, 2014 @12:06PM (#7621742)
Mailing lists wouldn't need to, or couldn't exist in this new magical email system. There's a hundred other solutions out there for what mailing lists provide.
Re:Most of the Amazon SES IP blacklisted by SpamCannibal by awj on Monday April 21, 2014 @12:09PM (#7621767)
Impose the fee only on one-way communications. A responsible mailing list would have a single instance of two-way communication when asking the user to confirm that they wanted to sign up. No I have no idea how that much state should be handled in a distributed fashion.
Re:Most of the Amazon SES IP blacklisted by SpamCannibal by gnopgnip on Monday April 21, 2014 @11:48AM (#7621644)
How would a decentralized ledger handle the 100 billion emails sent a day?
Re:Most of the Amazon SES IP blacklisted by SpamCannibal by revelation on Monday April 21, 2014 @11:35AM (#7621564)
Re:Most of the Amazon SES IP blacklisted by SpamCannibal by bcoates on Monday April 21, 2014 @01:33PM (#7622353)
Separate authentication from message delivery. The problem with both spam and spam mitigation measures is that the message is considered as coming 'from' a sending system instead of the actual originator of the email.

Splitting these up converts one impossible problem into a tricky but mostly solved problem (delivery) and a hard problem that has to be addressed anyway (internet identity)

Re:Most of the Amazon SES IP blacklisted by SpamCannibal by leccine on Monday April 21, 2014 @11:07AM (#7621400)
How about a PKI system were one or more authorities can sign keys and the email server admins can approve public keys based on its combined score coming from the authorities. Authorities could be universities, engineering organizations and other non-profit entities.
Re:Most of the Amazon SES IP blacklisted by SpamCannibal by mpyne on Monday April 21, 2014 @11:46AM (#7621638)
So now people have to register identities and can't use anonymous email addresses. And it wouldn't fix the issue anyways since spammers would just use botnets of legit sender addresses.
Re:Most of the Amazon SES IP blacklisted by SpamCannibal by leccine on Monday April 21, 2014 @07:13PM (#7624610)
You are mixing up registration with registration with real data. You could still register an email address with arbitrary details and after a while you could establish a score that would grant your non-spam status. What you are confused with is that in this system there is no disposable email address. That is actually a valid concern but I don't use those so i really don't care.