From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 60404385841E; Sat, 5 Nov 2022 00:17:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 60404385841E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1667607461; bh=rqYC6/XX76Q1kGkMCso68JgaZOujmMG1XXtiF0jEJiQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=OXlO+P+e5jIriwvbsLQ8nREz3BIO++B1EmyyGmgjO+TKCCavptys7FqVtrMcjzzli +EXcurpsaDk1ZxomnsSQenEJ2Xo7E/jxU59h2y3w0/78Kj+NU5wVnz1Plb45sy6OBN ZpiiYGekVAfy5u9lZPtxRfnp6levOO/1GPz4TLrA= From: "mark at klomp dot org" To: overseers@sourceware.org Subject: =?UTF-8?B?W0J1ZyBJbmZyYXN0cnVjdHVyZS8yOTcxM10gUGxlYXNlIG1ha2Ug?= =?UTF-8?B?bGliYy1hbHBoYSBtYWlsaW5nIGxpc3QgY29tcGF0aWJsZSB3aXRoIOKAnGdp?= =?UTF-8?B?dCBhbeKAnQ==?= Date: Sat, 05 Nov 2022 00:17:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: sourceware X-Bugzilla-Component: Infrastructure X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at klomp dot org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: overseers at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29713 --- Comment #23 from Mark Wielaard --- filter_content is set to No. But looking around it seems 8bit content transfer encodings are problematic with DKIM signing in general. The spec says before signing a message 8bit content should be transformed to a 7bit encoding so the signature survives = if any transport doesn't support the 8bit encoding. So it could be said this is just an issue with the mimecast dkim signing in the above case, since it doesn't know that the full transport to the end user is 8bit clean, it shou= ld have transformed to a 7bit encoding itself before signing. There is a postfix setting that seems to try to keep the 8bit content trans= fer encoding even if a transport doesn't explicitly say it supports 8bit encodi= ngs: http://www.postfix.org/postconf.5.html#disable_mime_output_conversion Disable the conversion of 8BITMIME format to 7BIT format. Mime output conversion is needed when the destination does not advertise 8BITMIME suppo= rt.=20 This is recommended for postfix filters and milters to avoid breaking DKIM = etc. signatures: https://www.postfix.org/MILTER_README.html#workarounds https://www.postfix.org/FILTER_README.html#advanced_filter So we probably just need to set disable_mime_output_conversion=3Dyes and ho= pe that any further transports do actually support 8BITMIME. --=20 You are receiving this mail because: You are the assignee for the bug.=