Vexim/ Exim - Spam Score wird nicht beachtet!

Postfix, QMail, Sendmail, Dovecot, Cyrus, Courier, Anti-Spam
benedelux
Posts: 36
Joined: 2005-03-05 15:35
Location: im Allgäu...

Vexim/ Exim - Spam Score wird nicht beachtet!

Post by benedelux » 2005-11-30 13:37

Hallo Zusammen,

ich habe schon vor längerem mal unter meiner Debian Kiste Exim4 mit Vexim nach dem DebianHowTo installiert.

Nur neuerdings habe ich wohl das Problem das Spamassassin die Score von Vexim nicht mehr beachtet. Hier mal ein kleiner Auszug aus ner Spam e-Mail:

Code: Select all

x-sender: sausqdk@linkamerica.net
x-receiver: info@xxxxxxxx.de
Received: from exchange-pop3-connector.com ([192.168.1.7]) by srv-ex01.xxxxxxxxx.de with Microsoft SMTPSVC(6.0.3790.1830);
	 Wed, 30 Nov 2005 12:31:08 +0100
Return-path: <sausqdk@linkamerica.net>
Envelope-to: info@xxxxxxxxx.de
Received: from ron59-1-82-225-127-94.fbx.proxad.net ([82.225.127.94] helo=dujardin)
	by mail.xxxxxxxxx.de with smtp (Exim 4.50)
	id 1EhQ6H-0008M8-MZ
	for info@xxxxxxxx.de; Wed, 30 Nov 2005 12:26:14 +0100
MIME-Version: 1.0
Content-Type: multipart/related;
        boundary="_NextPart_000_0001_2da3067a.669ed962"
MessageId: <000d$01ccc13f$034a3707@dujardin>
Date: Wed, 30 Nov 2005 11:26:07 +0000
To: sausqdk@linkamerica.net
From: "Devin Rowland" <sausqdk@linkamerica.net>
Subject: Re[9]
X-Antivirus: avast! (VPS 0548-0, 29/11/2005), Outbound message
X-Antivirus-Status: Clean
X-Spam-Score: 6.2 (++++++)
X-Spam-Report: Software zur Erkennung von "Spam" auf dem Rechner
	mail.xxxxxxxx.de
	hat die eingegangene E-mail als mögliche "Spam"-Nachricht identifiziert.
	Die ursprüngliche Nachricht wurde an diesen Bericht angehängt, so dass
	Sie sie anschauen können (falls es doch eine legitime E-Mail ist) oder
	ähnliche unerwünschte Nachrichten in Zukunft markieren können.
	Bei Fragen zu diesem Vorgang wenden Sie sich bitte an
	the administrator of that system
	Vorschau: [...] 
	Inhaltsanalyse im Detail:   (6.2 Punkte, 5.0 benötigt)
	Pkte Regelname              Beschreibung
	---- ---------------------- --------------------------------------------------
	0.7 HTML_SHORT_LENGTH      BODY: Sehr, sehr kleiner HTML-Teil
	0.0 HTML_MESSAGE           BODY: Nachricht enthält HTML
	1.2 MIME_HTML_ONLY         BODY: MIME-Nachricht besteht nur aus HTML
	0.2 HTML_90_100            BODY: Nachricht besteht zu 90-100% aus HTML
	3.1 HTML_IMAGE_ONLY_04     BODY: Außer Bildern nur 0-400 Zeichen Text
	0.8 MIME_BASE64_BLANKS     RAW: Ã?berflüssige Leerzeilen bei der base64-Kodierung
	0.1 HTML_MIME_NO_HTML_TAG  Nachricht besteht nur aus HTML, hat aber kein "html"-Element
	0.1 MIME_BOUND_NEXTPART    Bestimmtes Muster von Spam-Software in MIME-Begrenzung
X-Spam-Flag: YES
X-Spam-Flag: YES
Message-ID: <SRV-EX01E1ioWwr2UAa00000104@srv-ex01.xxxxxxxxxxxx.de>
X-OriginalArrivalTime: 30 Nov 2005 11:31:08.0281 (UTC) FILETIME=[8EB6C690:01C5F5A1]
Hier steht deutlich 5 obwohl ich in Vexim 4 drin stehen habe. Und zum anderen Hat die e-Mail ja ne Score von 6.2 und müsste doch so oder so gelöscht werden.

