DarkFather
11.08.07, 16:27
ich habe das problem, dass mein spamassassin scheinbar die falschen informationen in den header schreibt. am besten ihr schaut euch das an folgendem beispiel an (gerade reingekommen)
in der mail:
Spam detection software, running on the ... usw.
Content preview: ... (vorschau halt)
Content analysis details: (9.9 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
3.5 BAYES_99 BODY: Bayesian spam probability is 99 to 100%
[score: 1.0000]
2.4 RCVD_IN_WHOIS_BOGONS RBL: CompleteWhois: sender on bogons IP block
[196.175.65.187 listed in combined-HIB.dnsiplists.completewhois.com]
2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address
[201.8.106.185 listed in dnsbl.sorbs.net]
1.9 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP
[201.8.106.185 listed in combined.njabl.org]
header:
X-Kaspersky: Checked
X-Spam-Checker-Version: SpamAssassin 3.1.7-deb (2006-10-05) on
myserver.entfernt:)
X-Spam-Level: ***
X-Spam-Status: No, score=3.5 required=5.0 tests=BAYES_99,UNPARSEABLE_RELAY
autolearn=no version=3.1.7-deb
Received: from localhost by myserver.entfernt:)
with SpamAssassin (version 3.1.7-deb);
Sat, 11 Aug 2007 17:18:45 +0200
From: "Nikki Dwenger" <Dwengerfvs@breton-distribution.com>
To: <infodd@myserver.entfernt:)>
Subject: *****SPAM***** The JScript is under 100 lines long.
Date: Sat, 11 Aug 2007 12:18:49 -0300
Message-Id: <485498197934.061739209074@breton-distribution.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_46BDD355.B4610D1A"
ganz klar, sa erkennt die mail als spam aber schreibt es im header nicht gescheit rein, deshalb stellt mein procmailrc die mail zu.
hier noch die passende stelle in der procmailrc falls dort der fehler liegt:
:0fw
| /usr/bin/spamassassin
:0
* ^X-Spam-Status: Yes
/dev/null
danke schonmal für eure hilfe
in der mail:
Spam detection software, running on the ... usw.
Content preview: ... (vorschau halt)
Content analysis details: (9.9 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
3.5 BAYES_99 BODY: Bayesian spam probability is 99 to 100%
[score: 1.0000]
2.4 RCVD_IN_WHOIS_BOGONS RBL: CompleteWhois: sender on bogons IP block
[196.175.65.187 listed in combined-HIB.dnsiplists.completewhois.com]
2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address
[201.8.106.185 listed in dnsbl.sorbs.net]
1.9 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP
[201.8.106.185 listed in combined.njabl.org]
header:
X-Kaspersky: Checked
X-Spam-Checker-Version: SpamAssassin 3.1.7-deb (2006-10-05) on
myserver.entfernt:)
X-Spam-Level: ***
X-Spam-Status: No, score=3.5 required=5.0 tests=BAYES_99,UNPARSEABLE_RELAY
autolearn=no version=3.1.7-deb
Received: from localhost by myserver.entfernt:)
with SpamAssassin (version 3.1.7-deb);
Sat, 11 Aug 2007 17:18:45 +0200
From: "Nikki Dwenger" <Dwengerfvs@breton-distribution.com>
To: <infodd@myserver.entfernt:)>
Subject: *****SPAM***** The JScript is under 100 lines long.
Date: Sat, 11 Aug 2007 12:18:49 -0300
Message-Id: <485498197934.061739209074@breton-distribution.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_46BDD355.B4610D1A"
ganz klar, sa erkennt die mail als spam aber schreibt es im header nicht gescheit rein, deshalb stellt mein procmailrc die mail zu.
hier noch die passende stelle in der procmailrc falls dort der fehler liegt:
:0fw
| /usr/bin/spamassassin
:0
* ^X-Spam-Status: Yes
/dev/null
danke schonmal für eure hilfe