So I understand the milter protocol requires the own local received
header to not be present, and Postfix hides it from milters. However, SA
considers internal only headers above the first Received. So, the
spamassassin as a milter architecture makes passing internal headers to
SA impossible.
Elod G
On 11/19/2015 12:27, Reindl Harald wrote:
>
>
> Am 19.11.2015 um 11:25 schrieb Reindl Harald:
>>
>> Am 19.11.2015 um 11:22 schrieb Elod G:
>>> Looking at the spamass-milter source code I see this:
>>> if (assassin->numrcpt() == 0)
>>> {
>>> /* Send the envelope headers as X-Envelope-From: and
>>> X-Envelope-To: so that SpamAssassin can use them in its
>>> whitelist checks. Also forge as complete a dummy
>>> Received: header as possible because SA gets a lot of
>>> info from it.
>>>
>>> This is what hides any other headers from SA's ALL-INTERNAL variable. I
>>> still don't understand why this milter has to forge headers and not let
>>> SA work on the actual ones
>>
>> because the *own local received header* is hidden from milters
>> it can't let SA work on anything which don't exist yet
>
> Bugfix for Postfix 2.11, 2.10, 2.9 and 2.8:
>
> Fix for configurations that prepend message headers with Postfix
> access maps, policy servers or Milter applications. Postfix now hides
> its own Received: header from Milters and exposes prepended headers to
> Milters, regardless of the mechanism used to prepend a header. This
> fix reverts a partial solution that was released on October 13, 2014,
> and replaces it with a complete solution
>
