Re: HOWTO: DKIM Signing with Kolab 16 on Debian 9

Hello Jan,

Sorry in the test before I did not use non-ASCIIs in the body, so I 
repeated the test with Umlauts.

Still everything seems OK for me:
-----------------------------------------------------
Return-Path: 	<[email protected]>
X-Spam-Checker-Version: 	SpamAssassin 3.4.0 (2014-02-07) on 
otherhost.otherdomain.com
X-Spam-Level:
X-Spam-Status: 	No, score=-99.4 required=4.0 
tests=BODY_SINGLE_WORD,DKIM_SIGNED, 
DKIM_VALID,DKIM_VALID_AU,SPF_HELO_NONE,SPF_PASS,USER_IN_WHITELIST 
autolearn=no autolearn_force=no version=3.4.0
X-Original-To: 	[email protected]
Delivered-To: 	[email protected]
Received: 	from myhost.mydomain.com (myhost.mydomain.com [1.2.3.4]) by 
otherhost.otherdomain.com (Postfix) with ESMTPS id 231963DE76 for 
<[email protected]>; Mon, 9 Sep 2019 12:31:18 +0200 (CEST)
DKIM-Filter: 	OpenDKIM Filter v2.11.0 otherhost.otherdomain.com 
231963DE76
Authentication-Results: 	otherhost.otherdomain.com; dkim=pass (4096-bit 
key) header.d=mydomain.com [email protected] header.b="gRrdhOg8"
To: 	[email protected]
DKIM-Signature: 	v=1; a=rsa-sha256; c=relaxed/simple; d=mydomain.com; 
s=myhost; t=1568025078; bh=xd+HXsc...; h=To:From:Subject:Date:From; 
b=gRrdh...
 From: 	Peter Koch <[email protected]>
Subject: 	Test 2
Message-ID: 	<[email protected]>
Date: 	Mon, 9 Sep 2019 12:31:17 +0200
MIME-Version: 	1.0
Content-Type: 	text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 	quoted-printable
Message contents

äöüÄÜÖ
-----------------------------------------------------

Kind regards
Peter

Am 09.09.2019 11:53, schrieb Jan Kowalsky:
> Hi Peter,
> 
> Am 08.09.19 um 19:48 schrieb Koch, Peter:
>> After fighting quite a bit to get DKIM signing to work, I finally
>> succeeded.
>> The existing documentation did not help much so I decided to write a
>> howto for Kolab 16 on Debian 9:
>> 
>> https://diala.org/dokuwiki/howto/dkim_signing_with_kolab_16_on_debian_9
> 
> great, thanks a lot.
> 
> By the way: did you encounter the problem that wallace parses messages
> after they are already signed by dkim?
> 
> We got the problem that in the mail flow it's working like this:
> 
>  Postfix SMTPD
>        |
>        V
>      Milter (dkim signature)
>        |
>        V
>     Wallace
> 
> While wallaces seems to enforce mails with non ascii characters to
> quoted printable encoding (even if the mail clients submits it with
> 8bit) the message is rewritten by wallace with the result that dkim
> signature is broken:
> 
>   https://lists.kolab.org/pipermail/users/2018-May/021441.html
> and ff.:
>   https://lists.kolab.org/pipermail/users/2018-June/021442.html
> 
> I would appreciate if you could test your dkim signing against emails
> from an email client which doesn't encode mails in quoted printable -
> and instead does 8 bit utf8 if any special characters are used.
> 
> Thunderbird e.g. does this with default (mail.strictly_mime set to 
> false).
> 
> Kind regards
> Jan
> _______________________________________________
> users mailing list
> [email protected]
> https://lists.kolab.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://lists.kolab.org/mailman/listinfo/users