I stumbled across the SpamAssassin protocol definition and its examples while implementing a .net client... Correct me if misunderstood anything, but aren't they kind of misleading or just wrong if you have a look at the examples?
First and second one is absolutely fine, but I've already got a question about the third one: One would expect SET as the header you have to specify when learning/reporting ham or spam. Having a look to the third example there is a ‘remove’ in the SET header which is kind of confusing to me (expected a ‘remote’ or so to tell SpamAssassin to report to a ‘remote’ network like Razor). Even more confusing, the fourth example: ‘Revoke a ham message’. Why is the message-class spam? Why is it set local? Wouldn’t this cause SpamAssassin to learn this message as spam for our ‘local’ bayes? The REMOVE header is set to ‘remove’, I would expect a ‘remote’ again, so one would interpret it as ‘Remove message from remote network’. To learn a message as spam: TELL SPAMC/1.3\r\n Message-class: spam\r\n Set: local\r\n To forget a learned message: TELL SPAMC/1.3\r\n Remove: local\r\n To report a spam message: TELL SPAMC/1.3\r\n Message-class: spam\r\n Set: local, remove\r\n To revoke a ham message: TELL SPAMC/1.3\r\n Message-class: spam\r\n Set: local\r\n Remove: remove\r\n Is this a documentation issue or did I mixed up anything here? Daniel -- View this message in context: http://old.nabble.com/SpamAssassin-protocol-examples-tp31001675p31001675.html Sent from the SpamAssassin - Dev mailing list archive at Nabble.com.
