I said:
I will isolate the "offensive" content
Well, we have a new "offensive" string to avoid: "c a s i o" without
interstitial spaces.
Clif made the mistake of using the word "occa sionally" (without the
interstitial space). Serves him right, really! He shoulda just wrote
"sometimes".
Seriously, someone needs to inform MS that their spam filter (I ass-u-me) is
bad. Bad for business, since MS directs users to rely on the MS "discussion
groups" for tech support.
FYI, I want to reiterate that the removal of articles can happen minutes
later. Even I got fooled initially when my first test with Clif failed
posting succeeded. "Succeeded" meant: the header appeared in OE. But try
opening the message (a separate NNTP request) some time later, and that's
when we might get the "deleted from server" message. I didn't! Oh yeah:
wait some time longer (5 min, in one case), reset the NG OE (i.e. flush
headers and bodies), then read headers again, and voila! The message is no
longer there.
Usually, it seems that the article was never posted at all because we do not
even see the header in OE. But careful monitoring of the NNTP protocol
reveals that the article is accepted by the server and even assigned a
number, which is my definition of "posted". The removal simply happens very
soon thereafter, often within seconds.
But the MSnews server seems unusually busy today, so the removal delay is
quite long. This can lead to the seemingly "inexplicable" situation where
articles posted to the MSnews server appear on other NG servers (Google
Groups, MSDG, etc), but not on the MSnews server itself. Those remote sites
are simply lucky(?) to poll and pull from the MSnews server before the
article is removed.
Geesh! I just found myself scanning this text for the offensive strings
before pushing the send button. This is ridiculous!
----- original message -----