Bin die Config schon durchgegangen hab aber nix entdecken können.
Im Forum brachte mich auch kein Beitrag weiter... :(

Danke für eure Hilfe!

dodolin
RSAC
Posts: 4009
Joined: 2003-01-21 01:59
Location: Sinsheim/Karlsruhe

Re: Vexim/ Exim - Spam Score wird nicht beachtet!

Post by dodolin » 2005-11-30 14:06

Hier sind wohl diverse Dinge im Spiel, die nicht genau so sind wie im Howto.

* Ein Exchange-Server. Was manipuliert der an den Mails rum?
* Es steht zweimal X-Spam-Flag: YES drin. Warum?
* Die Spammail wird als Attachment angehängt. Auch das ist nicht so im Debianhowto beschrieben, IIRC.

Es wäre zuerst mal hilfreich, zu wissen, was du im Vergleich zum Howto alles abgeändert hast. Ausserdem solltest du mal direkt in MySQL nachschauen, welche Spam-Einstellungen der entsprechende User dort hat. Hat er auch wirklich eingestellt, dass Spammails gelöscht werden sollen? Hast du auch die entsprechenden Blackhole-Router in die exim.conf eingebaut?

benedelux
Posts: 36
Joined: 2005-03-05 15:35
Location: im Allgäu...

Re: Vexim/ Exim - Spam Score wird nicht beachtet!

Post by benedelux » 2005-11-30 14:54

Aloá He dodolin!
Danke erstmal das du dich meiner wieder annimmst :-D

Das hast du alles mal wieder richtig erkannt.
Der Debian hier, arbeitet als RelayHost für den Exchange.
Erst kommen alle Mails auf dem Debian der in der DMZ steht an.
PopCon holt sich dann die e-Mail auf den ExchangeServer.

Ich mache das wegen der Sicherheit und weil ich den ExchangeServer net direkt an Netz hängen will.

Das Problem war sicher das ich sehr viel rumversucht habe eine Statistik für EXIM zu haben. Wollte mal SA-EXIM testen, hab dann
en modifiziertes Mailgraph drauf gemacht....Bis dahin hat es gepasst.

Fakt ist, nach dem Restart der Kiste ist SPAMASSASSIN neuerdings auf Deutsch! Ich habe in fast jeder Mail zwei XSpamFlags und die Datenbankeinträge die auf sa_refuse 4 stehen wird nicht beachtet.
Alles User stehen korrekt drin, und haben SPAMASSASSIN wie ANTIVIRUS
aktiviert.

Hier ist mal meine exim4.conf:

Code: Select all

######################################################################
#                  Runtime configuration file for Exim               #
######################################################################


# This is a default configuration file which will operate correctly in
# uncomplicated installations. Please see the manual for a complete list
# of all the runtime configuration options that can be included in a
# configuration file. There are many more than are mentioned here. The
# manual is in the file doc/spec.txt in the Exim distribution as a plain
# ASCII file. Other formats (PostScript, Texinfo, HTML, PDF) are available
# from the Exim ftp sites. The manual is also online at the Exim web sites.


# This file is divided into several parts, all but the first of which are
# headed by a line starting with the word "begin". Only those parts that
# are required need to be present. Blank lines, and lines starting with #
# are ignored.


########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
#                                                                          #
# Whenever you change Exim's configuration file, you *must* remember to    #
# HUP the Exim daemon, because it will not pick up the new configuration   #
# until you do. However, any other Exim processes that are started, for    #
# example, a process started by an MUA in order to send a message, will    #
# see the new configuration as soon as it is in place.                     #
#                                                                          #
# You do not need to HUP the daemon for changes in auxiliary files that    #
# are referenced from this file. They are read every time they are used.   #
#                                                                          #
# It is usually a good idea to test a new configuration for syntactic      #
# correctness before installing it (for example, by running the command    #
# "exim -C /config/file.new -bV").                                         #
#                                                                          #
########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########



######################################################################
#                    MAIN CONFIGURATION SETTINGS                     #
######################################################################

MAILMAN_HOME=/var/lib/mailman
MAILMAN_WRAP=MAILMAN_HOME/mail/mailman
MAILMAN_USER=list
MAILMAN_GROUP=daemon

# Specify your host's canonical name here. This should normally be the fully
# qualified "official" name of your host. If this option is not set, the
# uname() function is called to obtain the name. In many cases this does
# the right thing and you need not set anything explicitly.

# primary_hostname =

# Your IP address
MY_IP = 10.10.10.2

# The next three settings create two lists of domains and one list of hosts.
# These lists are referred to later in this configuration using the syntax
# +local_domains, +relay_to_domains, and +relay_from_hosts, respectively. They
# are all colon-separated lists:

# If you are using MySQL, uncomment the following two lines:
VIRTUAL_DOMAINS = SELECT DISTINCT domain FROM domains WHERE type = 'local' AND enabled = '1' AND domain = '${quote_mysql:$domain}'
RELAY_DOMAINS = SELECT DISTINCT domain FROM domains WHERE type = 'relay'  AND domain = '${quote_mysql:$domain}'
ALIAS_DOMAINS = SELECT DISTINCT alias FROM domainalias WHERE alias = '${quote_mysql:$domain}'

# If you are using PGSQL, uncomment the following four lines:
#VIRTUAL_DOMAINS = SELECT DISTINCT domain || ' : ' FROM domains WHERE type = 'local'
#RELAY_DOMAINS = SELECT DISTINCT domain || ' : ' FROM domains WHERE type = 'relay'

domainlist local_domains = @ : ${lookup mysql{VIRTUAL_DOMAINS}} : ${lookup mysql{ALIAS_DOMAINS}}

#domainlist local_domains = @ : pear.silverwraith.com : ${lookup mysql{VIRTUAL_DOMAINS}} : ${lookup mysql{ALIAS_DOMAINS}}

domainlist relay_to_domains = ${lookup mysql{RELAY_DOMAINS}}
hostlist relay_from_hosts = localhost : 192.168.1.0/24 : MY_IP : 192.168.1.7
trusted_users = vmail:www-data

hide mysql_servers = localhost::(/var/run/mysqld/mysqld.sock)/vexim/vexim/meinpasswort
#hide pgsql_servers = localhost/vexim/vexim/CHANGE

# Most straightforward access control requirements can be obtained by
# appropriate settings of the above options. In more complicated situations, you
# may need to modify the Access Control List (ACL) which appears later in this
# file.

# The first setting specifies your local domains, for example:
#
#   domainlist local_domains = my.first.domain : my.second.domain
#
# You can use "@" to mean "the name of the local host", as in the default
# setting above. This is the name that is specified by primary_hostname,
# as specified above (or defaulted). If you do not want to do any local
# deliveries, remove the "@" from the setting above. If you want to accept mail
# addressed to your host's literal IP address, for example, mail addressed to
# "user@[192.168.23.44]", you can add "@[]" as an item in the local domains
# list. You also need to uncomment "allow_domain_literals" below. This is not
# recommended for today's Internet.

# The second setting specifies domains for which your host is an incoming relay.
# If you are not doing any relaying, you should leave the list empty. However,
# if your host is an MX backup or gateway of some kind for some domains, you
# must set relay_to_domains to match those domains. For example:
#
# domainlist relay_to_domains = *.myco.com : my.friend.org
#
# This will allow any host to relay through your host to those domains.
# See the section of the manual entitled "Control of relaying" for more
# information.

# The third setting specifies hosts that can use your host as an outgoing relay
# to any other host on the Internet. Such a setting commonly refers to a
# complete local network as well as the localhost. For example:
#
# hostlist relay_from_hosts = 127.0.0.1 : 192.168.0.0/16
#
# The "/16" is a bit mask (CIDR notation), not a number of hosts. Note that you
# have to include 127.0.0.1 if you want to allow processes on your host to send
# SMTP mail by using the loopback address. A number of MUAs use this method of
# sending mail.


# All three of these lists may contain many different kinds of item, including
# wildcarded names, regular expressions, and file lookups. See the reference
# manual for details. The lists above are used in the access control list for
# incoming messages. The name of this ACL is defined here:

acl_smtp_rcpt = acl_check_rcpt

# You should not change that setting until you understand how ACLs work.

# The following ACL entry is used if you want to do content scanning with the
# exiscan-acl patch. When you uncomment this line, you must also review the
# acl_check_content entry in the ACL section further below.

acl_smtp_data = acl_check_content

# This ACL added by Avleen Vig will drop all mail where the sender's helo
# command contains your IP address. Please check the IP address at the top
# for the configure file to make it your own.

acl_smtp_helo = acl_check_helo

# This configuration variable defines the virus scanner that is used with
# the 'malware' ACL condition of the exiscan acl-patch. If you do not use
# virus scanning, leave it commented. Please read doc/exiscan-acl-readme.txt
# for a list of supported scanners.

av_scanner = clamd:/var/run/clamav/clamd.ctl

# The following setting is only needed if you use the 'spam' ACL condition
# of the exiscan-acl patch. It specifies on which host and port the SpamAssassin
# "spamd" daemon is listening. If you do not use this condition, or you use
# the default of "127.0.0.1 783", you can omit this option.

spamd_address = 127.0.0.1 783

# Specify the domain you want to be added to all unqualified addresses
# here. An unqualified address is one that does not contain an "@" character
# followed by a domain. For example, "caesar@rome.example" is a fully qualified
# address, but the string "caesar" (i.e. just a login name) is an unqualified
# email address. Unqualified addresses are accepted only from local callers by
# default. See the recipient_unqualified_hosts option if you want to permit
# unqualified addresses from remote sources. If this option is not set, the
# primary_hostname value is used for qualification.

# qualify_domain =


# If you want unqualified recipient addresses to be qualified with a different
# domain to unqualified sender addresses, specify the recipient domain here.
# If this option is not set, the qualify_domain value is used.

# qualify_recipient =


# The following line must be uncommented if you want Exim to recognize
# addresses of the form "user@[10.11.12.13]" that is, with a "domain literal"
# (an IP address) instead of a named domain. The RFCs still require this form,
# but it makes little sense to permit mail to be sent to specific hosts by
# their IP address in the modern Internet. This ancient format has been used
# by those seeking to abuse hosts by using them for unwanted relaying. If you
# really do want to support domain literals, uncomment the following line, and
# see also the "domain_literal" router below.

# allow_domain_literals


# No deliveries will ever be run under the uids of these users (a colon-
# separated list). An attempt to do so causes a panic error to be logged, and
# the delivery to be deferred. This is a paranoic safety catch. Note that the
# default setting means you cannot deliver mail addressed to root as if it
# were a normal user. This isn't usually a problem, as most sites have an alias
# for root that redirects such mail to a human administrator.

exim_user = Debian-exim
exim_group = Debian-exim
never_users = root


# The setting below causes Exim to do a reverse DNS lookup on all incoming
# IP calls, in order to get the true host name. If you feel this is too
# expensive, you can specify the networks for which a lookup is done, or
# remove the setting entirely.

host_lookup = *


# The settings below, which are actually the same as the defaults in the
# code, cause Exim to make RFC 1413 (ident) callbacks for all incoming SMTP
# calls. You can limit the hosts to which these calls are made, and/or change
# the timeout that is used. If you set the timeout to zero, all RFC 1413 calls
# are disabled. RFC 1413 calls are cheap and can provide useful information
# for tracing problem messages, but some hosts and firewalls have problems
# with them. This can result in a timeout instead of an immediate refused
# connection, leading to delays on starting up an SMTP session.

rfc1413_hosts = *
rfc1413_query_timeout = 0s


# By default, Exim expects all envelope addresses to be fully qualified, that
# is, they must contain both a local part and a domain. If you want to accept
# unqualified addresses (just a local part) from certain hosts, you can specify
# these hosts by setting one or both of
#
# sender_unqualified_hosts =
# recipient_unqualified_hosts =
#
# to control sender and recipient addresses, respectively. When this is done,
# unqualified addresses are qualified using the settings of qualify_domain
# and/or qualify_recipient (see above).


# If you want Exim to support the "percent hack" for certain domains,
# uncomment the following line and provide a list of domains. The "percent
# hack" is the feature by which mail addressed to x%y@z (where z is one of
# the domains listed) is locally rerouted to x@y and sent on. If z is not one
# of the "percent hack" domains, x%y is treated as an ordinary local part. This
# hack is rarely needed nowadays; you should not enable it unless you are sure
# that you really need it.
#
# percent_hack_domains =
#
# As well as setting this option you will also need to remove the test
# for local parts containing % in the ACL definition below.


# When Exim can neither deliver a message nor return it to sender, it "freezes"
# the delivery error message (aka "bounce message"). There are also other
# circumstances in which messages get frozen. They will stay on the queue for
# ever unless one of the following options is set.

# This option unfreezes frozen bounce messages after two days, tries
# once more to deliver them, and ignores any delivery failures.

ignore_bounce_errors_after = 2d

# This option cancels (removes) frozen messages that are older than a week.

timeout_frozen_after = 7d


# We also want a little more detail in our logs, helps with debugging

log_selector = +subject +tls_cipher +tls_peerdn +received_recipients +received_sender +sender_on_delivery +smtp_confirmation


######################################################################
#                       ACL CONFIGURATION                            #
#         Specifies access control lists for incoming SMTP mail      #
######################################################################

begin acl
  .include /etc/exim4/vexim-acl-check-spf.conf

acl_check_helo:

# Include Vexim specific helo ACLs
  .include /etc/exim4/vexim-acl-check-helo.conf

# This access control list is used for every RCPT command in an incoming
# SMTP message. The tests are run in order until the address is either
# accepted or denied.

acl_check_rcpt:

  # Accept if the source is local SMTP (i.e. not over TCP/IP). We do this by
  # testing for an empty sending host field.

  accept  hosts = :

  # Include Vexim specific rcpt ACLs
  .include /etc/exim4/vexim-acl-check-rcpt.conf

  # Deny if the local part contains @ or % or / or | or !. These are rarely
  # found in genuine local parts, but are often tried by people looking to
  # circumvent relaying restrictions.

  # Also deny if the local part starts with a dot. Empty components aren't
  # strictly legal in RFC 2822, but Exim allows them because this is common.
  # However, actually starting with a dot may cause trouble if the local part
  # is used as a file name (e.g. for a mailing list).

  deny    local_parts   = ^.*[@%!/|] : ^\.

  # Accept mail to postmaster in any local domain, regardless of the source,
  # and without verifying the sender.

  accept  local_parts   = postmaster
          domains       = +local_domains

  # Deny unless the sender address can be verified.
  # require verify        = sender

  #############################################################################
  # There are no checks on DNS "black" lists because the domains that contain
  # these lists are changing all the time. However, here are two examples of
  # how you could get Exim to perform a DNS black list lookup at this point.
  # The first one denies, while the second just warns.
  #
  # deny    message       = rejected because $sender_host_address is in a black list at $dnslist_domainn$dnslist_text
  #         dnslists      = black.list.example
  #
  # warn    message       = X-Warning: $sender_host_address is in a black list at $dnslist_domain
  #         log_message   = found in $dnslist_domain
  #         dnslists      = black.list.example
  #############################################################################

  # Accept if the address is in a local domain, but only if the recipient can
  # be verified. Otherwise deny. The "endpass" line is the border between
  # passing on to the next ACL statement (if tests above it fail) or denying
  # access (if tests below it fail).

  accept  domains       = +local_domains
          endpass
          verify        = recipient

  # Accept if the address is in a domain for which we are relaying, but again,
  # only if the recipient can be verified.

  accept  domains       = +relay_to_domains
          endpass
          verify        = recipient

  # If control reaches this point, the domain is neither in +local_domains
  # nor in +relay_to_domains.

  # Accept if the message comes from one of the hosts for which we are an
  # outgoing relay. Recipient verification is omitted here, because in many
  # cases the clients are dumb MUAs that don't cope well with SMTP error
  # responses. If you are actually relaying out from MTAs, you should probably
  # add recipient verification here.

  accept  hosts         = +relay_from_hosts

  # Accept if the message arrived over an authenticated connection, from
  # any host. Again, these messages are usually from MUAs, so recipient
  # verification is omitted.

  accept  authenticated = *

  # Reaching the end of the ACL causes a "deny", but we might as well give
  # an explicit message.

  deny    message       = relay not permitted


# This access control list is used for content scanning with the exiscan-acl
# patch. You must also uncomment the entry for acl_smtp_data (scroll up),
# otherwise the ACL will not be used. IMPORTANT: the default entries here
# should be treated as EXAMPLES. You MUST read the file doc/exiscan-acl-spec.txt
# to fully understand what you are doing ...

acl_check_content:

  # Include Vexim specific rcpt ACLs
  .include /etc/exim4/vexim-acl-check-content.conf

  # finally accept all the rest
  accept
  

######################################################################
#                      ROUTERS CONFIGURATION                         #
#               Specifies how addresses are handled                  #
######################################################################
#     THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT!       #
# An address is passed to each router in turn until it is accepted.  #
######################################################################

begin routers

# This router routes to remote hosts over SMTP by explicit IP address,
# when an email address is given in "domain literal" form, for example,
# <user@[192.168.35.64]>. The RFCs require this facility. However, it is
# little-known these days, and has been exploited by evil people seeking
# to abuse SMTP relays. Consequently it is commented out in the default
# configuration. If you uncomment this router, you also need to uncomment
# allow_domain_literals above, so that Exim can recognize the syntax of
# domain literal addresses.

# domain_literal:
#   driver = ipliteral
#   domains = ! +local_domains
#   transport = remote_smtp


# This router routes addresses that are not in local domains by doing a DNS
# lookup on the domain name. Any domain that resolves to 0.0.0.0 or to a
# loopback interface address (127.0.0.0/8) is treated as if it had no DNS
# entry. Note that 0.0.0.0 is the same as 0.0.0.0/32, which is commonly treated
# as the local host inside the network stack. It is not 0.0.0.0/0, the default
# route. If the DNS lookup fails, no further routers are tried because of
# the no_more setting, and consequently the address is unrouteable.

dnslookup:
  driver = dnslookup
  domains = ! +local_domains
  transport = remote_smtp
  ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
  no_more

mailman_router:
  driver = accept
  require_files = MAILMAN_HOME/lists/$local_part/config.pck
  local_part_suffix_optional
  local_part_suffix = -bounces : -bounces+* : 
                      -confirm+* : -join : -leave : 
                      -owner : -request : -admin
  headers_remove = X-Spam-Score:X-Spam-Report
  transport = mailman_transport

# The remaining routers handle addresses in the local domain(s).

# The virtual_domains alias, queries your given mysql database
# and requests the home directory of the user's maildir, the
# UID and the GID of the process to deliver under. You can be
# clever, and set the UID and GID of a user, to that of a
# local system user, so they can check their mail locally,
# rather than having to over a network. Three different
# transports are specified. virtual_delivery delivers if the
# home directory is a given directory on a locally accessible
# file system. address_reply is called if the home directory
# returns an email address (making the rcpt address an alias).
# finally, pipe_transport is used to pipe the mail to a
# process.

# This router caused me so much s*** it's untrue.
# If your db lookup returns 'no data', then $spam_in_score is
# greater than no data, and mail gets deleted.
# Eventually got this working with Philip Hazel and Codiac's help.
ditch_maxmsgsize:
  driver = redirect
  allow_fail
  condition = ${if >{$message_size}{${lookup mysql{select users.maxmsgsize from users,domains 
  		where localpart = '${quote_mysql:$local_part}' 
		and domain = '${quote_mysql:$domain}' 
		and users.maxmsgsize > 0 
		and users.domain_id=domains.domain_id }{${value}K}fail}} {yes}{no}}
  data = :fail:nYour message is too big.n 
	 	Your message was rejected because the user $local_part@$domainn 
		does not accept messages larger than 
		${lookup mysql{select users.maxmsgsize from users,domains 
		where localpart = '${quote_mysql:$local_part}' 
		and domain = '${quote_mysql:$domain}' 
		and users.maxmsgsize > 0 
		and users.domain_id=domains.domain_id}{${value}K}fail} Kb.
  local_part_suffix = -*
  local_part_suffix_optional
  retry_use_local_part

ditch_malware:
  driver = redirect
  allow_fail
  data = :blackhole:
  condition = ${if and { {match {$h_X-ACL-Warn:}{.*malware.*}} 
                         {eq {${lookup mysql{select users.on_avscan from users,domains 
		                where localpart = '${quote_mysql:$local_part}' 
		                and domain = '${quote_mysql:$domain}'  
		                and users.on_avscan = '1' 
		                and users.domain_id=domains.domain_id}}}{1} }} {yes}{no} }

ditch_spam:
  driver = redirect
  allow_fail
  data = :blackhole:
  condition = ${if >{$spam_score_int}{${lookup mysql{select users.sa_refuse * 10 from users,domains 
                where localpart = '${quote_mysql:$local_part}' 
                and domain = '${quote_mysql:$domain}' 
        	and users.on_spamassassin = '1' 
                and users.domain_id=domains.domain_id 
		and users.sa_refuse > 0 }{$value}fail}} {yes}{no}}
  local_part_suffix = -*
  local_part_suffix_optional
  retry_use_local_part

ditch_hdrmailer:
  driver = redirect
  allow_fail
  data = :blackhole:
  condition = ${if eq {${lookup mysql{select count(*) from blocklists,users,domains 
  			where blocklists.blockhdr = 'x-mailer' 
			and blocklists.blockval = '${quote_mysql:$h_x-mailer:}' 
			and users.localpart = '${quote_mysql:$local_part}' 
  			and domains.domain = '${quote_mysql:$domain}' 
			and domains.domain_id=blocklists.domain_id 
			and users.user_id=blocklists.user_id}}}{1} {yes}{no}}
  local_part_suffix = -*
  local_part_suffix_optional
  retry_use_local_part

ditch_hdrto:
  driver = redirect
  allow_fail
  data = :blackhole:
  condition = ${if eq {${lookup mysql{select count(*) from blocklists,users,domains 
  			where blocklists.blockhdr = 'to' 
			and blocklists.blockval = '${quote_mysql:$h_to:}' 
			and users.localpart = '${quote_mysql:$local_part}' 
  			and domains.domain = '${quote_mysql:$domain}' 
			and domains.domain_id=blocklists.domain_id 
			and users.user_id=blocklists.user_id}}}{1} {yes}{no}}
  local_part_suffix = -*
  local_part_suffix_optional
  retry_use_local_part

ditch_hdrfrom:
  driver = redirect
  allow_fail
  data = :blackhole:
  condition = ${if eq {${lookup mysql{select count(*) from blocklists,users,domains 
  			where blocklists.blockhdr = 'from' 
			and blocklists.blockval = '${quote_mysql:$h_from:}' 
			and users.localpart = '${quote_mysql:$local_part}' 
  			and domains.domain = '${quote_mysql:$domain}' 
			and domains.domain_id=blocklists.domain_id 
			and users.user_id=blocklists.user_id}}}{1} {yes}{no}}
  local_part_suffix = -*
  local_part_suffix_optional
  retry_use_local_part

ditch_hdrsubject:
  driver = redirect
  allow_fail
  data = :blackhole:
  condition = ${if eq {${lookup mysql{select count(*) from blocklists,users,domains 
  			where blocklists.blockhdr = 'subject' 
			and blocklists.blockval = '${quote_mysql:$h_subject:}' 
			and users.localpart = '${quote_mysql:$local_part}' 
  			and domains.domain = '${quote_mysql:$domain}' 
			and domains.domain_id=blocklists.domain_id 
			and users.user_id=blocklists.user_id}}}{1} {yes}{no}}
  local_part_suffix = -*
  local_part_suffix_optional
  retry_use_local_part

virtual_vacation:
  driver = accept
  condition = ${if and { {!match {$h_precedence:}{(?i)junk|bulk|list}} 
                         {eq {${lookup mysql{select users.on_vacation from users,domains 
		                where localpart = '${quote_mysql:$local_part}' 
		                and domain = '${quote_mysql:$domain}'  
		                and users.on_vacation = '1' 
		                and users.domain_id=domains.domain_id}}}{1} }} {yes}{no} }
  no_verify
  no_expn
  unseen
  transport = virtual_vacation_delivery

virtual_forward:
  driver = redirect
  check_ancestor
  unseen = ${if eq {${lookup mysql{select unseen from users,domains 
		where localpart = '${quote_mysql:$local_part}' 
		and domain = '${quote_mysql:$domain}' 
		and users.on_forward = '1' 
		and users.domain_id=domains.domain_id}}}{1} {yes}{no}}
  data = ${lookup mysql{select forward from users,domains 
	where localpart='${quote_mysql:$local_part}' 
	and domain='${quote_mysql:$domain}' 
	and users.domain_id=domains.domain_id 
	and on_forward = '1'}}
  # We explicitly make this condition NOT forward mailing list mail!
  condition = ${if and { {!match {$h_precedence:}{(?i)junk}} 
                         {eq {${lookup mysql{select users.on_forward from users,domains 
		                where localpart = '${quote_mysql:$local_part}' 
		                and domain = '${quote_mysql:$domain}'  
		                and users.on_forward = '1' 
		                and users.domain_id=domains.domain_id}}}{1} }} {yes}{no} }
  
virtual_domains:
  driver = redirect
  allow_fail
  data = ${lookup mysql{select smtp from users,domains 
  		where localpart = '${quote_mysql:$local_part}' 
		and domain = '${quote_mysql:$domain}' 
		and domains.enabled = '1' 
		and users.enabled = '1' 
		and users.domain_id = domains.domain_id}}
  headers_add = ${if >{$spam_score_int}{${lookup mysql{select users.sa_tag * 10 from users,domains 
  		where localpart = '${quote_mysql:$local_part}' 
		and domain = '${quote_mysql:$domain}' 
		and users.on_spamassassin = '1' 
		and users.domain_id=domains.domain_id }{$value}fail}} {X-Spam-Flag: YESn}{} }
  headers_remove = ${if or { { <{$spam_score_int}{1} } 
  			     { <{$spam_score_int}{${lookup mysql{select users.sa_tag * 10 from users,domains 
			       where localpart = '${quote_mysql:$local_part}' 
			       and domain = '${quote_mysql:$domain}' 
			       and users.on_spamassassin = 1 
			       and users.domain_id=domains.domain_id}{$value}fail}} } 
			     { eq {0}{${lookup mysql{select users.sa_tag * 10 from users,domains 
			       where localpart = '${quote_mysql:$local_part}' 
			       and domain = '${quote_mysql:$domain}' 
			       and users.on_spamassassin = 0 
			       and users.domain_id=domains.domain_id}{$value}fail}}} 
			   } {X-Spam-Score:X-Spam-Report} }
  local_part_suffix = Debian-exim -*
  local_part_suffix_optional
  retry_use_local_part
  file_transport = virtual_delivery
  reply_transport = address_reply
  pipe_transport = address_pipe
  
#.include /etc/exim4/vexim-group-router.conf

virtual_domains_catchall:
  driver = redirect
  allow_fail
  data = ${lookup mysql{select smtp from users,domains where localpart = '*' 
  		and domain = '${quote_mysql:$domain}' 
		and users.domain_id = domains.domain_id}}
  retry_use_local_part
  file_transport = virtual_delivery
  reply_transport = address_reply
  pipe_transport = address_pipe_catchall

virtual_domain_alias:
  driver = redirect
  allow_fail
  data = ${lookup mysql{select concat('${quote_mysql:$local_part}@', domain) 
  		from domains,domainalias where domainalias.alias = '${quote_mysql:$domain}' 
		and domainalias.domain_id = domains.domain_id}}
  retry_use_local_part
  

# This router handles aliasing using a linearly searched alias file with the
# name /etc/aliases. When this configuration is installed automatically,
# the name gets inserted into this file from whatever is set in Exim's
# build-time configuration. The default path is the traditional /etc/aliases.
# If you install this configuration by hand, you need to specify the correct
# path in the "data" setting below.
#
##### NB  You must ensure that the alias file exists. It used to be the case
##### NB  that every Unix had that file, because it was the Sendmail default.
##### NB  These days, there are systems that don't have it. Your aliases
##### NB  file should at least contain an alias for "postmaster".
#
# If any of your aliases expand to pipes or files, you will need to set
# up a user and a group for these deliveries to run under. You can do
# this by uncommenting the "user" option below (changing the user name
# as appropriate) and adding a "group" option if necessary. Alternatively, you
# can specify "user" on the transports that are used. Note that the transports
# listed below are the same as are used for .forward files; you might want
# to set up different ones for pipe and file deliveries from aliases.

system_aliases:
  driver = redirect
  allow_fail
  allow_defer
  data = ${lookup{$local_part}lsearch{/etc/aliases}}
  user = Debian-exim
  group = Debian-exim
  file_transport = address_file
  pipe_transport = address_pipe


# This router handles forwarding using traditional .forward files in users'
# home directories. If you want it also to allow mail filtering when a forward
# file starts with the string "# Exim filter", uncomment the "allow_filter"
# option.

# The no_verify setting means that this router is skipped when Exim is
# verifying addresses. Similarly, no_expn means that this router is skipped if
# Exim is processing an EXPN command.

# The check_ancestor option means that if the forward file generates an
# address that is an ancestor of the current one, the current one gets
# passed on instead. This covers the case where A is aliased to B and B
# has a .forward file pointing to A.

# The three transports specified at the end are those that are used when
# forwarding generates a direct delivery to a file, or to a pipe, or sets
# up an auto-reply, respectively.

userforward:
  driver = redirect
  check_local_user
  file = $home/.forward
  no_verify
  no_expn
  check_ancestor
# allow_filter
  file_transport = address_file
  pipe_transport = address_pipe_local
  reply_transport = address_reply
  condition = ${if exists{$home/.forward} {yes} {no} }
  group = mail


# This router matches local user mailboxes. If the router fails, the error
# message is "Unknown user".

localuser:
  driver = accept
  check_local_user
  transport = local_delivery
  cannot_route_message = Unknown user



######################################################################
#                      TRANSPORTS CONFIGURATION                      #
######################################################################
#                       ORDER DOES NOT MATTER                        #
#     Only one appropriate transport is called for each delivery.    #
######################################################################

# A transport is used only when referenced from a router that successfully
# handles an address.

begin transports


# This transport is used for delivering messages over SMTP connections.

remote_smtp:
  driver = smtp

# This transport is used for local delivery to user mailboxes in traditional
# BSD mailbox format. By default it will be run under the uid and gid of the
# local user, and requires the sticky bit to be set on the /var/mail directory.
# Some systems use the alternative approach of running mail deliveries under a
# particular group instead of using the sticky bit. The commented options below
# show how this can be done.

local_delivery:
  driver = appendfile
  file = /var/mail/$local_part
  delivery_date_add
  envelope_to_add
  return_path_add
  group = mail
  user = $local_part
  mode = 0660
  no_mode_fail_narrower

virtual_delivery:
  driver = appendfile
  envelope_to_add
  return_path_add
  mode = 0600
  maildir_format = true
  create_directory = true
  directory = ${lookup mysql{select smtp from users,domains 
		where localpart = '${quote_mysql:$local_part}' 
		and domain = '${quote_mysql:$domain}' 
		and users.domain_id = domains.domain_id}}
  user = ${lookup mysql{select users.uid  from users,domains 
		where localpart = '${quote_mysql:$local_part}' 
		and domain = '${quote_mysql:$domain}' 
		and users.domain_id = domains.domain_id}}
  group = ${lookup mysql{select users.gid from users,domains 
		where localpart = '${quote_mysql:$local_part}' 
		and domain = '${quote_mysql:$domain}' 
		and users.domain_id = domains.domain_id}}
  quota = ${lookup mysql{select users.quota from users,domains 
  		where localpart = '${quote_mysql:$local_part}' 
		and domain = '${quote_mysql:$domain}' 
		and users.domain_id = domains.domain_id}{${value}M}}
  quota_is_inclusive = false
  #quota_size_regex = ,S=(d+):
  quota_warn_threshold = 75%
  maildir_use_size_file = false
  quota_warn_message = "To: $local_part@$domainn
  			Subject: Mailbox quota warningnn
			This message was automatically generated by the mail delivery software.nn
			You are now using over 75% of your allocated mail storage quota.nn
			If your mailbox fills completely, further incoming messages will be automaticallyn
			returned to their senders.nn
			Please take note of this and remove unwanted mail from your mailbox.n"

virtual_vacation_delivery:
  driver   = autoreply
  from     = "${local_part}@${domain}"
  to       = ${sender_address}
  subject  = "Autoreply from ${local_part}@${domain}"
  text     = ${lookup mysql{select vacation from users,domains 
		where domain='${quote_mysql:$domain}' 
		and localpart='${quote_mysql:$local_part}' 
		and users.domain_id=domains.domain_id}}

mailman_transport:
  driver = pipe
  command = MAILMAN_WRAP 
            '${if def:local_part_suffix 
                  {${sg{$local_part_suffix}{-(\w+)(\+.*)?}{$1}}} 
                  {post}}' 
            $local_part
  current_directory = MAILMAN_HOME
  home_directory = MAILMAN_HOME
  user = MAILMAN_USER
  group = MAILMAN_GROUP

