You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by ha...@t-online.de on 2006/04/30 17:35:53 UTC
qmail auth mail received as spam
Here is a piece of mail that gets classified as spam,
although it should not.
I have replaced a few email addresses by fake ones, they dont contribute to the problem.
So what happens: a mail is sent via an authenticated session, to a qmail / qmail-scanner
setup running at mydomain.de
Here qmail adds its received header
Received: from p5499d2c7.dip.t-dialin.net (HELO test) (w1p1@84.153.210.199)
identifying that the mail originates from a dynamic ip. Note that out of many smtp auth
patches only this one seems to put the ESMTPA keyword in the header.
Next, qmail-scanner adds its own header
Received: from 84.153.210.199 (w1p1@84.153.210.199) by mail3 (envelope-from <me...@mydomain.de.de>, uid 0) with qmail-scanner-2.01
saying essentially the same things again (dynamic ip, known user name) just with the dynamic
dns name of the sender replaced by its ip address.
The mail is sent to its destination, another qmail machine running SA
Here, SA assigns score to DUL lists, and to a numeric ip in helo (which
was only added by qmail-scanner, The HOST_EQ_D_D_D_D and HOST_EQ_D_D_D_DB
entries also seem to be triggered by the qmail-scanner header
Wolfgang Hamann
>> X-Spam-Level: ********
>> X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mailserver
>> X-Spam-Flag: YES
>> X-Spam-Status: Yes, score=8.2 required=5.2 tests=DK_SIGNED,HELO_EQ_IP_ADDR,
>> HOST_EQ_D_D_D_D,HOST_EQ_D_D_D_DB,NO_REAL_NAME,RCVD_IN_NJABL_DUL,
>> RCVD_IN_SORBS_DUL,RCVD_NUMERIC_HELO autolearn=no version=3.1.1
>> X-Spam-Report:
>> * 0.7 HOST_EQ_D_D_D_D HOST_EQ_D_D_D_D
>> * 1.1 HELO_EQ_IP_ADDR HELO using IP Address (not private)
>> * 0.6 NO_REAL_NAME From: does not include a real name
>> * 0.9 HOST_EQ_D_D_D_DB HOST_EQ_D_D_D_DB
>> * 0.0 DK_SIGNED Domain Keys: message has an unverified signature
>> * 1.3 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO
>> * 2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address
>> * [84.153.210.199 listed in dnsbl.sorbs.net]
>> * 1.7 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP
>> * [84.153.210.199 listed in combined.njabl.org]
>> Received: (qmail 13293 invoked by uid 0); 30 Apr 2006 10:13:00 -0000
>> Received: from me@mydomain.de by mail1 by uid 81 with qmail-scanner-1.20rc2
>> (clamdscan: 0.88. hbedv: AntiVir / Linux Version 2.1.6-23 spamassassin: 3.1.1. Clear:RC:0:.
>> Processed in 3.195621 secs); 30 Apr 2006 10:13:00 -0000
>> Received: from shared3.provider.de (HELO shared3.provider.de) (qmailr@1.2.3.4)
>> by mail1.provider.de with AES256-SHA encrypted SMTP; 30 Apr 2006 10:12:56 -0000
>> Received: (qmail 30465 invoked by uid 0); 30 Apr 2006 10:12:55 -0000
>> Received: from 84.153.210.199 (w1p1@84.153.210.199) by shared3 (envelope-from <me...@mydomain.de.de>, uid 0) with qmail-scanner-2.01
>> (clamdscan: 0.88.1/1426. hbedv: 6.34.1.27/6.34.1.12. spammassassin: 3.1.1
>> Clear:RC:0(84.153.210.199):.
>> Processed in 1.306009 secs); 30 Apr 2006 10:12:55 -0000
>> X-Qmail-Scanner-Mail-From: me@mydomain.de via shared3
>> X-Qmail-Scanner: 2.01 (Clear:RC:0(84.153.210.199):. Processed in 1.306009 secs)
>> Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
>> DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
>> s=default; d=mydomain.de;
>> b=ur58T/KNSEqQPRhnEoNUvKyvKlEhz9l5nbRkZCcpUuuKn+CDCuuSMRpRRPVeBInvhGF5Z/j8dRxEfZL74d3A/A36I4dxQuqQZHNPJ8aLTzIqQRnv76ynl4CB+zDzo/VGsYiLD3R07lOe+BTwtknoSdTQ3ENbHp37KnDE37mZHXo= ;
>> Received: from p5499d2c7.dip.t-dialin.net (HELO test) (w1p1@84.153.210.199)
>> by www.mydomain.de with ESMTPA; 30 Apr 2006 10:11:39 -0000
>> From: me@mydomain.de
>> To: ....
Re: qmail auth mail received as spam
Posted by jdow <jd...@earthlink.net>.
From: "Matt Kettler" <mk...@evi-inc.com>
> Jason Haar wrote:
>> HOST_EQ_D_D_D_D isn't part of standard SA - where did that come from?
>>
>
> It appears to come from:
> http://www.rulesemporium.com/rules/88_FVGT_headers.cf
>
>
>
> header HOST_EQ_D_D_D_D X-Spam-Relays-Untrusted =~ /^[^\]]+ rdns=[^
> ]+\d{1,3}[^0-9]\d{1,3}[^0-9]\d{1,3}[^0-9]\d{1,3}[^ ]+ /
> score HOST_EQ_D_D_D_D 0.665
> #counts HOST_EQ_D_D_D_D 10886s/231h of 41745 corpus (34134s/7611h FVGT) 03/29/06
>
> header HOST_EQ_D_D_D_DB X-Spam-Relays-Untrusted =~ /^[^\]]+
> rdns=\d{1,3}[^0-9]\d{1,3}[^0-9]\d{1,3}[^0-9]\d{1,3}[^ ]+ /
> score HOST_EQ_D_D_D_DB 0.888
> #counts HOST_EQ_D_D_D_DB 4324s/71h of 42070 corpus (34144s/7926h FVGT) 04/19/06
>
>
>>>From the looks of it they're detecting untrusted relays which reverse-dns names
> which are of the typical host-208-39-141-94.example.com format for dynamic hosts.
It's time for Fred to work over 88_FGVT rule scores a little. Or else
I get a different mix of spam than he does. I just set FM_3PLUS_NODNS
and FB_SINGLE_1WORD to zero. They were not hitting much of anything and
what they hit was more ham than spam.
{^_^}
Re: qmail auth mail received as spam
Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.
Jason Haar wrote:
> I guess a more generic question would be: how do sites handle calling SA
> for validated-but-remote local users? Qmail-Scanner defaults to *not*
> calling SA - is that what most others do too?
>
> If not, how do you handle the fact those users are (by definition) going
> to be on DUL lists?
If you can't avoid scanning their mail, either by not scanning mail sent
through your own MSAs, or funky configuring in an application like
Qmail-scanner, there are ways to deal with it in SpamAssassin:
http://wiki.apache.org/spamassassin/DynablockIssues
Re: qmail auth mail received as spam
Posted by Jason Haar <Ja...@trimble.co.nz>.
I guess a more generic question would be: how do sites handle calling SA
for validated-but-remote local users? Qmail-Scanner defaults to *not*
calling SA - is that what most others do too?
If not, how do you handle the fact those users are (by definition) going
to be on DUL lists?
--
Cheers
Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
Re: qmail auth mail received as spam
Posted by Matt Kettler <mk...@evi-inc.com>.
Jason Haar wrote:
> HOST_EQ_D_D_D_D isn't part of standard SA - where did that come from?
>
It appears to come from:
http://www.rulesemporium.com/rules/88_FVGT_headers.cf
header HOST_EQ_D_D_D_D X-Spam-Relays-Untrusted =~ /^[^\]]+ rdns=[^
]+\d{1,3}[^0-9]\d{1,3}[^0-9]\d{1,3}[^0-9]\d{1,3}[^ ]+ /
score HOST_EQ_D_D_D_D 0.665
#counts HOST_EQ_D_D_D_D 10886s/231h of 41745 corpus (34134s/7611h FVGT) 03/29/06
header HOST_EQ_D_D_D_DB X-Spam-Relays-Untrusted =~ /^[^\]]+
rdns=\d{1,3}[^0-9]\d{1,3}[^0-9]\d{1,3}[^0-9]\d{1,3}[^ ]+ /
score HOST_EQ_D_D_D_DB 0.888
#counts HOST_EQ_D_D_D_DB 4324s/71h of 42070 corpus (34144s/7926h FVGT) 04/19/06
>From the looks of it they're detecting untrusted relays which reverse-dns names
which are of the typical host-208-39-141-94.example.com format for dynamic hosts.
Re: qmail auth mail received as spam
Posted by Jason Haar <Ja...@trimble.co.nz>.
hamann.w@t-online.de wrote:
> So what happens: a mail is sent via an authenticated session, to a qmail / qmail-scanner
> setup running at mydomain.de
>
By default Qmail-Scanner specifically doesn't pass locally generated or
authenticated mail to SpamAssassin. Have you overridden that? If so,
why? As most of your authenticated end-users are connecting to your
Internet mail server from dialup (DUL) addresses, it makes no sense to
run SA against their email (if SA is configured to do RBL checks that is).
> The mail is sent to its destination, another qmail machine running SA
> Here, SA assigns score to DUL lists, and to a numeric ip in helo (which
> was only added by qmail-scanner, The HOST_EQ_D_D_D_D and HOST_EQ_D_D_D_DB
> entries also seem to be triggered by the qmail-scanner header
>
>
HOST_EQ_D_D_D_D isn't part of standard SA - where did that come from?
--
Cheers
Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
--
Cheers
Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1