I'm sure that there are a lot of other rules that aren't behaving correctly because of 300558 on Debian, that just
don't fail as spectacularly or obviously as ALL_TRUSTED, because of
the lack of Received parsing.
Yeah, that could well be, good point.
For example, I'm quite suspicious of the way SA's SPF checking is working -- it seems to be testing the wrong set of Received headers to me. I'm guessing this is because it can't parse the correct set.
Yeah, I expect that the SA maintainer is going to forward this one
upstream.
OK! I think they are pretty busy... I've been trying to do some helping by forwarding, reviewing, talking with upstream and stuff.
Feel free to forward this to the upstream Bugzilla, if you think it's appropriate.
However, could you perhaps ask the Exim folks how the Received headers are built, perhaps that makes it clear why SA fails to parse them.
Well, you and I are both running Exim here, so a quick look at our mail exchange provides some exemplars:
Received: from pooh.kjernsmo.net ([217.77.32.186])
by pyloric.projectile.ca with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32)
(Exim 4.44)
id 1DDO0Z-0002aI-9h
for [EMAIL PROTECTED]; Mon, 21 Mar 2005 09:36:00 -0500
Received: from ti100710a080-8594.bb.online.no ([85.165.33.146])
by pooh.kjernsmo.net with esmtp (Exim 4.44)
id 1DDO0V-0003Ug-SE; Mon, 21 Mar 2005 15:35:52 +0100- Marc
- Marc
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