# This transport is used for handling pipe deliveries generated by alias or
# .forward files. If the pipe generates any standard output, it is returned
# to the sender of the message as a delivery error. Set return_fail_output
# instead of return_output if you want this to happen only when the pipe fails
# to complete normally. You can set different transports for aliases and
# forwards if you want to - see the references to address_pipe in the routers
# section above.

address_pipe:
  driver = pipe
  return_output
  user = ${lookup mysql{select users.uid from users,domains where localpart = '${quote_mysql:$local_part}' and domain = '${quote_mysql:$domain}' and users.domain_id = domains.domain_id}}
  group = ${lookup mysql{select users.gid from users,domains where localpart = '${quote_mysql:$local_part}' and domain = '${quote_mysql:$domain}' and users.domain_id = domains.domain_id}}

address_pipe_catchall:
  driver = pipe
  return_output
  user = ${lookup mysql{select users.uid from users,domains where localpart = '*' and domain = '${quote_mysql:$domain}' and users.domain_id = domains.domain_id}}
  group = ${lookup mysql{select users.gid from users,domains where localpart = '*' and domain = '${quote_mysql:$domain}' and users.domain_id = domains.domain_id}}

address_pipe_local:
  driver = pipe
  return_output


# This transport is used for handling deliveries directly to files that are
# generated by aliasing or forwarding.

