Block mail from IP address

  • Thread starter Thread starter Noël Burgess
  • Start date Start date
N

Noël Burgess

Using OL2K on XP Pro.
Is there any way I can set up a rule to delete mail originating from a
specified IP address? I receive 30-40 mails a day from two or three IP
addresses, all of them infected with Yaha-R virus. Subject lines, text and
reply-to fields vary.

Complaints to the originating mail server's abuse service have had no
effect. And after six weeks I'm fed up.

Noël
 
Start a new rule from a blank - don't use a template

There are options such as Junk sender - but the messages must all come from named domains so you need to identify the
Better option might be to look for the ip addresses 'in the message header' since they seem to be consistent

then continue defining and 'permanently delete' them

HT

Reg
 
You're better off using a program such as mailwasher (nmailwasher.net) to
filter your mail before you get it with outlook.
 
Thanks, Diane. Ill check it out.

Noël
Diane Poremsky said:
You're better off using a program such as mailwasher (nmailwasher.net) to
filter your mail before you get it with outlook.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)





Noël Burgess said:
Using OL2K on XP Pro.
Is there any way I can set up a rule to delete mail originating from a
specified IP address? I receive 30-40 mails a day from two or three IP
addresses, all of them infected with Yaha-R virus. Subject lines, text and
reply-to fields vary.

Complaints to the originating mail server's abuse service have had no
effect. And after six weeks I'm fed up.

Noël
Click to expand...
Click to expand...
 
Thanks, Reg. I had overlooked in the rules wizard the option to check for
specified words in the header. So my new rule deletes all messages
originating from 80.196.240.27. Pity the poor guy who doesn't know he's
spreading havoc.

Noël

RegUK said:
Start a new rule from a blank - don't use a template.

There are options such as Junk sender - but the messages must all come
Click to expand...
from named domains so you need to identify them
Better option might be to look for the ip addresses 'in the message
Click to expand...
header' since they seem to be consistent.
 
Back
Top