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, evidentl
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 sign
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 pars
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 spam
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.
> -Original Message-
> From: Chris [mailto:cpoll...@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
&g
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
t;>
>> 20_head_tests.cf hits on this as an UNPARSEABLE_RELAY.
>> SA isn't able to look up that IP address on all the
>> network tests.
>>
>> I'm e-mailing Tech Support for the company that
>> publishes the firewall software, but is there anything
>> that can be done on the SA side?
>>
>> Thank you very much.
>>
>
>
--
View this message in context:
http://www.nabble.com/Received-header-unparseable-tf2340368.html#a6539503
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
or the company that
> publishes the firewall software, but is there anything
> that can be done on the SA side?
>
> Thank you very much.
>
--
View this message in context:
http://www.nabble.com/Received-header-unparseable-tf2340368.html#a6529150
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
My firewall puts a received header on every e-mail it
forwards to SA 3.1.5:
Received: from f66108.upc-f.chello.nl ([80.56.66.108])
by myfirewall; Tue, 26 Sep 2006 12:35:52 -0500
(Central Daylight Time)
But when my firewall can't find a DNS entry for the
e-mail's last relay IP address, it just put
10 matches
Mail list logo
