You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Charles Gregory <cg...@hwcn.org> on 2004/03/25 19:34:03 UTC
Bogus Received headers
Hallo!
Equally applicable to viruses and spam:
I am seeing bogus received headers like the following. We are 'hwcn.org',
of course, but the inside the parentheses domain is not hwcn.org related.
I believe this means they have tried to 'HELO' as hwcn.org, but RDNS found
their real domain name?
Received: from hwcn.org (h24-81-114-183.vc.shawcable.net [24.81.114.183])
by host.hwcn.org (Postfix) with ESMTP id CCACE48233
for <__...@hwcn.org>; Thu, 25 Mar 2004 04:14:58 -0500 (EST)
Would a test like the following work okay?
header FAKHELO Received =~ /hwcn.org \(.*[(?!199\.212\.94\.[0-9]+).*]\)/i
(where 199.212.94.? is our class C for the negative look-ahead)
Or would I get false positives on this from badly configured mail
clients? I can see not doing it the other way around. But particularly
with the latest batch of viruses, this is a combination I wouldn't mind
'zapping'.....
- Charles
Re: Bogus Received headers
Posted by "Keith C. Ivey" <kc...@cpcug.org>.
Bart Schaefer <sc...@zanshin.com> wrote:
> Good in theory, but look-ahead has to be a fixed-length string, so you
> can't have [0-9]+ in there.
You're thinking of look-behind. A look-ahead doesn't have to
be fixed-length.
--
Keith C. Ivey <kc...@cpcug.org>
Washington, DC
Re: Bogus Received headers
Posted by Steve Thomas <li...@sthomas.net>.
On Thu, Mar 25, 2004 at 01:34:03PM -0500, Charles Gregory is rumored to have said:
>
> I am seeing bogus received headers like the following. We are 'hwcn.org',
> of course, but the inside the parentheses domain is not hwcn.org related.
> I believe this means they have tried to 'HELO' as hwcn.org, but RDNS found
> their real domain name?
Yep, it's a faked helo. I just added a couple of acls to our exim config to 550 any server using a HELO or EHLO of either our domain name or our server's IP address. Almost 350 rejects so far (~14 hours). Looking through the logs, they're almost all from cable or dsl customers. Ya think it was spammers using hijacked machines? Nahh..
--
"He would make a lovely corpse."
- Charles Dickens (1812-1870)
Re: Bogus Received headers
Posted by Bart Schaefer <sc...@zanshin.com>.
On Thu, 25 Mar 2004, Charles Gregory wrote:
> header FAKHELO Received =~ /hwcn.org \(.*[(?!199\.212\.94\.[0-9]+).*]\)/i
>
> (where 199.212.94.? is our class C for the negative look-ahead)
Good in theory, but look-ahead has to be a fixed-length string, so you
can't have [0-9]+ in there.
Also you need to backslash the outer set of square brackets.
I think
header FAKHELO Received =~ /hwcn.org \(.*\[(?!199\.212\.94\.)[0-9]+.*\]\)/i
might do it.