From: Andrew Gierth (andrew@erlenstar.demon.co.uk)
Date: Fri Nov 05 1999 - 11:49:17 CST
>>>>> "Charles" == Charles Lindsey <chl@clw.cs.man.ac.uk> writes:
Charles> But I am not sure what you gain from those parameters. They
Charles> all have the same BI (they are all the same spam).
When issuing NoCeMs, it's normal for one notice to list articles from
many different spams.
Charles> What other than 'hide' do you want?
NoCeM allows "show", though this isn't being used AFAIK; the idea of
that is to allow pseudo-moderated groups, where the moderator issues
"show" notices listing those articles that he approves. I think the
generic Unix client allows this, though the on-spool implementations
only process "hide" notices.
Charles> And can someone please show me how the same example would
Charles> appear in accepted NOCEM syntax (or point me at the NOCEM
Charles> RFC).
NoCeM spec can be found at Cancelmoose[tm]'s site: http://www.cm.org
In NoCeM form that would look like (I'll use one of mine from a real
spam as an example):
>Path: ...!news-out.riddles.org.uk!annihilator-nocem
>From: Annihilator-1@erlenstar.demon.co.uk
>Subject: Annihilator New Binary-EMP Report binnew.19991105173145 @@NCM
>Newsgroups: news.lists.filters,alt.nocem.misc
>Followup-To: news.admin.nocem
>Date: Fri, 05 Nov 1999 11:31:46 -0600
>Message-ID: <nocem-binnew-19991105173146$3529@news-out.riddles.org.uk>
>
[boilerplate text with link to www.cm.org and human-readable explanation]
>
>-----BEGIN PGP SIGNED MESSAGE-----
>
>@@BEGIN NCM HEADERS
>Version: 0.9
>Issuer: annihilator-1@erlenstar.demon.co.uk
>Type: spam
>Action: hide
>Notice-ID: binnew.19991105173145
>Hierarchies: alt,alt.binaries
>Count: 15
>@@BEGIN NCM BODY
># intnet.net 207.90.1.201 Rk7JmPf/EEWeDEcsKiEK0A== 21.21/1
><8e75.b03a.35c@one> alt.binaries.erotica
> alt.binaries.erotica.breasts
># intnet.net 207.90.1.201 Rk7JmPf/EEWeDEcsKiEK0A== 21.21/1
><8e75.b040.19a@one> alt.binaries.erotica.butts
> alt.binaries.erotica.sex.in.the.morning
># intnet.net 207.90.1.201 Rk7JmPf/EEWeDEcsKiEK0A== 21.21/1
><8e75.b045.2a8@one> alt.binaries.pictures.erotica
> alt.binaries.pictures.erotica.amateur
[rest of entries snipped]
>@@END NCM BODY
>
>
>-----BEGIN PGP SIGNATURE-----
>Version: 2.6.3i
>Charset: noconv
>
>iQBVAwUBOCMUgQFKZ9wCIW3ZAQGNiQH8CAUs56kZw9aUHJmYVHbb+Gba9qtIgFnZ
>PYM9TrdPbaMOhw9PaX4BcZwp+TDjwpKMzfS3d3O6Jx2FxxzdByIy1A==
>=BDHv
>-----END PGP SIGNATURE-----
Notes on the above:
The "Hierarchies" header is non-standard and not used by clients
AFAIK; it's there so that I can test my batching code that atttempts
to group entries together by hierarchy so that I can support different
NoCeM groups for different hierarchies (e.g. there's a de.* group for
NoCeMs).
The other headers in the NCM HEADERS block are all required by the
spec.
The # lines are comment lines; I include the origin information as
deduced (accurately or otherwise) from the Path, the NNTP-Posting-Host,
the ID of the spam within my correlation database, and the BI and time
interval (i.e. 21.21/1 means that the BI of 21.21 was reached within
only one day).
-- Andrew.