On Thu, 13 Jul 2017, Marc Haber wrote: > On Thu, Jul 13, 2017 at 08:47:56AM +0200, Alexander Wirt wrote: > > I am talking about the report: > > X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up > > entirely of whitespace (char 20 hex): X-Spam_report: ...T_ADDRESS@@ > > for details. Content previ[...] > > If this very header is generated in a non-rfc-conforming way, then it > would be up to amavis to generate it correctly. Not an exim issue. > > The presence of an X-Header does not make the message rfc-uncompliant. > > > This does not belong to outgoing mail. > > The configuration in question is not part of the default configuration. > Only the local admin can judge what constitutes "outgoing" in the site > context. > > I am not opposed to the patch in question, but alas, it doesn't help. This is not about amavis. Amavis is not involved. This is about 40_exim4-config_check_data which uses SpamAssassin with spamd.
Alex