GNOME Bugzilla – Bug 206666
Mails for mail lists arrives with ugly tail
Last modified: 2017-10-09 23:51:39 UTC
If I post something to maillist (gnome-cyr example) and list manager makes addition like identification strings, such additions becomes ugly. Here is example ?z&y??????x%??`·?·s*?·?·??!????f?? ???+?? ?Y ÷?b???~??·?·cyr= One of our list members tells it's because of base64 encoding and problem may be solved with quoted-printable. Can Evolution be tuneable in transfer encoding (8bit, quoted, base64) by user? May be in preferences?
Evolution itself does not show such garbage but other MUAs like Pine or Mozilla do.
See bug 207154 for the reverse of this (sending messages in base64 can get them corrupted.)
Evolution uses (as per rfc) the LEAST POSSIBLE encoding when transferring messages. So this can't really be changed just with a user option. i.e. it will use qp encoding if it can, and still meet other requirements. Namely QP doesn't allow NUL characters (bytes of zero) in the stream, or lines longer than 999 octets. BTW from i can see, this is the same problem as 7154.
*** bug 207154 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 207154 ***
Can anyone explain me why this bug has been closed? With Evolution 3.26.0 I see that e-mails that could have been encoded as 7-bit ASCII e-mails are encoded using Base64. For an example, see e.g.: * https://marc.info/?l=linux-rdma&m=150756901022360 (decoded version) * https://marc.info/?l=linux-rdma&m=150756901022360&q=raw (raw e-mail) Both Evolution and Thunderbird display the last part of that e-mail as follows: That's a good question but I'm not sure what would be a good time to remove this. I think the answer depends on how likely it is that people use this variable in scripts or /etc/modprobe.d configuration files because in that case removing the module parameter would break setups. Bart.�{.n�+�������+%��lzwm��b�맲��r��zX��ݙ�����ܨ}���Ơz�&j:+v�������zZ+��+zf���h���~����i���z��w���?����&�)ߢf