Re: TCPIP Services for OpenVMS V5.4 ECO1 anti spam feature

From: Jonathan Boswell (jsb.NOSP_at_M.cdrh.fda.gov)
Date: 05/29/04 

Date: Fri, 28 May 2004 18:40:47 -0400

"sol gongola" <sol@adldata.com> wrote in message
news:40B78885.D12131D1@adldata.com...
> The smtp relay sending you the email is 200.118.109.122. That is the relay
> connecting to your alpha that is controllable with good-client/bad-client.

Oh rats. That explains why it's not working. So by "client", HP really
means "last relay". This is useless in my present circumstance since I have
never seen the outblaze.com spammers use the same relay twice. But their
email client IP address is visible in the email headers (farther down) and
they only use a few IP addresses which could easily be blocked if TCPIP
Services had this feature.

>On TCPIP V5.1 the other "Received: from" lines aren't usable for blocking.
> I am not sure about later version of TCPIP.

Rats rats rats! I'm using 5.4 ECO1, and your comment would explain my
server is passing all this spam. Virtually none of the relays outblaze.com
uses are listed on blackhole lists I have checked.

> If you want to block "ranamail.com", you should be using
"Reject-Mail-From"
> and specify something like:
> Reject-Mail-From: *ranamail*

What's ranamail.com? If that's just your example, can I Reject-Mail-From:
*.outblaze.com and expect it to work? This address
(something.or.other.outblaze.com) is always visible (lower down) in the spam
headers.