On Thursday 30 October 2008 23:20, Jan Wagner wrote:
> There are 2 examples ... I guess you are talking about postfwd.cf.gz. You
> initial bug report was about using the example-cfg2.txt.gz with debian
> package(1.10pre7).
> Please can you test the example-cfg2.txt.gz with the removed "$$dnsbltext"
> entry, this should be the only incompatibility against 1.10pre7.
>
> sid:/usr/share/doc/postfwd/examples# ls -la *.gz
> -rw-r--r-- 1 root root 2013 Jul 15 22:47 example-cfg2.txt.gz
> -rw-r--r-- 1 root root 1542 May  5 09:20 postfwd.cf.gz

Maybe you will give the attached config a try.

With kind regards, Jan.
-- 
Never write mail to <[EMAIL PROTECTED]>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------
# downloaded from http://hege.li/howto/spam/etc/postfwd/postfwd.conf
# check for more recent versions!

###
### Example config for postfwd 1.10pre8+
###

## Check DNS whitelists, maybe we don't need more checks

id=OK_DNSWL; \
  rbl=list.dnswl.org/^127/43200; \
  action=DUNNO

## Check (non-fqdn/ip/dynamic) HELO and (missing) reverse DNS

id=SET_HELO; \
  helo_name=!!\.; \
  helo_name=[0-9.-]{7}; \
  action=set(HIT_helo=1)

id=SET_NODNS; \
  client_name=^unknown$; \
  action=set(HIT_nodns=1)

id=REJECT_HELO_NODNS; \
  HIT_helo==1; HIT_nodns==1; \
  action=REJECT Blocked - contact [EMAIL PROTECTED] for help - Suspicious HELO 
[$$helo_name] and missing reverse DNS [$$client_address]

## Check ZEN first for immediate blocking - less queries for other lists
## See usage policy: http://www.spamhaus.org/organization/dnsblusage.html

id=REJECT_RBL_ZEN; \
  rbl=zen.spamhaus.org; \
  action=REJECT Blocked - contact [EMAIL PROTECTED] for help - zen.spamhaus.org 
RBL

## Check other DNSBLs in parallel

&&DNSBLS { \
  rbl=bl.spamcop.net; \
  rbl=dnsbl-1.uceprotect.net; \
  rbl=dnsbl-2.uceprotect.net; \
  rbl=dnsbl-3.uceprotect.net; \
  rbl=psbl.surriel.com; \
  rbl=combined.njabl.org; \
  rbl=dnsbl.ahbl.org; \
  rbl=dnsbl.sorbs.net; \
  rbl=ix.dnsbl.manitu.net; \
  rbl=dyna.spamrats.com; \
};

id=EVAL_DNSBLS; \
  &&DNSBLS; rblcount=all; \
  action=set(HIT_rbls=$$rblcount)

id=REJECT_RBL_MULTI; \
  HIT_rbls>=2; \
  action=REJECT Blocked - contact [EMAIL PROTECTED] for help - Multiple DNSBLs

## Check RHSBLs if there wasn't enough DNSBLs hit

&&RHSBLS_REVERSE { \
  rhsbl_reverse_client=dynamic.rhs.mailpolice.com; \
};

&&RHSBLS_SENDER { \
  rhsbl_sender=multi.uribl.com; \
  rhsbl_sender=multi.surbl.org; \
  rhsbl_sender=bulk.rhs.mailpolice.com; \
  rhsbl_sender=rhsbl.ahbl.org; \
  rhsbl_sender=rhsbl.sorbs.net; \
  rhsbl_sender=dsn.rfc-ignorant.org; \
};

id=EVAL_RHSBLS; \
  &&RHSBLS_REVERSE; &&RHSBLS_SENDER; rhsblcount=all; \
  action=set(HIT_rhsbls=$$rhsblcount)

id=REJECT_RHSBL_MULTI; \
  HIT_rhsbls>=2; \
  action=REJECT Blocked - contact [EMAIL PROTECTED] for help - Multiple RHSBLs 
[$$HIT_rtxt]

## See if we get any combined hits from rules before

id=REJECT_RBL_RHSBL; \
  HIT_rbls>=1; HIT_rhsbls>=1; \
  action=REJECT Blocked - contact [EMAIL PROTECTED] for help - RHSBL and DNSBL 
[$$HIT_rtxt] [$$HIT_dtxt]

id=REJECT_RBL_HELO; \
  HIT_rbls>=1; HIT_helo==1; \
  action=REJECT Blocked - contact [EMAIL PROTECTED] for help - DNSBL 
[$$HIT_dtxt] and suspicious HELO [$$helo_name]

id=REJECT_RBL_NODNS; \
  HIT_rbls>=1; HIT_nodns==1; \
  action=REJECT Blocked - contact [EMAIL PROTECTED] for help - DNSBL 
[$$HIT_dtxt] and missing reverse DNS [$$client_address]

id=REJECT_RHSBL_HELO; \
  HIT_rhsbls>=1; HIT_helo==1; \
  action=REJECT Blocked - contact [EMAIL PROTECTED] for help - RHSBL 
[$$HIT_rtxt] and suspicious HELO [$$helo_name]

id=REJECT_RHSBL_NODNS; \
  HIT_rhsbls>=1; HIT_nodns==1; \
  action=REJECT Blocked - contact [EMAIL PROTECTED] for help - RHSBL 
[$$HIT_rtxt] and missing reverse DNS [$$client_address]

## Finally greylist all lesser hits.
##
## A more DNSBL friendly way would be to greylist everything suspicious
## before DNS checks. Currently this requires you to setup some postfix
## tables before postfwd is called, since greylisting can be only done last
## in postfwd (action always exits processing).

id=GREY_HELO; HIT_helo==1; action=check_postgrey
id=GREY_NODNS; HIT_nodns==1; action=check_postgrey
id=GREY_RBL; HIT_rbls>=1; action=check_postgrey
id=GREY_RHSBL; HIT_rhsbls>=1; action=check_postgrey


##
## This example is free to use as per BSD license:
##
## Copyright (c) 2008, Henrik Krohns <[EMAIL PROTECTED]>
## All rights reserved.
## 
## Redistribution and use in source and binary forms, with or without 
modification,
## are permitted provided that the following conditions are met:
## 
##  * Redistributions of source code must retain the above copyright
##    notice, this list of conditions and the following disclaimer.
##  * Redistributions in binary form must reproduce the above copyright
##    notice, this list of conditions and the following disclaimer in
##    the documentation and/or other materials provided with the
##    distribution.
##  * Neither the name of the authors nor the names of his contributors
##    may be used to endorse or promote products derived from this
##    software without specific prior written permission.
## 
## THIS SOFTWARE IS PROVIDED BY ME ``AS IS'' AND ANY EXPRESS OR IMPLIED 
WARRANTIES,
## INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND 
FITNESS
## FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL BE LIABLE FOR ANY 
DIRECT,
## INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 
(INCLUDING, BUT
## NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 
DATA, OR
## PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF 
LIABILITY,
## WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR 
OTHERWISE)
## ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
## POSSIBILITY OF SUCH DAMAGE.
##

Attachment: pgpEhgn4OYJ48.pgp
Description: PGP signature

Reply via email to