head	1.1;
access;
symbols
	pkgsrc-2024Q1:1.1.0.8
	pkgsrc-2024Q1-base:1.1
	pkgsrc-2023Q4:1.1.0.6
	pkgsrc-2023Q4-base:1.1
	pkgsrc-2023Q3:1.1.0.4
	pkgsrc-2023Q3-base:1.1
	pkgsrc-2023Q2:1.1.0.2
	pkgsrc-2023Q2-base:1.1;
locks; strict;
comment	@.\" @;


1.1
date	2023.04.21.13.03.09;	author manu;	state Exp;
branches;
next	;
commitid	gogzkVtS2RohyYlE;


desc
@@


1.1
log
@Add missing patch, as pointed by wiz@@
Split patch as one per patched file, as requested by sketch@@
@
text
@$NetBSD$

Add OmitHeadersDB directive to specify file containing per-recipient 
list of headers to not use in signature. The file format is:

user@@doamin.tld	header1,header2,header3
domain.tld	header4,header5

From upstream https://github.com/trusteddomainproject/OpenDKIM/pull/173

--- opendkim/opendkim.conf.5.in.orig
+++ opendkim/opendkim.conf.5.in
@@@@ -619,6 +619,15 @@@@ default; for example, "*,+foobar" will use the entire default list plus
 the name "foobar", while "*,-Bcc" would use the entire default list except
 for the "Bcc" entry.
 
+.TP
+.I OmitHeadersDB (string)
+Specify a file containing a per-recipient list of headers to omit 
+when generating signatures. Return-Path, Received, Comments, and
+Keywoard are implicitely added to the list. The file should have
+two columns : a recipient as user@@domain.tld or domain.tld, and 
+a comma-separated lis of headers to omit. For example 
+"list@@example.net Subject,Bcc"
+
 .TP
 .I On-BadSignature (string)
 Selects the action to be taken when a signature fails to validate.
@