RE: Bogus Undesirable Messages

  • From: "Jeff Bishop" <jeff@xxxxxxxxxxxxxx>
  • To: <blindcasting@xxxxxxxxxxxxx>
  • Date: Sun, 2 Apr 2006 09:32:15 -0700

I will try to see if this is possible. I am not sure at what point it
examines blocking of the domains though Steve...  I am very close to closing
the list. 

-----Original Message-----
From: blindcasting-bounce@xxxxxxxxxxxxx
[mailto:blindcasting-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Holmes
Sent: Sunday, April 02, 2006 1:27 AM
To: blindcasting@xxxxxxxxxxxxx
Subject: Bogus Undesirable Messages

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Suggestion here.

Everyone of the messages I looked at closely that have this melicious
content have the following content in the message header.  Perhaps you could
filter out or ban this domain.

Received: from dbmail-mx1.orcon.net.nz (loadbalancer1.orcon.net.nz
[219.88.242.3])
        by turing.freelists.org (Avenir Technologies Mail Multiplex) with
ESMTP

Does this list have any lagitimate users in the orcon.net.nz domain? If not,
just block that domain.  Every message with this profanity and Eloquence
savitage phrases came from this domain or at least have this domain
appearing early in the routing sequence.

Just expand the headers on any of these e-mails and you'll see what I mean.

- --
HolmesGrown Solutions
The best solutions for the best price!
http://ld.net/?holmesgrown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFEL4rvWSjv55S0LfERAy6QAJ95mA4zkFoPo84zOYlCvXZtdWv0ZwCgre7B
D/OdRvlVVaFLP3Vl/HI+nlw=
=gEb6
-----END PGP SIGNATURE-----

Other related posts: