Hi [2019-05-05 19:41] Dmitry Bogatov <kact...@debian.org> > mmh sometimes generates boundary separators in multipart messages with > non-ascii symbols in it. Not sure about RFC-compliance, but at least > Python standard library does not work well with them. > > Here is example of problematic separator: > > --21189_ĵaŭ_Maj__2_15_03_59_UTC_2019 > > Notice non-ascii "ĵ" letter. The separator looks like output of date(1) > (my locale is eo.utf-8).
This is clearly not rfc compliant. > According to my investigation, such boundary is generated in mhsign.sh > script, newboundary() function, line 185 (in mmh=0.4 release), which > have following line: > > b=$$_`date|sed 's/[ : ]/_/g'` > > I think the simpliest fix would be using C locale for date. Patch is > attached. Not sure, whether it is safe to export LC_ALL=C at top of > script. Your patch looks good. I'll add it to the repo. Adding export LC_ALL=C to the hole script causes problems, like diffrent messages from gpg. Philipp
