Test

Oops. If this message went through why was my other post stopped by a filter?

--
Mike Walsh

On Mon, 11 Feb 2008 10:34:35 -0500, Mike Walsh
<spam_sucks@bellsouth.net> wrote:

>
>
>Oops. If this message went through why was my other post stopped by a filter?

What other post, what filter? Sometimes news servers just
have glitches and it takes longer for a post to show up.

If it was stopped by a filter it would depend on the filter
parameters, if you had posted from the same account, same IP
address, then the only thing a filter would look at is the
header and body of the message, if it had registered as X #
of hits on a spam filter based on the words used, for
example.

kony wrote:
>
> On Mon, 11 Feb 2008 10:34:35 -0500, Mike Walsh
> <spam_sucks@bellsouth.net> wrote:
>
> >
> >
> >Oops. If this message went through why was my other post stopped by a filter?
>
> What other post, what filter? Sometimes news servers just
> have glitches and it takes longer for a post to show up.
>
> If it was stopped by a filter it would depend on the filter
> parameters, if you had posted from the same account, same IP
> address, then the only thing a filter would look at is the
> header and body of the message, if it had registered as X #
> of hits on a spam filter based on the words used, for
> example.

When I tried to respond to Jethro the message was blocked by a "Post Filter". After the test worked I responded to GT instead and it worked. There is probably a filter on Bell South's server. I never had it happen with my old ISP.

--
Mike Walsh