ietf-nntp anti-spam nntp extensions

[Jeff Garzik]

In order to keep up with the rising tide of spam, real-time transmission
of spam message ids to downstream sites is needed.  To that end, I am
designing anti-spam extensions to NNTP.  Here's what I've come up with:

MODE FILTER

	Notifies the server that a connecting client
	wishes to send real-time spam message ids.

FILTER <id>

	Notifies the server that article <id> is
	considered spam by the connecting client.



As implemented in INN, the following logic would be applied to each <id>
passed to the server:

	if ( <id>-in-history-database )
		attempt article cancel
	else
		add <id> to history database

Smarter implementations could also optimize by, and for, the presence of
spam cancel messages.  If a spam cancel is present in the form of
<cancel.id> in history, further processing could be avoided.  And if
<id> is not in the history database, then <cancel.id> can be added to
the database as well, to refuse the spam cancel that's almost certainly
to follow.

I used "filter" instead of "spam" in the commands so Hormel won't sue
me.  :)

Comments?
-- 
Jeff Garzik			    Typhoon, Cyclone, Diablo, and INN
Spinne USENET News Service	        Fast and efficient news feeds
http://www.spinne.com/usenet/	           News tuning and consulting