You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Matthew Dickinson <ma...@ire.org> on 2007/05/17 21:41:36 UTC
Sendmail SMTP auth'd message strange behavior with Botnet and SPF
Hi,
When sending messages from clients using SMTP Auth to a server running
sendmail, I'm seeing issues with SPF and Botnet thinking these messages are
spam-like - I'm not sure if this issue lays with SA or with sendmail itself.
The below message is sent from a (broken) Cingular 8125 phone, hence the no
RDNS.
Matthew
Received: from Inbox ([166.216.69.130])
(authenticated bits=0)
by server.domain.org (8.12.11.20060308/8.12.11) with ESMTP id
l4HJRKUm015411
(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
for <ma...@domain.org>; Thu, 17 May 2007 14:27:29 -0500
Message-Id: <20...@server.domain.org>
MIME-Version: 1.0
From: Matthew Dickinson <ma...@domain.org>
Subject: Test message
Date: Thu, 17 May 2007 14:28:00 -0500
Importance: normal
X-Priority: 3
To: <ma...@domain.org>
Content-Type: text/plain; charset="iso-8859-1"
X-Virus-Scanned: ClamAV version 0.88.7, clamav-milter version 0.88.7 on
server.domain.org
X-Virus-Status: Clean
X-Spam-Status: No, score=2.5 required=5.0 tests=AWL,BAYES_50,BOTNET,
BOTNET_NORDNS,DKIM_POLICY_SIGNSOME,DK_POLICY_SIGNSOME,MISSING_MID,RDNS_NONE,
SPF_FAIL shortcircuit=no autolearn=no version=3.2.0
X-Spam-Level: **
X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) on server.domain.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by server.domain.org id
l4HJRKUm015411
Re: Sendmail SMTP auth'd message strange behavior with Botnet and
SPF
Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.
René Berber wrote:
> Looks more like MailScanner to me, not a milter, notice the virus
> scan... and MS does include the full received headers. But your point
> is valid, that could be the cause of the problem in some cases.
The virus scan looks like it's compliments of clamav-milter to me. :)
Daryl
Re: Sendmail SMTP auth'd message strange behavior with Botnet and
SPF
Posted by René Berber <r....@computer.org>.
Daryl C. W. O'Shea wrote:
> René Berber wrote:
>> Matthew Dickinson wrote:
>>
>>> When sending messages from clients using SMTP Auth to a server
>>> running sendmail, I'm seeing issues with SPF and Botnet thinking
>>> these messages are spam-like - I'm not sure if this issue lays with
>>> SA or with sendmail itself.
>>
>> The issue is with SA, sendmail is an innocent bystander.
>
> There's no evidence of that. In fact there's evidence of the contrary.
> Since the X-Spam header fields were appended to the bottom of the
> header they were added by a milter and not SA. It's quite likely that
> they were added by a milter like spamass-milter that isn't providing SA
> with the auth info it needs to extend trust accordingly.
Looks more like MailScanner to me, not a milter, notice the virus scan... and MS
does include the full received headers. But your point is valid, that could be
the cause of the problem in some cases.
>> SA: do you have trusted_networks set correctly?
>
> In the case of auth'd connections from unknown in advance IPs it's up to
> whatever passes the message to SpamAssassin to provide the appropriate
> auth info. trusted_networks only needs to be configured to include the
> server that the auth'd user/device/whatever connects to.
Correct, my observation was ambiguous, I meant that the server should be
included in the trusted_networks, not the client.
--
René Berber
Re: Sendmail SMTP auth'd message strange behavior with Botnet and
SPF
Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.
René Berber wrote:
> Matthew Dickinson wrote:
>
>> When sending messages from clients using SMTP Auth to a server running
>> sendmail, I'm seeing issues with SPF and Botnet thinking these
>> messages are spam-like - I'm not sure if this issue lays with SA or
>> with sendmail itself.
>
> The issue is with SA, sendmail is an innocent bystander.
There's no evidence of that. In fact there's evidence of the contrary.
Since the X-Spam header fields were appended to the bottom of the
header they were added by a milter and not SA. It's quite likely that
they were added by a milter like spamass-milter that isn't providing SA
with the auth info it needs to extend trust accordingly.
> SA: do you have trusted_networks set correctly?
In the case of auth'd connections from unknown in advance IPs it's up to
whatever passes the message to SpamAssassin to provide the appropriate
auth info. trusted_networks only needs to be configured to include the
server that the auth'd user/device/whatever connects to.
Daryl
RE: Sendmail SMTP auth'd message strange behavior with Botnet and SPF
Posted by Matthew Dickinson <ma...@ire.org>.
Hi,
I believe I have things set:
(yes, this many are trusted)
trusted_networks 128.206/16
botnet_pass_auth 1
Will run through debug,
Matthew
> -----Original Message-----
> From: news [mailto:news@sea.gmane.org] On Behalf Of René Berber
> Sent: Thursday, May 17, 2007 17:00
> To: users@spamassassin.apache.org
> Subject: Re: Sendmail SMTP auth'd message strange behavior with Botnet and
SPF
>
> Matthew Dickinson wrote:
>
> > When sending messages from clients using SMTP Auth to a server running
> > sendmail, I'm seeing issues with SPF and Botnet thinking these messages
are
> > spam-like - I'm not sure if this issue lays with SA or with sendmail
itself.
>
> The issue is with SA, sendmail is an innocent bystander.
>
> SA: do you have trusted_networks set correctly?
>
> Botnet: do you have "botnet_pass_auth 1" set?
>
> SPF shouldn't have triggered, looks like a problem with trusted_networks.
>
> The best way to figure this out is by running `spamassassin -x -D -t <
> test.eml`
> and look for the trusted pseudo-headers (X-Spam-Relays-Untrusted,
> X-Spam-Relays-Internal, X-Spam-Relays-External) and lines like:
>
> [824] dbg: received-header: relay 200.52.129.137 trusted? yes internal?
yes
>
>
> > The below message is sent from a (broken) Cingular 8125 phone, hence the
no
> > RDNS.
> >
> > Matthew
> >
> > Received: from Inbox ([166.216.69.130]) (authenticated bits=0) by
> > server.domain.org (8.12.11.20060308/8.12.11) with ESMTP id
l4HJRKUm015411
> > (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for
> > <ma...@domain.org>; Thu, 17 May 2007 14:27:29 -0500 Message-Id:
> > <20...@server.domain.org> MIME-Version: 1.0 From:
> > Matthew Dickinson <ma...@domain.org> Subject: Test message Date: Thu, 17
May
> > 2007 14:28:00 -0500 Importance: normal X-Priority: 3 To:
<ma...@domain.org>
> > Content-Type: text/plain; charset="iso-8859-1" X-Virus-Scanned: ClamAV
> > version 0.88.7, clamav-milter version 0.88.7 on server.domain.org
> > X-Virus-Status: Clean X-Spam-Status: No, score=2.5 required=5.0
> > tests=AWL,BAYES_50,BOTNET,
> >
> >
BOTNET_NORDNS,DKIM_POLICY_SIGNSOME,DK_POLICY_SIGNSOME,MISSING_MID,RDNS_NONE,
> > SPF_FAIL shortcircuit=no autolearn=no version=3.2.0 X-Spam-Level: **
> > X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) on
server.domain.org
> > Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from
quoted-printable
> > to 8bit by server.domain.org id l4HJRKUm015411
> --
> René Berber
Re: Sendmail SMTP auth'd message strange behavior with Botnet and
SPF
Posted by René Berber <r....@computer.org>.
Matthew Dickinson wrote:
> When sending messages from clients using SMTP Auth to a server running
> sendmail, I'm seeing issues with SPF and Botnet thinking these messages are
> spam-like - I'm not sure if this issue lays with SA or with sendmail itself.
The issue is with SA, sendmail is an innocent bystander.
SA: do you have trusted_networks set correctly?
Botnet: do you have "botnet_pass_auth 1" set?
SPF shouldn't have triggered, looks like a problem with trusted_networks.
The best way to figure this out is by running `spamassassin -x -D -t < test.eml`
and look for the trusted pseudo-headers (X-Spam-Relays-Untrusted,
X-Spam-Relays-Internal, X-Spam-Relays-External) and lines like:
[824] dbg: received-header: relay 200.52.129.137 trusted? yes internal? yes
> The below message is sent from a (broken) Cingular 8125 phone, hence the no
> RDNS.
>
> Matthew
>
> Received: from Inbox ([166.216.69.130]) (authenticated bits=0) by
> server.domain.org (8.12.11.20060308/8.12.11) with ESMTP id l4HJRKUm015411
> (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for
> <ma...@domain.org>; Thu, 17 May 2007 14:27:29 -0500 Message-Id:
> <20...@server.domain.org> MIME-Version: 1.0 From:
> Matthew Dickinson <ma...@domain.org> Subject: Test message Date: Thu, 17 May
> 2007 14:28:00 -0500 Importance: normal X-Priority: 3 To: <ma...@domain.org>
> Content-Type: text/plain; charset="iso-8859-1" X-Virus-Scanned: ClamAV
> version 0.88.7, clamav-milter version 0.88.7 on server.domain.org
> X-Virus-Status: Clean X-Spam-Status: No, score=2.5 required=5.0
> tests=AWL,BAYES_50,BOTNET,
>
> BOTNET_NORDNS,DKIM_POLICY_SIGNSOME,DK_POLICY_SIGNSOME,MISSING_MID,RDNS_NONE,
> SPF_FAIL shortcircuit=no autolearn=no version=3.2.0 X-Spam-Level: **
> X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) on server.domain.org
> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable
> to 8bit by server.domain.org id l4HJRKUm015411
--
René Berber
Re: Sendmail SMTP auth'd message strange behavior with Botnet and
SPF
Posted by Dan Schwartz <Da...@Lehigh.EDU>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Matthew Dickinson wrote:
> Hi,
>
> When sending messages from clients using SMTP Auth to a server running
> sendmail, I'm seeing issues with SPF and Botnet thinking these messages are
> spam-like - I'm not sure if this issue lays with SA or with sendmail itself.
>
>
> The below message is sent from a (broken) Cingular 8125 phone, hence the no
> RDNS.
>
> Matthew
>
> Received: from Inbox ([166.216.69.130])
> (authenticated bits=0)
> by server.domain.org (8.12.11.20060308/8.12.11) with ESMTP id
> l4HJRKUm015411
> (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
> for <ma...@domain.org>; Thu, 17 May 2007 14:27:29 -0500
> Message-Id: <20...@server.domain.org>
> MIME-Version: 1.0
> From: Matthew Dickinson <ma...@domain.org>
> Subject: Test message
> Date: Thu, 17 May 2007 14:28:00 -0500
> Importance: normal
> X-Priority: 3
> To: <ma...@domain.org>
> Content-Type: text/plain; charset="iso-8859-1"
> X-Virus-Scanned: ClamAV version 0.88.7, clamav-milter version 0.88.7 on
> server.domain.org
> X-Virus-Status: Clean
> X-Spam-Status: No, score=2.5 required=5.0 tests=AWL,BAYES_50,BOTNET,
>
> BOTNET_NORDNS,DKIM_POLICY_SIGNSOME,DK_POLICY_SIGNSOME,MISSING_MID,RDNS_NONE,
> SPF_FAIL shortcircuit=no autolearn=no version=3.2.0
> X-Spam-Level: **
> X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) on server.domain.org
> Content-Transfer-Encoding: 8bit
> X-MIME-Autoconverted: from quoted-printable to 8bit by server.domain.org id
> l4HJRKUm015411
>
Hi Matthew -
I just fixed my copy of spamass-milter to bypass spamassassin for
authenticated messages, and I'm wondering if you are running into the
same problem. There was a bypass patch posted for it in 2004 on the
spamass-milt-list mailing list. See -
http://lists.nongnu.org/archive/html/spamass-milt-list/2004-03/msg00008.html
One problem is that spamass-milter doesn't pass the whole received line
to spamassassin, so it never sees the part of the line with
(authenticated bits=0).
Dan Schwartz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGTLschCibbju3xzcRAqfDAJ4lOKn79eRJOiLI6Jn5TM5/w5F6OgCgy/KZ
rmqvPC/cz88DQ8M7DIMLaM4=
=41zU
-----END PGP SIGNATURE-----