Re: received-header: unparseable:

2009-08-17 Thread mouss
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

Re: received-header: unparseable:

2009-08-17 Thread Mark Martinec
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

Re: received-header: unparseable:

2009-08-16 Thread LuKreme
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

Re: received-header: unparseable:

2009-08-16 Thread Chris
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 > > smtpo

Re: received-header: unparseable:

2009-08-16 Thread mouss
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.

RE: received-header: unparseable:

2009-08-16 Thread Michael Hutchinson
> -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 > -t. Is this having an effe

Re: Received header unparseable

2006-09-27 Thread benthere-nine
A second attempt tests much better. Added at line 747: # Received: from ([10.0.0.6]) by myfirewalll; Thu, # 13 Mar 2003 06:26:21 -0500 (EST) if (/^from \(\[(${IP_ADDRESS})\]\) by myfirewall/) { $mta_looked_up_dns = 1; $helo = $1; $ip = $1; $by = 'myfirewall'; goto enough;

Re: Received header unparseable

2006-09-27 Thread benthere-nine
In a desperate newbie attempt to fix this problem myself, I added the following lines to Received.pm at line 895: # Received: from ([10.0.0.6]) by myfirewalll; Thu, # 13 Mar 2003 06:26:21 -0500 (EST) if (/^from \(\[(${IP_ADDRESS})\]\) by myfirewall/) { $ip = $1; $by = 'my.firewa