On Sun, Nov 11, 2018 at 12:23:53PM +0200, Henrik K wrote: > > I have milter chain opendkim->opendmarc->amavisd-milter for incoming > external mail. Postfix 3.1.0 from Ubuntu 16.04.5. > > As I understand, the correct positioning of milter inserted internal headers > would be above postfix's own. But it seems all Authentication-Results are > added below it, so SpamAssassin won't consider them as internal. > > Return-Path: <x...@xxx.com> > X-Spam-Status: ... > Received: from xxx (xxx [1.2.3.4]) > by hege.li (Postfix) with ESMTP id xxxxxxxx > for <h...@hege.li>; Thu, 8 Nov 2018 16:55:03 +0200 (EET) > Authentication-Results: hege.li; dmarc=none (p=none dis=none) header.from=xxx > Authentication-Results: hege.li; spf=pass smtp.mailfrom=xxx > Authentication-Results: hege.li; > dkim=pass (1024-bit key; unprotected) header.d=xxx.com > header.i=@xxx.com header.b=xxx; > dkim-atps=neutral > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > d=xxx.com; s=s1024; ... > Received: from xxx.com ... > From: Fubar <x...@xxx.com> > > Both open* milters seem to insert the header at index 1. > > dmarcf_insheader(ctx, 1, AUTHRESULTSHDR.. > dkimf_insheader(ctx, 1, AUTHRESULTSHDR.. > > I found some old talk about indexes etc, but I'm still confused. What needs > to be done so they end up above postfix's own header?
Compiled new opendmarc that inserts to index 0 and it ends up correctly above postfix's header. I guess many people have this problem without realizing it. Sigh, yet more custom patched packages to run..
