Mailing List Archive: SA tagged something I don't agree with...

SA tagged the following headers as spam (yes, I changed some scores).
However, I don't believe the message should've been tagged since the
message was being received from a legit server.

The message originated on a machine with a dynamic dns, was sent through
the ISP's mail server, and arrived at my server. The dynamic dns caused
the message to be flagged as spam. However, that implies that no matter
what I do, I can't send messages from my own mail server (which is also on
a dynamic dns) without also being considered spam, even though I route
everything outgoing through my ISP's mail server.

I believe this is incorrect behavior, but I wanted to find out if I'm
misunderstanding something.

headers:

Return-Path: <removed-name@verizon.net>
Delivered-To: removed-name@thoughtleap.com
Received: (qmail 30207 invoked from network); 12 Mar 2004 20:49:36 -0000
Received: from out009pub.verizon.net (HELO out009.verizon.net)
(206.46.170.131)
by 10.42.42.1 with SMTP; 12 Mar 2004 20:49:36 -0000
Received: from Tom ([129.44.9.106]) by out009.verizon.net
(InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP
id <20040312204934.RYTV29216.out009.verizon.net@Tom>
for <removed-name@thoughtleap.com>; Fri, 12 Mar 2004 14:49:34 -0600
From: "removed-name" <removed-name@verizon.net>
To: removed-name <removed-name@thoughtleap.com>
Date: Fri, 12 Mar 2004 15:47:44 -0500
MIME-Version: 1.0
Subject: test
Message-ID: <4051DBA0.2829.341CCD3@localhost>
Priority: normal
X-mailer: Pegasus Mail for Windows (v4.12a)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Authentication-Info: Submitted using SMTP AUTH at out009.verizon.net
from [129.44.9.106] at Fri, 12 Mar 2004 14:49:33 -0600

At 04:10 PM 3/12/2004, jmorton@thoughtleap.com wrote:
>SA tagged the following headers as spam (yes, I changed some scores).
>However, I don't believe the message should've been tagged since the
>message was being received from a legit server.
>
>The message originated on a machine with a dynamic dns, was sent through
>the ISP's mail server, and arrived at my server. The dynamic dns caused
>the message to be flagged as spam. However, that implies that no matter
>what I do, I can't send messages from my own mail server (which is also on
>a dynamic dns) without also being considered spam, even though I route
>everything outgoing through my ISP's mail server.

Have you verified your trust paths are correct?

Please try adding a 'trusted_networks' statement to your local.cf,
declaring ONLY your mailservers to be trusted.

Some network configs, including NAT, multihome, etc, can confuse SA's
trust-path code, making it think a mailserver that's outside your network
is your border MTA. The purpose of forcing a trusted_networks statement is
to prevent it from trusting the ISPs mailserver.