You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Chris <cp...@embarqmail.com> on 2009/08/17 00:44:40 UTC
received-header: unparseable:
I keep seeing this when running some messages throught spamassassin -D
-t. Is this having an effect on whether or not short circuit works?
received-header: unparseable: from spam01.embarq.synacor.com (LHLO
smtpout01.embarq.synacor.com) (10.50.1.1) by md29.embarq.synacor.com
with LMTP;
Should this be in my trusted_networks in local.cf:
10.50.1/24
--
KeyID 0xE372A7DA98E6705C
Re: received-header: unparseable:
Posted by Mark Martinec <Ma...@ijs.si>.
On Monday 17 August 2009 08:45:03 LuKreme wrote:
> > Received: from spam05.embarq.synacor.com (LHLO
> > smtpout01.embarq.synacor.com) (10.50.1.5) by md29.embarq.synacor.com
> > with LMTP; Sun, 16 Aug 2009 19:19:56 -0400 (EDT)
>
> LMTP? Seriously? Does anyone use that? Well, yes, evidently.
A significant number of backends use LMTP for delivery to a mailbox,
nothing unusual about it. The above header field is syntactically
correct (interpreting the parenthesized text as a comment), although
its semantics is probably twisted (the helo and what-could-be-a-TCP-info
are swapped).
> Anyway, the line is not parsed, so it's not relevant to SA and not
> used by SA. In fact, you can consider it to be invisible to SA.
I hope that it is true, i.e. that it does not break the chain of
consecutive trusted trace fields.
Mark
Re: received-header: unparseable:
Posted by mouss <mo...@ml.netoyen.net>.
LuKreme a écrit :
> On 16-Aug-2009, at 18:03, Chris wrote:
>> Received: from spam05.embarq.synacor.com (LHLO
>> smtpout01.embarq.synacor.com) (10.50.1.5) by md29.embarq.synacor.com
>> with LMTP; Sun, 16 Aug 2009 19:19:56 -0400 (EDT)
>
>
> LMTP? Seriously? Does anyone use that? Well, yes, evidently.
of course. LMTP is a standard.
>
> Anyway, the line is not parsed, so it's not relevant to SA and not used
> by SA. In fact, you can consider it to be invisible to SA.
>
It will trigger UNPARSEABLE_RELAY, which default score is 0.001.
Re: received-header: unparseable:
Posted by LuKreme <kr...@kreme.com>.
On 16-Aug-2009, at 18:03, Chris wrote:
> Received: from spam05.embarq.synacor.com (LHLO
> smtpout01.embarq.synacor.com) (10.50.1.5) by md29.embarq.synacor.com
> with LMTP; Sun, 16 Aug 2009 19:19:56 -0400 (EDT)
LMTP? Seriously? Does anyone use that? Well, yes, evidently.
Anyway, the line is not parsed, so it's not relevant to SA and not
used by SA. In fact, you can consider it to be invisible to SA.
--
Bowling scores are way up, minigolf scores are way down, and we
have more excellent waterslides than any other planet we
communicate with
Re: received-header: unparseable:
Posted by Chris <cp...@embarqmail.com>.
On Mon, 2009-08-17 at 01:22 +0200, mouss wrote:
> Chris a écrit :
> > I keep seeing this when running some messages throught spamassassin -D
> > -t. Is this having an effect on whether or not short circuit works?
> >
> > received-header: unparseable: from spam01.embarq.synacor.com (LHLO
> > smtpout01.embarq.synacor.com) (10.50.1.1) by md29.embarq.synacor.com
> > with LMTP;
> >
>
> the format is not recognized. not really an issue since this is a
> "local" relay line.
>
> What software generateds this line? can you show the full header?
>
> > Should this be in my trusted_networks in local.cf:
>
> no. this won't change anything. if SA says the line is not parsable,
> then the IP in the line isn't parsed.
>
> >
> > 10.50.1/24
> >
>
I couldn't find the exact post but all in my inbox contain the similiar
line. Here are all headers minus the SA markup:
Received: from pop.embarqmail.com [208.47.184.129] by
localhost.localdomain with POP3 (fetchmail-6.3.9) for
<cp...@localhost> (single-drop); Sun, 16 Aug 2009 18:21:00 -0500
(CDT)
Received: from spam05.embarq.synacor.com (LHLO
smtpout01.embarq.synacor.com) (10.50.1.5) by md29.embarq.synacor.com
with LMTP; Sun, 16 Aug 2009 19:19:56 -0400 (EDT)
Return-path: <ow...@ema3lsv06.turner.com>
X-binding: md29.embarq.synacor.com
X-cmae-whitelist: YES
X_cmae_category: 0,0 Undefined,Undefined
X-cnfs-analysis: v=1.0 c=1 a=HgbDHJuKAAAA:8 a=PNnWT_N-lLNevInYF7IA:9
a=TWuli8_fnVi7Vfb2VDcA:7 a=ctBsUv0MhcFH_AVhxCwKj_KngRoA:4
a=B9WObwvXIC4A:10 awl=host:1027
X-cm-score: 0
X-scanned-By: Cloudmark Authority Engine
Authentication-results: spam05.embarq.synacor.com
smtp.mail=owner-TEXTBREAKINGNEWS@EMA3LSV06.TURNER.COM; spf=pass
Received-spf: pass (spam05.embarq.synacor.com: domain
EMA3LSV06.TURNER.COM designates 157.166.236.51 as permitted sender)
Received: from [157.166.236.51] ([157.166.236.51:32777]
helo=p17.web2.mail.cnn.com) by smtp.embarq.synacor.com (envelope-from
<ow...@ema3lsv06.turner.com>) (ecelerity 2.2.2.36
r(27513/27514)) with ESMTP id 0C/32-02964-C14988A4; Sun, 16 Aug 2009
19:19:56 -0400
Date: Sun, 16 Aug 2009 19:19:56 -0400 (18:19 CDT)
Received: from ema3lsv06 (157.166.236.30) by p17.web2.mail.cnn.com
(PowerMTA(TM) v3.5r6) id hh2a1s0j3k4l; Sun, 16 Aug 2009 19:10:29 -0400
(envelope-from <ow...@EMA3LSV06.TURNER.COM>)
X-Job: 20090816191016.textbreakingnews.18417
Message-id: <20...@mail.cnn.com>
From: CNN Breaking News <Br...@mail.cnn.com>
To: textbreakingnews@ema3lsv06.turner.com
Subject: CNN Breaking News
X-senderip: 157.166.236.51
X-asn: ASN-5662
X-cidr: 157.166.224.0/20
Chris
--
KeyID 0xE372A7DA98E6705C
Re: received-header: unparseable:
Posted by mouss <mo...@ml.netoyen.net>.
Chris a écrit :
> I keep seeing this when running some messages throught spamassassin -D
> -t. Is this having an effect on whether or not short circuit works?
>
> received-header: unparseable: from spam01.embarq.synacor.com (LHLO
> smtpout01.embarq.synacor.com) (10.50.1.1) by md29.embarq.synacor.com
> with LMTP;
>
the format is not recognized. not really an issue since this is a
"local" relay line.
What software generateds this line? can you show the full header?
> Should this be in my trusted_networks in local.cf:
no. this won't change anything. if SA says the line is not parsable,
then the IP in the line isn't parsed.
>
> 10.50.1/24
>
RE: received-header: unparseable:
Posted by Michael Hutchinson <mh...@manux.co.nz>.
> -----Original Message-----
> From: Chris [mailto:cpollock@embarqmail.com]
> Sent: Monday, 17 August 2009 10:45 a.m.
> To: users@spamassassin.apache.org
> Subject: received-header: unparseable:
>
> I keep seeing this when running some messages throught spamassassin -D
> -t. Is this having an effect on whether or not short circuit works?
>
> received-header: unparseable: from spam01.embarq.synacor.com (LHLO
> smtpout01.embarq.synacor.com) (10.50.1.1) by md29.embarq.synacor.com
> with LMTP;
Is "LHLO" a valid SMTP command? Perhaps this is causing the unparseable
header problem..
> Should this be in my trusted_networks in local.cf:
>
> 10.50.1/24
>
> --
> KeyID 0xE372A7DA98E6705C