It worked before, but now (don't know for how long actually) the e-mails I'm receiving about inline comments on commits looks very broken:

This is how that inline commit looks like on Phabricator:

So I get this:

 Работает непр
едсказуемо ко
гда делаешь ри
сет конфигов.

instead of this:

Работает непредсказуемо когда делаешь рисет конфигов.

I'm using Gmail to view e-mails and it's known that it reformats encoded e-mail body to have 80 symbols max per line. This makes sense for e-mails in English that are not encoded in any way. This also doesn't break 100% quoted printable e-mails or base64-encoded ones.

However MetaMTA seems to create some mixed form of e-mail (encoded + not encoded) and wherever Gmail splits actually affects decoded e-mail content making it unusable. The effect is worser with non-English letters (e.g. Russian) when single letter can correspond to 3 bytes of encoded text.

Here is "View Original" of received e-mail (no headers, since they are irrelevant to a problem, because I'm receiving e-mail after all):

volodimir added inline comments.=0A=0AINLINE COMMENTS=0A  /projects/asico/t=

runk/modules/custom/units/sections/in-commerce/products/e_product_eh.php:85=

 =D0=A0=D0=B0=D0=B1=D0=BE=D1=82=D0=B0=D0=B5=D1=82 =D0=BD=D0=B5=D0=BF=D1=80=

=D0=B5=D0=B4=D1=81=D0=BA=D0=B0=D0=B7=D1=83=D0=B5=D0=BC=D0=BE =D0=BA=D0=BE=

=D0=B3=D0=B4=D0=B0 =D0=B4=D0=B5=D0=BB=D0=B0=D0=B5=D1=88=D1=8C =D1=80=D0=B8=

=D1=81=D0=B5=D1=82 =D0=BA=D0=BE=D0=BD=D1=84=D0=B8=D0=B3=D0=BE=D0=B2.=0A=0AU=

SERS=0A  volodimir (Author)=0A=0ACOMMIT=0A  http://qa.intechnic.com/rASI142=

78=0A=0AREPLY HANDLER ACTIONS=0A  Reply to comment.=0A=0ATo: volodimir, ale=

x=0ACc: alex=0A

The error in way, how MetaMTA is encoding e-mail is much more visible. You can see USERS word from e-mail, but MetaMTA suddenly decided to encode U (see U=) letter but not SERS (on next line, SERS=0A).