Re the discussion in mozilla bugzilla about camram and hashcash integration approaches. I think perhaps what the mozilla guys will want to hear is something mozilla centric. My thought is the mozilla-centric way to express the full CR camram approach is to talk about the netscape spam-filter as the spam-filter, the mozilla-mail spam marked messages as the spam-trap. (They are not actually in a separate folder (by default -- perhaps you can override this to make them be so), but there are folder view options where you can hide them. You can edit and so train this by changing the view so you can see both spam and non spam marked messages turning on clicking on the little spam icon to to undo false positives, and clicking to mark as spam for false negatives. (Well actually you can do false negatives in spam-free view). Could this view be used as the spam-trap? Seems maybe could. Getting out of the spam trap would just be a subsequent stamp would promote it from likely spam to non-spam. The last part would be issuing of DSN or whatever notifications and processing of the responses. I suspect this last one is what would most likely make mozilla as a MUA feel this was more than they wanted to go direct into a MUA, rather than as 3rd party add on because it results in mixed human/machine readable mail messages being sent which are not (at this point) RFC compliant. If we could move these notifications towards standardization, perhaps. For standardization the machine processability seems ok. But human readability seems more challenging -- what goes there (up to implementation?) and presumably on the scale of mozilla there can not be direct web pointers there due to overload / centralization, so all that could go there would be download software pointers, perhaps. Just thinking aloud to think about how one would go towards mozilla supporting camram (and bare hashcash). Adam On Sun, Apr 04, 2004 at 07:48:56PM -0700, bugzilla-daemon@xxxxxxxxxxx wrote: > In the long run, yes. I was only offering offering to work with the > camram code as a proof of concept. after all, it is some 6000 odd > lines of Python not including CRM114, emailrelay, and hashcash. I > just thought that reusing existing code and pulling all of the anti > spam functionality out as totally separate some process would have > some benefits. Especially since I figure it might take some time to > translate all of the camram functionality into whatever language > mozilla uses.