Shane Kerr wrote:
Interesting idea, although we need to take a bit of care security-wise. If we do an automatic unsubscribe, we'd need to:
- Make the bound address non-predictable (hash with a secret would work):
$ echo 'dia.uniroma3.it@ripe.net LotsOfRoutes' | md5sum 61081c9ee3097365710e7a0881f79e70
Return-Path <myasn-bounce-colitti=61081c9ee3097365710e7a0881f79e70@ripe.net>
That way I couldn't unsubscribe you by sending to your bounce address,
Hmm... yes, I hadn't thought of that. Well, I was 50% there, wasn't I? :)
Also, what about temporary delays? Do those go to the "Return-Path:"? I'd hate for someone to get unsubscribed because they exceeded their disk quota and had a bounce that made it through 30 minutes later.
I think so. But the only way to get around this is to keep state for every subscriber, right? Cheers, Lorenzo -- --------------------------------------------------------- Lorenzo Colitti Ph.D student Computer Networks research group Roma Tre University colitti@dia.uniroma3.it +39-0655173215 ---------------------------------------------------------