address_file:
  driver = appendfile
  delivery_date_add
  envelope_to_add
  return_path_add


# This transport is used for handling autoreplies generated by the filtering
# option of the userforward router.

address_reply:
  driver = autoreply



######################################################################
#                      RETRY CONFIGURATION                           #
######################################################################

begin retry

# This single retry rule applies to all domains and all errors. It specifies
# retries every 15 minutes for 2 hours, then increasing retry intervals,
# starting at 1 hour and increasing each time by a factor of 1.5, up to 16
# hours, then retries every 6 hours until 4 days have passed since the first
# failed delivery.

# Domain               Error       Retries
# ------               -----       -------

*                      *           F,2h,15m; G,16h,1h,1.5; F,14d,6h



######################################################################
#                      REWRITE CONFIGURATION                         #
######################################################################

# There are no rewriting specifications in this default configuration file.

begin rewrite



######################################################################
#                   AUTHENTICATION CONFIGURATION                     #
######################################################################

# There are no authenticator specifications in this default configuration file.

begin authenticators

plain_login:
        driver = plaintext
        public_name = PLAIN
        server_condition = ${lookup mysql{SELECT '1' FROM users 
				WHERE username = '${quote_mysql:$2}' 
				AND clear = '${quote_mysql:$3}'} {yes}{no}}
        server_set_id = $2

