Ben Wylie writes:
> >> Received: (from localhost [24.180.47.240])
> >> by server. (NAVGW 2.5.2.12) with SMTP id M2006060503484615455
> >> for <[EMAIL PROTECTED]>; Mon, 05 Jun 2006 03:48:47 +0100
> >
> > OK, we specifically skip received headers that start with "(" at line
> > 387 of Received.pm
Ben Wylie wrote:
If you had the time to write a patch for this I would be very grateful, and
let me know what I would need to do to apply the patch, and if I would need
to make changes every time I upgraded.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4943
Daryl
Ben Wylie wrote:
Received: (from localhost [24.180.47.240])
by server. (NAVGW 2.5.2.12) with SMTP id M2006060503484615455
for <[EMAIL PROTECTED]>; Mon, 05 Jun 2006 03:48:47 +0100
OK, we specifically skip received headers that start with "(" at line
387 of Received.pm. Annoyingly, we don't pro
Ben Wylie wrote:
> > > Received: (from localhost [24.180.47.240])
> > > by server. (NAVGW 2.5.2.12) with SMTP id M2006060503484615455
> > > for <[EMAIL PROTECTED]>; Mon, 05 Jun 2006 03:48:47 +0100
>
> > What broken-ass software is producing these received headers? "by
> > server." certainly isn
>> Received: (from localhost [24.180.47.240])
>> by server. (NAVGW 2.5.2.12) with SMTP id M2006060503484615455
>> for <[EMAIL PROTECTED]>; Mon, 05 Jun 2006 03:48:47 +0100
>
> OK, we specifically skip received headers that start with "(" at line
> 387 of Received.pm. Annoyingly, we don't provide
On 6/4/2006 11:28 PM, Ben Wylie wrote:
Received: from [127.0.0.1] by arkbb.co.uk with SMTP (HELO server.)
(ArGoSoft Mail Server Pro for WinNT/2000/XP, Version 1.8 (1.8.8.2)); Mon,
5 Jun 2006 03:48:52 +0100
Received: (from localhost [24.180.47.240])
by server. (NAVGW 2.5.2.12) with SMTP id M2
>Current versions of SpamAssassin won't fire ALL_TRUSTED if it can't
>parse all of the received headers.
>
> Since you provided no current debug info, or even said what version you
> are using, I can only guess at what you're problem might be. Are you
> sure it's not parsing the header and isn'
On 6/4/2006 9:54 PM, Ben Wylie wrote:
I have had a problem with a particular form of received header not being
parsed correctly because it is malformed. I had a brief conversation on this
list about a year ago with a glimmer of hope that in future versions this
would be overcome. However a year l
I have had a problem with a particular form of received header not being
parsed correctly because it is malformed. I had a brief conversation on this
list about a year ago with a glimmer of hope that in future versions this
would be overcome. However a year later these emails are still being marked
> I am using 3.0.3 on Windows 2003.
> What is the fix? Will it recognise it as a received header even though it
is
> invalid?
No. Well, I believe there have been some changes in received header
parsing, so some valid headers not recognized on .3 will be correctly
recognized. But this isn't that
>> Why was the second header not parsed?
>
> Invalid format. Need "from" as the first word, not "(from".
Ok thanks.
I don't know why it has it in that format. It was put in by my AV proxy,
which usually has valid headers:
Received: from a.mx.bluesine.com ([66.18.211.109])
by server. (NAVGW 2.5.
> Received: (from localhost [218.232.123.135])
> by server. (NAVGW 2.5.2.12) with SMTP id M2005060510393927686
> for <[EMAIL PROTECTED]>; Sun, 05 Jun 2005 10:39:39 +0100
>
> Why was the second header not parsed?
Invalid format. Need "from" as the first word, not "(from".
> It was given an all
12 matches
Mail list logo
