homepage fixes

2006-08-28 Thread Robert Felber

Setup HOWTO as well as FAQs contained a typo/error:

check_policy_service 127.0.0.1:12525

which caused a 

Aug 27 22:50:56 machine postfix/smtpd[72739]: fatal: invalid transport name:
127.0.0.1 in service: 127.0.0.1:12525

corrected it to 

check_policy_service inet:127.0.0.1:12525

Thanks to B. Hajduk for reporting.


-- 
Robert Felber (PGP: 896CF30B)
Munich, Germany


Policyd-weight Mailinglist - http://www.policyd-weight.org/


spam with perfect rDNS/HELO/sender match

2006-08-28 Thread /dev/rob0
I have a site with a small but heavily-spammed domain. I was relaying 
through a remote MX, but recently I set it up to be its own MX. I put 
in place all the usual strategies which used to take out 95% of the 
spam. I also set up amavisd-new with SA.

With all that, the spam kept coming. Perfect FCrDNS, in agreement with 
the HELO and sender domain. (In fact usually the HELO is the rDNS 
name.) Usually no suspicious patterns in rDNS, like too many numbers. 
These spammers came up mostly clean in RBL checks: maybe a spamcop or 
tqmcube or fivetensg hit, but never Spamhaus or DSBL or NJABL.

Even the content inspection missed these, because the URL's used were 
not yet in URIBL or SURBL.

I stopped the spam eventually, by check_client_access blocking the 
networks of the recidivists. (49 entries in a CIDR table.)

I also started using the Joewein.de spam domain list in 
check_{client,helo,sender}_access[1], which didn't help much with the 
clean gang, but as time goes on it's catching more.

The interesting thing here is that rDNS/HELO/sender match can at times 
be an indication of spam! That has important implications for 
policyd-weight and the antispam world in general.

I have a theory, however, on how these might be caught, and testing 
shows partially that I may be right.

I put Joewein.de in warn_if_reject check_{helo,sender}_{mx,ns}_access 
lookups, and occasionally I see only the warnings, and not the 
rejections.

That of course is not the same as a lookup of the IP address, which is 
why I say, partially. I've asked /dev/wife to write me a Perl script 
using Net::DNS to grab NS names from Joe's list, look up the IP 
addresses, and store the whole mess in a pgsql database. I don't know 
when that will be done. I might even dig into the Net::DNS and DBI 
documentation and try to code it myself.

Then ... the theory is that rDNS/HELO/sender match with the domain NS 
found in that list would be strong evidence, perhaps even proof, of 
spam. Working hypotheses are that the list of NS IP addresses will be 
very small, and that the overlap will be very high.


About the secrecy thing: I believe Joe Wein has already done some 
research along these lines, so I figured it doesn't matter. Also, 
despite being an open and archived list, we're low-profile here. I 
doubt the few clueful meta-spammers out there even know we exist.


[1] If anyone is interested in pulling this list from me, let me know. 
I've got 2 scripts which do the job, one as non-root to retrieve the 
file, and another as root to install and postmap(1) it.
-- 
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header


Policyd-weight Mailinglist - http://www.policyd-weight.org/


version update: version 0.1.13 beta-5

2006-08-28 Thread Robert Felber
changes:

scoring:

-   CL_IP_NE_HELO was not DNSBL influenced.

When the IP of the HELO argument couldnt be verified against the
Client IP we just gave the bad score of @client_ip_eq_helo_score
without adding eventually RBL scores.

-- 
Robert Felber (PGP: 896CF30B)
Munich, Germany


Policyd-weight Mailinglist - http://www.policyd-weight.org/


Re: spam with perfect rDNS/HELO/sender match

2006-08-28 Thread Robert Felber
On Mon, Aug 28, 2006 at 09:37:24AM -0500, /dev/rob0 wrote:
 I put Joewein.de in warn_if_reject check_{helo,sender}_{mx,ns}_access 
 lookups, and occasionally I see only the warnings, and not the 
 rejections.
 
 That of course is not the same as a lookup of the IP address, which is 
 why I say, partially. I've asked /dev/wife to write me a Perl script 
 using Net::DNS to grab NS names from Joe's list, look up the IP 
 addresses, and store the whole mess in a pgsql database. I don't know 
 when that will be done. I might even dig into the Net::DNS and DBI 
 documentation and try to code it myself.
 
 Then ... the theory is that rDNS/HELO/sender match with the domain NS 
 found in that list would be strong evidence, perhaps even proof, of 
 spam. Working hypotheses are that the list of NS IP addresses will be 
 very small, and that the overlap will be very high.

I currently understand jowein as RHSBL list, is that correct?
And, we receive the NS record of each domain, and compare it against the
NS record of the Sender|HELO|Client Domain?

In short - we need a RBL which lists spammer's NS.


-- 
Robert Felber (PGP: 896CF30B)
Munich, Germany


Policyd-weight Mailinglist - http://www.policyd-weight.org/