fixed_login:
        driver = plaintext
        public_name = LOGIN
        server_prompts = "Username:: : Password::"
        server_condition = ${lookup mysql{SELECT '1' FROM users 
				WHERE username = '${quote_mysql:$1}' 
				AND clear = '${quote_mysql:$2}'} {yes}{no}}                    
        server_set_id = $1

fixed_cram:
        driver = cram_md5
        public_name = CRAM-MD5
        server_secret = ${lookup mysql{SELECT clear FROM users 
				WHERE username = '${quote_mysql:$1}'}{$value}fail}
        server_set_id = $1


######################################################################
#                   CONFIGURATION FOR local_scan()                   #
######################################################################

# If you have built Exim to include a local_scan() function that contains
# tables for private options, you can define those options here. Remember to
# uncomment the "begin" line. It is commented by default because it provokes
# an error with Exim binaries that are not built with LOCAL_SCAN_HAS_OPTIONS
# set in the Local/Makefile.

# begin local_scan


# End of Exim configuration file
Kann es noch an was anderes wie dieser Config liegen?
Sonst poste ich mal den Rest noch rein!
Eigentlich habe/wollte ich nix zu dem HowTO ändern... :?

Danke für die Hilfe!

dodolin
RSAC
Posts: 4009
Joined: 2003-01-21 01:59
Location: Sinsheim/Karlsruhe

