How to block TCP/IP address?

[Michael T.]

I keep getting spam from a TCP/IP address in Beijing China. Namely,
124.116.235.209.

The forged email-address (and domain name) of the sender varies, so I cannot
use either a Message Rule or the Blocked Senders List to block a specific
e-mail address.

So I am left wondering if there is a way to block all e-mail from a specific
TCP/IP address?

 

[Tom [Pepper] Willett]

This would need to be done in your firewall.

:I keep getting spam from a TCP/IP address in Beijing China. Namely,
: 124.116.235.209.
:
: The forged email-address (and domain name) of the sender varies, so I
cannot
: use either a Message Rule or the Blocked Senders List to block a specific
: e-mail address.
:
: So I am left wondering if there is a way to block all e-mail from a
specific
: TCP/IP address?
:
:
:

 

[John]

What email server are you using? You can't get Outlook to do that.
You need an antispam/content filtering software, particularly one that works
with DNSBL.

 

[Peter Durkee]

You can write a rule that deletes any message with 124.116.235.209 in the
message header.
-Peter

 

[John]

Sure if the goal is to block *that* IP only.

You can write a rule that deletes any message with 124.116.235.209 in the
message header.
-Peter

 

[Michael T.]

You can write a rule that deletes any message with 124.116.235.209 in the
message header.
-Peter

Sounds good Peter.

Is this unique to Outlook, or can I use Outlook Express 6?

I am currently running OE6, but I do have an old copy of Outlook I could use
instead.

However it appears that the "Tools" menu selection does not contain the
option "Rules and Alerts."

 

[Brian Tillman]

I keep getting spam from a TCP/IP address in Beijing China. Namely,
124.116.235.209.

The forged email-address (and domain name) of the sender varies, so I
cannot use either a Message Rule or the Blocked Senders List to block
a specific e-mail address.

So I am left wondering if there is a way to block all e-mail from a
specific TCP/IP address?

You might be able to do it with a rule that looks for "124.116.235.209" in
the headers. I thnk a better approach would be to block it on the server
end, if possible, or use a tool like SpamPal.