You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2005/04/15 00:08:01 UTC
Re: SpamAssassin and Horde
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
check the bugzilla -- I'm pretty sure this is fixed for 3.1.0.
- --j.
> Received: from 200-102-255-31.smace701.dsl.brasiltelecom.net.br
> (200-102-255-31.smace701.dsl.brasiltelecom.net.br [200.102.255.31]) by
> domain.tld (Horde) with HTTP for <so...@domain.tld>; Thu Thu,
> 14 Apr 2005 14:19:04 -0300
>
> This is the IP from the computer the user was using to send mail. Some thing
> is very wrong here. Why IMP 4.x takes user ip and send it as Helo?? This
> does no happens with imp 3.x. I guess i have two options one hack imp code
> to send localhost in helo or make spamassasin igonore imp headers.
>
> Any ideas ???
>
> Full headers:
> Return-Path: <so...@domain.tld>
> Delivered-To: other@domain.tld
> Received: from domain.tld (localhost.localdomain [127.0.0.1])
> by odi.com.br (Postfix) with ESMTP id 1C14D19072
> for <ot...@domain.tld>; Thu, 14 Apr 2005 14:19:05 -0300 (BRT)
> Received: by odi.com.br (Postfix, from userid 48)
> id E617919071; Thu, 14 Apr 2005 14:19:04 -0300 (BRT)
> Received: from 200-102-255-31.smace701.dsl.brasiltelecom.net.br
> (200-102-255-31.smace701.dsl.brasiltelecom.net.br [200.102.255.31]) by
> webmail.domain.tld (Horde) with HTTP for <so...@domain.tld>; Thu,
> 14 Apr 2005 14:19:04 -0300
> Message-ID: <20...@webmai.domain.tld>
> Date: Thu, 14 Apr 2005 14:19:04 -0300
> From: someuser@domain.tld
> To: user@domain.tld
> Subject: Teste Testando testado
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset=ISO-8859-1
> Content-Disposition: inline
> Content-Transfer-Encoding: 7bit
> User-Agent: Internet Messaging Program (IMP) H3 (4.0)
> X-AV-Checked: ClamAV using ClamSMTP
> X-Spam-Flag: YES
> X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on odi.com.br
> X-Spam-Level: *****
> X-Spam-Status: Yes, score=5.7 required=5.0 tests=AWL,BAYES_00,
> HELO_DYNAMIC_HCC,HELO_DYNAMIC_IPADDR2,NO_REAL_NAME autolearn=no
> version=3.0.1
> X-Spam-Report:
> * 0.0 NO_REAL_NAME From: does not include a real name
> * 3.5 HELO_DYNAMIC_IPADDR2 Relay HELO'd using suspicious hostname (IP addr
> 2)
> * 3.7 HELO_DYNAMIC_HCC Relay HELO'd using suspicious hostname (HCC)
> * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
> * [score: 0.0000]
> * 1.0 AWL AWL: From: address is in the auto white-list
>
> ----- Original Message -----
> From: "Matt Kettler" <mk...@evi-inc.com>
> To: "Angelo Ayres Camargo" <cr...@odi.com.br>
> Cc: <us...@spamassassin.apache.org>
> Sent: Tuesday, April 12, 2005 2:18 PM
> Subject: Re: SpamAssassin and Horde
>
> > Angelo Ayres Camargo wrote:
> >
> >> Hello,
> >>
> >> Mail sent from horde imp are been taged as spam, this was discussed
> >> here before, searching the archives i found no solution. Anyone have
> >> any ideia of how make mail from Horde/Imp not be taged as spam?
> >>
> >> Angelo
> >
> > Angelo,
> >
> > First, I assume you mean the thread with subject: Confused about
> > HELO_DYNAMIC_*
> >
> > At the end of that thread we concluded it had nothing to do with IMP
> > whatsoever. Instead, it was a NATed mailserver triggering the broken
> > trust path problem.
> >
> > If your inbound MX mailserver is NATed such that it IP is in reserved
> > range (ie: 10.*, 192.168.*, 172.16.*, etc) you MUST declare
> > trusted_networks manually.
> >
> > If you don't, ALL mail originating at dialup accounts that appear in the
> > Received: headers will be heavily penalized. That includes mail sent via
> > IMP by dialup users, but is not IMP specific. Mail sent by a dialup user
> > through even their own ISP's sendmail server will be subject to the same
> > problems.
> >
> >
> > See the wiki for details:
> >
> > http://wiki.apache.org/spamassassin/TrustPath
> >
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFCXunBMJF5cimLx9ARAtfZAJ9juBmRkypLZ45mZTfg/h+3o7wpwwCfS3bd
FzkpxWvTVZo78x3JdSamyF4=
=S3B5
-----END PGP SIGNATURE-----
Re: SpamAssassin and Horde
Posted by "Ângelo A. Camargo" <cr...@odi.com.br>.
How could i forgot checking the bugziila??? Well thank you and sorry for the
wasted time.
Angelo
----- Original Message -----
From: "Justin Mason" <jm...@jmason.org>
Cc: <us...@spamassassin.apache.org>
Sent: Thursday, April 14, 2005 7:08 PM
Subject: Re: SpamAssassin and Horde
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> check the bugzilla -- I'm pretty sure this is fixed for 3.1.0.
>
> - --j.
>
>
Re: SpamAssassin and Horde
Posted by JP Kelly <li...@jpkvideo.net>.
regarding the problem where mail from horde gets hit with
HELO_DYNAMIC_DHCP rule due to sender's IP address.
see below...
do you mean SA 3.1?
On Apr 14, 2005, at 3:08 PM, Justin Mason wrote:
>
>
> check the bugzilla -- I'm pretty sure this is fixed for 3.1.0.
>
> - --j.
>
>>
>> This is the IP from the computer the user was using to send mail.
>> Some thing
>> is very wrong here. Why IMP 4.x takes user ip and send it as
>> Helo?? This
>> does no happens with imp 3.x. I guess i have two options one hack
>> imp code
>> to send localhost in helo or make spamassasin igonore imp headers.
Re: SpamAssassin and Horde
Posted by "J.P. Kelly" <jp...@jpkvideo.com>.
regarding the problem where mail from horde gets hit with
HELO_DYNAMIC_DHCP rule due to sender's IP address.
see below...
do you mean SA 3.1?
On Apr 14, 2005, at 3:08 PM, Justin Mason wrote:
>
>
> check the bugzilla -- I'm pretty sure this is fixed for 3.1.0.
>
> - --j.
>
>>
>> This is the IP from the computer the user was using to send mail.
>> Some thing
>> is very wrong here. Why IMP 4.x takes user ip and send it as
>> Helo?? This
>> does no happens with imp 3.x. I guess i have two options one hack
>> imp code
>> to send localhost in helo or make spamassasin igonore imp headers.
Re: SpamAssassin and Horde
Posted by "J.P. Kelly" <jp...@jpkvideo.com>.
do you mean SA 3.1?
On Apr 14, 2005, at 3:08 PM, Justin Mason wrote:
>
>
> check the bugzilla -- I'm pretty sure this is fixed for 3.1.0.
>
> - --j.
>
>> Received: from 200-102-255-31.smace701.dsl.brasiltelecom.net.br
>> (200-102-255-31.smace701.dsl.brasiltelecom.net.br
>> [200.102.255.31]) by
>> domain.tld (Horde) with HTTP for <so...@domain.tld>; Thu Thu,
>> 14 Apr 2005 14:19:04 -0300
>>
>> This is the IP from the computer the user was using to send mail.
>> Some thing
>> is very wrong here. Why IMP 4.x takes user ip and send it as
>> Helo?? This
>> does no happens with imp 3.x. I guess i have two options one hack
>> imp code
>> to send localhost in helo or make spamassasin igonore imp headers.