Re: Vexim/ Exim - Spam Score wird nicht beachtet!

Post by dodolin » 2005-11-30 15:41

Wollte mal SA-EXIM testen
Der läuft wohl immer noch, denn nur SA-EXIM ist in der Lage, Spammails in ein Attachment zu packen. Mit dem Debianhowto Setup ist das gar nicht möglich.

benedelux
Posts: 36
Joined: 2005-03-05 15:35
Location: im Allgäu...

Re: Vexim/ Exim - Spam Score wird nicht beachtet!

Post by benedelux » 2005-11-30 15:45

Ok!
Dann werde ich das jetzt mal wieder mit apt-get removen und die Kisten neustarten.... :roll:

Danke schon mal!!!

benedelux
Posts: 36
Joined: 2005-03-05 15:35
Location: im Allgäu...

Re: Vexim/ Exim - Spam Score wird nicht beachtet!

Post by benedelux » 2005-12-01 08:53

Guten Morgen Zusammen!

Sodele, habe jetzt mit apt-get sa-exim wieder gelöscht.
SPAMASSASSIN ist jetzt auch wieder auf English und nicht mehr Deutsch.

Leider wird die sa_refuse score in der DB nicht beachtet.
Stehen immernoch auf in der DB 4 und nicht 5 wie in der Mail hier.

