qpsmtpd/sme10/qpsmtpd-0.96-SME10139-Message-Id.patch

diff -Nur qpsmtpd-0.96.old/plugins/headers qpsmtpd-0.96/plugins/headers
--- qpsmtpd-0.96.old/plugins/headers    2016-02-16 17:52:02.000000000 -0500
+++ qpsmtpd-0.96/plugins/headers        2017-03-08 11:59:48.411000000 -0500
@@ -18,6 +18,8 @@
 
 If the remote IP is whitelisted, header validation is skipped.
 
+As per March 2017 it has been reported some well known senders are putting multiple Message-Id. As a result we removed Message-Id from the singular_headers array. See https://bugs.contribs.org/show_bug.cgi?id=9773
+
 =head1 CONFIGURATION
 
 The following optional settings exist:
@@ -106,8 +108,8 @@
 
 #my @should_headers   = qw/ Message-ID /;
 my @singular_headers = qw/ Date From Sender Reply-To To Cc Bcc
-  Message-Id In-Reply-To References
-  Subject /;
+  In-Reply-To References
+  Subject /; # <- to be RFC 5322 complient add Message-Id here
 
 sub register {
     my ($self, $qp) = (shift, shift);
1	diff -Nur qpsmtpd-0.96.old/plugins/headers qpsmtpd-0.96/plugins/headers
2	--- qpsmtpd-0.96.old/plugins/headers 2016-02-16 17:52:02.000000000 -0500
3	+++ qpsmtpd-0.96/plugins/headers 2017-03-08 11:59:48.411000000 -0500
4	@@ -18,6 +18,8 @@
5
6	If the remote IP is whitelisted, header validation is skipped.
7
8	+As per March 2017 it has been reported some well known senders are putting multiple Message-Id. As a result we removed Message-Id from the singular_headers array. See https://bugs.contribs.org/show_bug.cgi?id=9773
9	+
10	=head1 CONFIGURATION
11
12	The following optional settings exist:
13	@@ -106,8 +108,8 @@
14
15	#my @should_headers = qw/ Message-ID /;
16	my @singular_headers = qw/ Date From Sender Reply-To To Cc Bcc
17	- Message-Id In-Reply-To References
18	- Subject /;
19	+ In-Reply-To References
20	+ Subject /; # <- to be RFC 5322 complient add Message-Id here
21
22	sub register {
23	my ($self, $qp) = (shift, shift);