Barry Warsaw writes:

 > I suppose you could also have each mailing list publish a pubkey and  
 > require that messages be encrypted with that pubkey in order to get  
 > posted.

Hey, that's great, we can update RFC 2369 with a List-Pubkey header!
I bet Gmane learns to use it within a week after proposal!<wink>

 > Sure, spammers could use the same key to sign spam, but I wonder if
 > that wouldn't be more work than is worthwhile for a botnet.

Don't bet on it.  As Brad points out, a botnet has effectively
unbounded resources per message.  If this becomes a standard feature
of any software as widely distributed as Mailman, some spammer will
decide to exploit it, and there goes the neighborhood.

_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Reply via email to