"N. Miller" wrote:

On Wed, 22 Mar 2006 05:08:30 -0800, Bill wrote:



Okay, BUT...

Somewhere, surely, in "details" and/or "message sender" there is something
that "block sender" picks up on (like the senders name/address) that derails
it from ever getting in the receivers in box.

All I want is to be able to do the same to the sender's ISP, e.g. block
everything, regardless of name, address, etc., from him, the same as I can
now do to a single e-address/sender.

You wrote (that), "... have to be willing to learn how to run your own MTA
to do
this. Most people aren't."

I'm a writer. That's all. Learning how to do anything with a computer is a
chore and usually over my head. OE has made a lot of things easy, like
blocking a sender. Just carry it one more step on.

You also said, "... This can't be done at the client level. By the time MS
Outlook express is pulling email from the POP3 or IMAP server, the message
has been received. You can't block it, now; all you can do is divert suspect
email to a
special folder, or delete it. ...."

Okay, so OE does all that, but why can't I divert anything, any message,
that includes a designated ISP in the "details" or "message headings" as well
as a designated e-address/sender with the simple click of a key?

And, finally, "... MSFT shouldn't, and likely won't consider it. Ask MSFT to
add a Naive Bayesian filter to the next iteration of Outlook Express; that
would be more feasible."

I don't have a clue as to what you said. Who is MSFT and what is a Naive
Bayesian filter? Remember, I'm a writer, therefore computer stupid. Tell me
what to ask them for (and where to contact them) and I'll ask, nicely.

Come to think of it, maybe I should have used "divert" instead of "block."
There must be a difference.