Why won't MBAM detect Spector Pro?

[G. Morgan]

Why won't MBAM detect Spector Pro?

I know two of you that would know. What's the deal?

[G. Morgan]

never mind. I canceled it, but I guess it's already out there.

[Jagg]

On Mon, 13 Jun 2011 19:08:30 -0500, G. Morgan wrote:

> never mind. I canceled it, but I guess it's already out there.

You can onbly cancel posts if your ISP supports it and most don't.

[VanguardLH]

Jagg wrote:

> G. Morgan wrote:
>
>> never mind. I canceled it, but I guess it's already out there.
>
> You can onbly cancel posts if your ISP supports it and most don't.

Eternal-September, the newsgroup provider used by Morgan, says they do
honor cancels but under the conditions that the poster be using the same
ES account through which they made the original post. That they support
cancels doesn't mean the NNTP client issues it correctly but the process
is rather simple and it would have to be a really dumb or lazy
programmer of the NNTP client that doesn't know how to issue posts to
the control.cancel newsgroup with the appropriate content to *request* a
cancel.

I believe cancels are not peered between NNTP servers. That's because
the poster must submit the cancel to the same NNTP server to which they
submitted the original post.

The FAQ at Eternal-September is incredibly sparse and does not mention
support or lack thereof for cancel requests. Here's what I found under
their Terms Of Use (rather than under their FAQ):

_No control messages_

No control messages may be posted through news.eternal-september.org
with the following exceptions:

1. Cancel and supersede messages for your own articles that have been
posted through Eternal-September
2. newgroup and rmgroup control messages for de.alt.*

*You should familiar with de.alt.admin conventions and proceedings*

3. Control messages to free.*

So it appears ES does support cancels submitted to their NNTP server
against posts from the SAME poster that also submitted the original post
through their NNTP server.

Just because a particular NNTP server honors cancels doesn't mean your
article will disappear from other NNTP servers. Peering is usually very
quick. By the time you navigate the menus in your NNTP client to figure
out how to submit a cancel, your original post has probably already been
peered to other NNTP servers. That is, you'll always be late in getting
a cancel submitted. If a post disappears from the NNTP server (it's no
longer in either the overview or article databases), it might also
disappear from a peered NNTP server but don't count on it. Even if the
peering NNTP servers remove the deleted post, there are many web-to-NNTP
gateways (often for forums leeching from Usenet to provide a webnews-
for-boobs interface to Usenet) that archive the posts and which will
retain your article regarding of you cancelling it from the NNTP server
that you used to add your post.

If you look at posts submitted through ES, there is a Cancel-Lock
header. This is encoded to the poster, their account, and perhaps the
server. You cannot cancel Morgan's post because you don't have the
login credentials needed to logon under that account. When Morgon logs
into the ES server and submits the cancel, that header gets used to
qualify that he has permission to cancel his post. If cancels are not
working to remove your posts from their NNTP server, contact them to
report the problem as they claim to support cancels.

I no longer have an ES account so I cannot logon there and download
their control.cancel newsgroup. I would doubt it's peered between NNTP
servers as the cancels target the same NNTP server as through which the
original post was submitted. Since Morgan issued a cancel, and since he
logs onto his ES account with his NNTP client, he can go look at the
control.cancel newsgroup to see if his cancel request got there.

Might work, might not. If it works on your NNTP server doesn't mean
your post disappears elsewhere.