Hier ein neuer Auszug aus ne SPAMMAIL:

Code: Select all

x-sender: fsqgombeo@comcast.com
x-receiver: brennstoffe@xxxxxxxxxxxx.de
x-receiver: d.stoeckler@xxxxxxxxxxxx.de
Received: from exchange-pop3-connector.com ([192.168.1.7]) by srv-ex01.xxxxxxxxxxxx.de with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 1 Dec 2005 06:57:50 +0100
Return-path: <fsqgombeo@comcast.com>
Envelope-to: brennstoffe@xxxxxxxxxx.de
Received: from mforward.dtag.de ([194.25.242.123])
	by mail.xxxxxxxxxxx.de with esmtp (Exim 4.50)
	id 1EhhKk-0000V9-Cw
	for brennstoffe@xxxxxxxxxxxxxde; Thu, 01 Dec 2005 06:50:18 +0100
Received: from 194.25.242.123 ([61.37.174.190])
	by mforward.dtag.de (8.13.3/8.13.3) with SMTP id jB15oBeR019157;
	Thu, 1 Dec 2005 06:50:13 +0100
Received: from wahl.hal.fi ([IPv6:::ffff:68.1]:3873 "EHLO
	cabot.emphases.fi" smtp-auth: <none> TLS-CIPHER: <none> TLS-PEER: <none>)
	by bouncy.sojourn.org with ESMTP id <S2622232amoebaecombine>;
	Thu, 01 Dec 2005 04:42:15 -0100
Date: Thu, 01 Dec 2005 09:42:15 +0400
Message-ID: <200308011.72818.GA16253@ibm.eu.org>
From: "Marissa Barnhart" <fsqgombeo@comcast.com>
To: d.stoeckler@xxxxxxxxxxx.de
Subject: Ever Have a Small St0ck Take Off?
X-Mailer: Mulberry/2.1.50
X-Spam-Score: 2.1 (++)
X-Spam-Report: Spam detection software, running on the system "mail.xxxxxxxxx.de", has
	identified this incoming email as possible spam.  The original message
	has been attached to this so you can view it (if it isn't spam) or label
	similar future email.  If you have any questions, see
	the administrator of that system for details.
	Content preview:  Gulf Biomedical Corp (GBIC) Current Price $0.50 Is this
	an Undiscovered Gem that is Positioned to Go Higher? Pleasee R e a d
	the Following Announcement in its Entirety and Consider the
	Possibilities... Watch This One Trade Monday! [...] 
	Content analysis details:   (2.1 points, 5.0 required)
	pts rule name              description
	---- ---------------------- --------------------------------------------------
	0.6 RCVD_HELO_IP_MISMATCH  Received: HELO and IP do not match, but should
	1.5 RCVD_NUMERIC_HELO      Received: contains an IP address used for HELO
X-Spam-Flag: YES
X-Spam-Flag: YES
X-OriginalArrivalTime: 01 Dec 2005 05:57:50.0558 (UTC) FILETIME=[298E27E0:01C5F63C]
Habe aber immernoch zwei X-Spam-Flags :x
Weis jemand wie das sein kann??
SA-EXIM ist gelöscht und die Kiste danach neu gebootet...

Wie kann es sein das da noch was greift?
An der EXIM.CONF wurde nichts mehr verändert. Obige ist noch aktuell.

D A N K E !!!

dodolin
RSAC
Posts: 4009
Joined: 2003-01-21 01:59
Location: Sinsheim/Karlsruhe

Re: Vexim/ Exim - Spam Score wird nicht beachtet!

Post by dodolin » 2005-12-01 12:42

Leider wird die sa_refuse score in der DB nicht beachtet.
Stehen immernoch auf in der DB 4 und nicht 5 wie in der Mail hier.
Missverständnis deinerseits.
Was hier wie folgt eingetragen wird:
Content analysis details: (2.1 points, 5.0 required)
Ist für alle User unabhängig von den Einstellungen gleich. Erst in den entsprechenden Blackhole-Routern werden dann die user-spezifischen Einstellungen beachtet. Um das zu testen, müsstest du eine Mail mit einem Score zwischen 4 und 5 haben und an diesen User senden. Sie sollte dann trotzdem gelöscht werden. Oder setze testweise den sa_refuse score in der DB relativ niedrig.

benedelux
Posts: 36
Joined: 2005-03-05 15:35
Location: im Allgäu...

Re: Vexim/ Exim - Spam Score wird nicht beachtet!

Post by benedelux » 2005-12-01 18:56

OK! Werde ich mal testen.

Das würde ja heißen das ich weder in der "mail.log" noch in der e-Mail(HEADER) wirklich erkennen kann wie hoch die refuse score ist?! Richtig? Weil die ja immer auf 5 steht.

Habe gedacht das das übernommen wird in die logs und e-Mail.
Wie gesagt ich werde es mal testen!

D A N K E !!!