On October 30, 2014 8:07:32 PM "Dmitry E. Mikhailov"
<d.mikhailov_at_infocommunications.ru> wrote:
> Hi,
>
> CentOS 5/i386, Postfix 2.3.3 and OpenDKIM 2.9.2 installed
>
> Trying to send the message with overly long UTF8 "From:" header:
>
> From: =?UTF-8?Q?=D0=9A=D0=BE=D0=BC=D0=BF=D0=B0=D0=BD=D0=B8=D1=8F_=22?=
> =?UTF-8?Q?=D0=9F=D1=80=D0=BE=D0=BC=D1=8B=D1=88=D0=BB=D0=B5=D0=BD=D0=BD?=
> =?UTF-8?Q?=D0=BE=D0=B5_=D0=9E=D0=B1=D0=BE=D1=80=D1=83=D0=B4=D0=BE=D0=B2?=
> =?UTF-8?Q?=D0=B0=D0=BD=D0=B8=D0=B5=22?= <kpo_at_ufaprom.ru>
>
> OpenDKIM won't sign:
> Oct 30 13:01:50 ufaprom opendkim[17058]: (unknown-jobid): no signing
> table match for 'kpo_at_uf'
> Oct 30 13:01:50 ufaprom opendkim[17058]: 6337A1248920: no signature data
>
> Looks like there's ~256 byte limit somewhere. IMHO it's in
> libopendkim/dkim-mailparse.c because it takes a string and returns
> strings. But I wasn't able to fully understand the C code.
http://takahisa.info/2010/03/11/setup-dkim-on-postfix-with-amavisd-new/
See 8bitmime, as i see it its doubble 8bit encoded first level with
qoutedprintelble, and then again with utf-8, only one is needed :)
If you dont use amavisd then only way is to disable this in postfix, dont
know here how milters handle it, bugfix in opendkim could be to remove
doupple encoindings?
Try allow 8bit in mua, so mua does not encode 8bit, but possible just send
as utf-8, hoppefully this will solve it
Received on Fri Oct 31 2014 - 05:06:18 PST