[opensuse-factory] Character Encoding and strange fonts below my signature
Hi, Due some unwanted behavior I had by using my yahoo.com and gmail.com accounts on this mailing-list I switched to hotmail.com as you can observe by my email. Well, I was noticing a strange behavior which I don't yet discovered if it is due the Mail provider itself (outlook.com) or some setting on my Thunderbird mail client. One fact I discovered just now is that on systems (personal computers) wherein I set the Character Encoding = UTF-8, some strange fonts are displayed on my e-mail messages sent on the list, when I receive back from opensuse-factory: Example 1: -- For every action, there is an equal and opposite criticism. �{.n�+����������� }�-����{.n�+������Ǩ��r��i�m��0��ޙ������� }�-���� ޮ�^�ˬz� Example 2: -- TThheerree''ss aann EEcchhoo iinn hheerree. N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ� Whereas on the pc I'm using now, where Thunderbird is using Character Encoding = ISO-88591-1, this behavior doesn't appears. -- Marco Calistri N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
On Tuesday 2017-10-31 15:09, Marco Calistri wrote:
Due some unwanted behavior I had by using my yahoo.com and gmail.com accounts on this mailing-list I switched to hotmail.com as you can observe by my email.
Well, I was noticing a strange behavior which I don't yet discovered if it is due the Mail provider itself (outlook.com) or some setting on my Thunderbird mail client.
One fact I discovered just now is that on systems (personal computers) wherein I set the Character Encoding = UTF-8, some strange fonts are displayed on my e-mail messages sent on the list, when I receive back from opensuse-factory:
Example 1:
-- For every action, there is an equal and opposite criticism. ???{.n???+????????????????????????????????? }???-????????????{.n???+??????????????????Ǩ??????r??????i???m??????0??????ޙ????????????????????? }???-???????????? ޮ???^???ˬz???
It happens when mail software (such as that which runs the mailing list) simply inserts its own signature in its own encoding without paying attention to the encoding the user has chosen. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-------- Original Message -------- From: Jan Engelhardt Sent: Tuesday, Oct 31, 2017 3:16 PM SAE To: Marco Calistri Cc: opensuse-factory Subject: [opensuse-factory] Character Encoding and strange fonts below my signature
On Tuesday 2017-10-31 15:09, Marco Calistri wrote:
Due some unwanted behavior I had by using my yahoo.com and gmail.com accounts on this mailing-list I switched to hotmail.com as you can observe by my email.
Well, I was noticing a strange behavior which I don't yet discovered if it is due the Mail provider itself (outlook.com) or some setting on my Thunderbird mail client.
One fact I discovered just now is that on systems (personal computers) wherein I set the Character Encoding = UTF-8, some strange fonts are displayed on my e-mail messages sent on the list, when I receive back from opensuse-factory:
Example 1:
-- For every action, there is an equal and opposite criticism. ???{.n???+????????????????????????????????? }???-????????????{.n???+??????????????????Ǩ??????r??????i???m??????0??????ޙ????????????????????? }???-???????????? ޮ???^???ˬz???
It happens when mail software (such as that which runs the mailing list) simply inserts its own signature in its own encoding without paying attention to the encoding the user has chosen.
So this means that sometimes you have seen same strange fonts on other users email posting on this ML? That should be comfortable to know. Thanks and regards, -- Marco Calistri N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
On Tuesday 2017-10-31 18:24, Marco Calistri wrote:
Example 1:
-- For every action, there is an equal and opposite criticism. ???{.n???+????????????????????????????????? }???-????????????{.n???+??????????????????Ǩ??????r??????i???m??????0??????ޙ????????????????????? }???-???????????? ޮ???^???ˬz???
It happens when mail software (such as that which runs the mailing list) simply inserts its own signature in its own encoding without paying attention to the encoding the user has chosen.
So this means that sometimes you have seen same strange fonts on other users email posting on this ML?
I have seen it elsewhere, such as on the Linux kernel mailing lists (which is using Majordomo). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-------- Original Message -------- From: Jan Engelhardt Sent: Tuesday, Oct 31, 2017 3:26 PM SAE To: Marco Calistri Cc: opensuse-factory Subject: [opensuse-factory] Character Encoding and strange fonts below my signature
On Tuesday 2017-10-31 18:24, Marco Calistri wrote:
Example 1:
-- For every action, there is an equal and opposite criticism. ???{.n???+????????????????????????????????? }???-????????????{.n???+??????????????????Ǩ??????r??????i???m??????0??????ޙ????????????????????? }???-???????????? ޮ???^???ˬz???
It happens when mail software (such as that which runs the mailing list) simply inserts its own signature in its own encoding without paying attention to the encoding the user has chosen.
So this means that sometimes you have seen same strange fonts on other users email posting on this ML?
I have seen it elsewhere, such as on the Linux kernel mailing lists (which is using Majordomo).
Oh! Many thanks indeed, I was getting crazy trying to modify my settings to resolve this occurrence! Cheers, -- Marco Calistri
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Content-ID:
It happens when mail software (such as that which runs the mailing list) simply inserts its own signature in its own encoding without paying attention to the encoding the user has chosen.
So this means that sometimes you have seen same strange fonts on other users email posting on this ML?
I have seen it elsewhere, such as on the Linux kernel mailing lists (which is using Majordomo).
Oh! Many thanks indeed, I was getting crazy trying to modify my settings to resolve this occurrence!
It is indeed related to your settings, but I don't remember which. The question has been asked in the past, and IIRC it happens to people using MIME which the mail list software does not support. If not MIME then some other word. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAln5AJEACgkQja8UbcUWM1yNrgEAggs2Fj8591vw/SzMupLokc9Q GryODsbAIMda6cHqGCYBAIk4yUM3c+II9veZXscgKLTJT7ybKGfCyz7F3VvWMYRg =S4IG -----END PGP SIGNATURE-----
Il 31/10/2017 21:00, Carlos E. R. ha scritto:
Content-ID:
El 2017-10-31 a las 17:32 -0000, Marco Calistri escribió:
It happens when mail software (such as that which runs the mailing list) simply inserts its own signature in its own encoding without paying attention to the encoding the user has chosen.
So this means that sometimes you have seen same strange fonts on other users email posting on this ML?
I have seen it elsewhere, such as on the Linux kernel mailing lists (which is using Majordomo).
Oh! Many thanks indeed, I was getting crazy trying to modify my settings to resolve this occurrence!
It is indeed related to your settings, but I don't remember which. The question has been asked in the past, and IIRC it happens to people using MIME which the mail list software does not support.
If not MIME then some other word.
-- Cheers Carlos E. R.
(from 42.2 x86_64 "Malachite" (Minas Tirith)) Ok,
I see some user is "always free" of this issue, may be he is using the right settings for our mailing-list manager. Cheers, -- Marco Calistri Linux version : openSUSE Tumbleweed 20171028 Kernel: 4.13.10-1.gdb36cf8-default - Cinnamon 3.4.6
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
Il 31/10/2017 21:00, Carlos E. R. ha scritto:
Content-ID:
El 2017-10-31 a las 17:32 -0000, Marco Calistri escribió:
It happens when mail software (such as that which runs the mailing list) simply inserts its own signature in its own encoding without paying attention to the encoding the user has chosen.
So this means that sometimes you have seen same strange fonts on other users email posting on this ML?
I have seen it elsewhere, such as on the Linux kernel mailing lists (which is using Majordomo).
Oh! Many thanks indeed, I was getting crazy trying to modify my settings to resolve this occurrence!
It is indeed related to your settings, but I don't remember which. The question has been asked in the past, and IIRC it happens to people using MIME which the mail list software does not support.
If not MIME then some other word.
Ok,
I see some user is "always free" of this issue, may be he is using the right settings for our mailing-list manager.
It doesn't happen to me :-) You can search for a post 2016-09-12, "Garbage at the end of my emails" where we commented on this. It happens to people using "Base64". The hack for the moment (years) is not use Base64. The list software adds a footer with instructions to unsubscribe in plain text, and this breaks. I understand it happens on all lists. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAln5u0sACgkQtTMYHG2NR9WYRACgiwMKy+sQOD31C3IMLCUmHwSx XvIAnR6qiLsGReUnYXix2e7h/a5MdBm/ =eR4M -----END PGP SIGNATURE-----
Il 01/11/2017 10:17, Carlos E. R. ha scritto:
Content-ID:
On Wednesday, 2017-11-01 at 11:16 -0000, Marco Calistri wrote:
Il 31/10/2017 21:00, Carlos E. R. ha scritto:
Content-ID:
El 2017-10-31 a las 17:32 -0000, Marco Calistri escribió:
> It happens when mail software (such as that which runs the mailing > list) simply inserts its own signature in its own encoding without > paying attention to the encoding the user has chosen.
So this means that sometimes you have seen same strange fonts on other users email posting on this ML?
I have seen it elsewhere, such as on the Linux kernel mailing lists (which is using Majordomo).
Oh! Many thanks indeed, I was getting crazy trying to modify my settings to resolve this occurrence!
It is indeed related to your settings, but I don't remember which. The question has been asked in the past, and IIRC it happens to people using MIME which the mail list software does not support.
If not MIME then some other word.
Ok,
I see some user is "always free" of this issue, may be he is using the right settings for our mailing-list manager.
It doesn't happen to me :-)
Right, you are garbage-font free certified! ;-)
You can search for a post 2016-09-12, "Garbage at the end of my emails" where we commented on this.
It happens to people using "Base64". The hack for the moment (years) is not use Base64.
Dunno if Thunderbird, which I use as my default client has the option to disable base64. I will look for this feature on Google.
The list software adds a footer with instructions to unsubscribe in plain text, and this breaks.
I understand it happens on all lists.
May be the feature to filter out base64 should be on the list manager software.
-- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)
Regards, -- Marco Calistri
Il 01/11/2017 11:05, Marco Calistri ha scritto:
Il 01/11/2017 10:17, Carlos E. R. ha scritto:
Content-ID:
On Wednesday, 2017-11-01 at 11:16 -0000, Marco Calistri wrote:
Il 31/10/2017 21:00, Carlos E. R. ha scritto:
Content-ID:
El 2017-10-31 a las 17:32 -0000, Marco Calistri escribió:
>> It happens when mail software (such as that which runs the mailing >> list) simply inserts its own signature in its own encoding without >> paying attention to the encoding the user has chosen. > > So this means that sometimes you have seen same strange fonts on > other > users email posting on this ML?
I have seen it elsewhere, such as on the Linux kernel mailing lists (which is using Majordomo).
Oh! Many thanks indeed, I was getting crazy trying to modify my settings to resolve this occurrence!
It is indeed related to your settings, but I don't remember which. The question has been asked in the past, and IIRC it happens to people using MIME which the mail list software does not support.
If not MIME then some other word.
Ok,
I see some user is "always free" of this issue, may be he is using the right settings for our mailing-list manager.
It doesn't happen to me :-)
Right, you are garbage-font free certified! ;-)
You can search for a post 2016-09-12, "Garbage at the end of my emails" where we commented on this.
It happens to people using "Base64". The hack for the moment (years) is not use Base64.
Dunno if Thunderbird, which I use as my default client has the option to disable base64. I will look for this feature on Google.
The list software adds a footer with instructions to unsubscribe in plain text, and this breaks.
I understand it happens on all lists.
May be the feature to filter out base64 should be on the list manager software.
-- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)
Regards, -- Marco Calistri �{.n�+����������� }�-����{.n�+������Ǩ��r��i�m��0��ޙ������� }�-���� ޮ�^�ˬz�
Changed a setting in Thunderbird output mail: West (ISO-8859-1). Let's see... -- Marco Calistri
Il 01/11/2017 10:17, Carlos E. R. ha scritto:
On Wednesday, 2017-11-01 at 11:16 -0000, Marco Calistri wrote:
I see some user is "always free" of this issue, may be he is using the right settings for our mailing-list manager.
It doesn't happen to me :-)
You can search for a post 2016-09-12, "Garbage at the end of my emails" where we commented on this.
It happens to people using "Base64". The hack for the moment (years) is not use Base64.
The list software adds a footer with instructions to unsubscribe in plain text, and this breaks.
I understand it happens on all lists.
I've not found any specific settings in Thunderbird to disable Base64. But probably I discovered a "workaround" now by selecting the output text encoding different than UTF-8, which I suppose is the cause of this problem. Regards, -- Marco Calistri N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
* Marco Calistri
I've not found any specific settings in Thunderbird to disable Base64. But probably I discovered a "workaround" now by selecting the output text encoding different than UTF-8, which I suppose is the cause of this problem.
Regards,
-- Marco Calistri N?????r??y隊Z)z{.???r?+?맲??r??z?^?ˬz??N?(?֜??^? ޭ隊Z)z{.???r?+??0???????Ǩ
your work-a-round has not worked: Content-Type: text/plain; charset="utf-8" Content-ID: <9D3259968546F44CAB9E4381B6CC6224@eurprd09.prod.outlook.com> Content-Transfer-Encoding: base64 ps: I have an old hotmail account. If it is still active I will post to you from there. I believe m$ is most of your problem, but I *am* biased. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2017-11-01 19:57, Marco Calistri wrote:
Il 01/11/2017 10:17, Carlos E. R. ha scritto:
On Wednesday, 2017-11-01 at 11:16 -0000, Marco Calistri wrote:
I see some user is "always free" of this issue, may be he is using the right settings for our mailing-list manager.
It doesn't happen to me :-)
You can search for a post 2016-09-12, "Garbage at the end of my emails" where we commented on this.
It happens to people using "Base64". The hack for the moment (years) is not use Base64.
The list software adds a footer with instructions to unsubscribe in plain text, and this breaks.
I understand it happens on all lists.
I've not found any specific settings in Thunderbird to disable Base64. But probably I discovered a "workaround" now by selecting the output text encoding different than UTF-8, which I suppose is the cause of this problem.
Very unlikely. ASCII-centric texts are almost always(*) QP-encoded simply because that produces a smaller mail than base64 encoding would. Then again, anything can happen with Microsoft products (which seem to be involved in the transmission history of your mails)…
-- Marco Calistri N?????r??y隊Z)z{.???r????????r??z?^?ˬz????(?֜???? ޭ隊Z)z{.???r????0???????Ǩ?
(*) If more than 1/6 of the bytes in the body are non-ASCII, switching from QP to base64 is preferable. I doubt any mail client implements it.. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-------- Original Message -------- From: Jan Engelhardt Sent: Wednesday, Nov 1, 2017 5:15 PM SAE To: Marco Calistri Cc: opensuse-factory@opensuse.org Subject: [opensuse-factory] Character Encoding and strange fonts below my signature
On Wednesday 2017-11-01 19:57, Marco Calistri wrote:
Il 01/11/2017 10:17, Carlos E. R. ha scritto:
On Wednesday, 2017-11-01 at 11:16 -0000, Marco Calistri wrote:
I see some user is "always free" of this issue, may be he is using the right settings for our mailing-list manager.
It doesn't happen to me :-)
You can search for a post 2016-09-12, "Garbage at the end of my emails" where we commented on this.
It happens to people using "Base64". The hack for the moment (years) is not use Base64.
The list software adds a footer with instructions to unsubscribe in plain text, and this breaks.
I understand it happens on all lists.
I've not found any specific settings in Thunderbird to disable Base64. But probably I discovered a "workaround" now by selecting the output text encoding different than UTF-8, which I suppose is the cause of this problem.
Very unlikely. ASCII-centric texts are almost always(*) QP-encoded simply because that produces a smaller mail than base64 encoding would.
Then again, anything can happen with Microsoft products (which seem to be involved in the transmission history of your mails)…
No, currently I'm using Windows 10 and Mozilla Thunderbird over my old hotmail.com account.
-- Marco Calistri N?????r??y隊Z)z{.???r????????r??z?^?ˬz????(?֜???? ޭ隊Z)z{.???r????0???????Ǩ?
(*) If more than 1/6 of the bytes in the body are non-ASCII, switching from QP to base64 is preferable. I doubt any mail client implements it..
The solution with Thunderbird mail client _apparently_ is to use: Tools->Options->Display->Advanced->output text encoding other than UTF-8 which results in Thunderbird switching to encode in Base64. Now I set it as West (Windows-1252) Regards, -- Marco Calistri
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
On Wednesday 2017-11-01 19:57, Marco Calistri wrote:
Il 01/11/2017 10:17, Carlos E. R. ha scritto:
...
Then again, anything can happen with Microsoft products (which seem to be involved in the transmission history of your mails)…
No, currently I'm using Windows 10 and Mozilla Thunderbird over my old hotmail.com account.
Well, that's the cause >:-P And, you are using a MS-Exchange mail server. I would compare in Thunderbird, view code (ctrl-U) your own message in your output folder with the one you get back from the mail list. I have the guess that the base64 encoding is done outside of your machine.
(*) If more than 1/6 of the bytes in the body are non-ASCII, switching from QP to base64 is preferable. I doubt any mail client implements it..
The solution with Thunderbird mail client _apparently_ is to use: Tools->Options->Display->Advanced->output text encoding other than UTF-8 which results in Thunderbird switching to encode in Base64. Now I set it as West (Windows-1252)
As yu see below, no.
Regards, -- Marco Calistri N?????r??y隊Z)z{.???r????????r??z?^?ˬz????(?֜???? ޭ隊Z)z{.???r????0???????Ǩ?
- -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAln6O8AACgkQtTMYHG2NR9WDrQCfXTRBPNy52wKy5xN+ONoskulT jCYAnj7NvoMDGsWr8ZG5VJjr6QT+W966 =3Dgu -----END PGP SIGNATURE-----
Il 01/11/2017 19:25, Carlos E. R. ha scritto:
Content-ID:
On Wednesday, 2017-11-01 at 19:37 -0000, Marco Calistri wrote:
No, currently I'm using Windows 10 and Mozilla Thunderbird over my old hotmail.com account.
Well, that's the cause >:-P
And, you are using a MS-Exchange mail server.
I would compare in Thunderbird, view code (ctrl-U) your own message in your output folder with the one you get back from the mail list. I have the guess that the base64 encoding is done outside of your machine.
The solution with Thunderbird mail client _apparently_ is to use: Tools->Options->Display->Advanced->output text encoding other than UTF-8 which results in Thunderbird switching to encode in Base64. Now I set it as West (Windows-1252)
As yu see below, no.
Regards, -- Marco Calistri N?????r??y隊Z)z{.???r????????r??z?^?ˬz????(?֜???? ޭ隊 Z)z{.???r????0???????Ǩ?
-- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)
Yes it has not worked Carlos because I've missed one setting which now I think is right selected, but I would have the confirmation only after I send this email... Cheers, -- Marco Calistri Linux version : openSUSE Tumbleweed 20171028 Kernel: 4.13.10-1.gdb36cf8-default - Cinnamon 3.4.6
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
Il 01/11/2017 19:25, Carlos E. R. ha scritto:
Yes it has not worked Carlos because I've missed one setting which now I think is right selected, but I would have the confirmation only after I send this email...
Cheers,
-- Marco Calistri Linux version : openSUSE Tumbleweed 20171028 Kernel: 4.13.10-1.gdb36cf8-default - Cinnamon 3.4.6 N?????r??y隊Z)z{.???r????????r??z?^?ˬz????(?֜???? >ޭ隊Z)z{.???r????0???????Ǩ?
No, it did not work. Content-Type: text/plain; charset="utf-8" Content-ID: <22B8FBBEEEDA2C48B4EF1033C44D6D5C@eurprd09.prod.outlook.com> Content-Transfer-Encoding: base64 <=========== Precedence: bulk - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAln6dbEACgkQtTMYHG2NR9WqewCdFeBfi31h74xVR6nTxTqyPaSK YLwAn02J3MEJbswYg/xo3nshvJirNqq+ =ujeU -----END PGP SIGNATURE-----
Il 01/11/2017 23:32, Carlos E. R. ha scritto:
Content-ID:
On Thursday, 2017-11-02 at 01:26 -0000, Marco Calistri wrote:
Il 01/11/2017 19:25, Carlos E. R. ha scritto:
Yes it has not worked Carlos because I've missed one setting which now I think is right selected, but I would have the confirmation only after I send this email...
Cheers,
-- Marco Calistri Linux version : openSUSE Tumbleweed 20171028 Kernel: 4.13.10-1.gdb36cf8-default - Cinnamon 3.4.6 N?????r??y隊Z)z{.???r????????r??z?^?ˬz????(?֜???? >ޭ隊 Z)z{.???r????0???????Ǩ?
No, it did not work.
Content-Type: text/plain; charset="utf-8" Content-ID: <22B8FBBEEEDA2C48B4EF1033C44D6D5C@eurprd09.prod.outlook.com> Content-Transfer-Encoding: base64 <=========== Precedence: bulk
-- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)
:-( Yes I see that it has not worked! Strange, because on Windows, after I set the options in same manner as I set here on Linux, it has worked. Well, now I'm tired, better go to sleep... Best regards, -- Marco Calistri Linux version : openSUSE Tumbleweed 20171028 Kernel: 4.13.10-1.gdb36cf8-default - Cinnamon 3.4.6
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2017-11-02 at 01:37 -0000, Marco Calistri wrote:
Il 01/11/2017 23:32, Carlos E. R. ha scritto:
No, it did not work.
Content-Type: text/plain; charset="utf-8" Content-ID: <22B8FBBEEEDA2C48B4EF1033C44D6D5C@eurprd09.prod.outlook.com> Content-Transfer-Encoding: base64 <=========== Precedence: bulk
:-( Yes I see that it has not worked! Strange, because on Windows, after I set the options in same manner as I set here on Linux, it has worked.
Well, now I'm tired, better go to sleep...
Best regards,
Here it worked. Notice that here you attach a PGP signature, which probably disables base64 (guess). Also see my previous response. Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="BDjBxqAEf5bwPa3HGsxiRg3sXxi5U5wiv" Precedence: bulk I saw another link, that you probably also read: https://superuser.com/questions/766269/how-to-change-content-transfer-encodi... I think that link is wrong, it is not true that email is limited to 7 bits. My emails have: Content-Type: text/plain; charset="utf-8" and they clearly work. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAln6eV8ACgkQtTMYHG2NR9XKGgCdHaD5QsUiYh6KAB9hL9B2r6BS DhEAn3rNouMMAAzS886djSPJjsIopDyB =Yn8C -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 01/11/2017 23:48, Carlos E. R. ha scritto:
On Thursday, 2017-11-02 at 01:37 -0000, Marco Calistri wrote:
Il 01/11/2017 23:32, Carlos E. R. ha scritto:
No, it did not work.
Content-Type: text/plain; charset="utf-8" Content-ID: <22B8FBBEEEDA2C48B4EF1033C44D6D5C@eurprd09.prod.outlook.com> Content-Transfer-Encoding: base64 <=========== Precedence: bulk
:-( Yes I see that it has not worked! Strange, because on Windows, after I set the options in same manner as I set here on Linux, it has worked.
Well, now I'm tired, better go to sleep...
Best regards,
Here it worked. Notice that here you attach a PGP signature, which probably disables base64 (guess). Also see my previous response.
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="BDjBxqAEf5bwPa3HGsxiRg3sXxi5U5wiv" Precedence: bulk
You're right but I also changed the contact preference for the address "opensuse-factory@opensuse.org" and I explicitly select it as an "only text e-mail recipient". Dunno if it made the things go.
I saw another link, that you probably also read:
https://superuser.com/questions/766269/how-to-change-content-transfer-encodi...
I think that link is wrong, it is not true that email is limited to 7 bits. My emails have:
Content-Type: text/plain; charset="utf-8"
and they clearly work.
Your emails are garbages-free!
-- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)
Closing down... -- Marco Calistri Linux version : openSUSE Tumbleweed 20171028 Kernel: 4.13.10-1.gdb36cf8-default - Cinnamon 3.4.6 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/11/2017 04:05, Marco Calistri wrote:
Il 01/11/2017 23:48, Carlos E. R. ha scritto:
On Thursday, 2017-11-02 at 01:37 -0000, Marco Calistri wrote:
Il 01/11/2017 23:32, Carlos E. R. ha scritto:
No, it did not work.
Content-Type: text/plain; charset="utf-8" Content-ID: <22B8FBBEEEDA2C48B4EF1033C44D6D5C@eurprd09.prod.outlook.com> Content-Transfer-Encoding: base64 <=========== Precedence: bulk
:-( Yes I see that it has not worked! Strange, because on Windows, after I set the options in same manner as I set here on Linux, it has worked.
Well, now I'm tired, better go to sleep...
Best regards,
Here it worked. Notice that here you attach a PGP signature, which probably disables base64 (guess). Also see my previous response.
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="BDjBxqAEf5bwPa3HGsxiRg3sXxi5U5wiv" Precedence: bulk
You're right but I also changed the contact preference for the address "opensuse-factory@opensuse.org" and I explicitly select it as an "only text e-mail recipient". Dunno if it made the things go.
I saw another link, that you probably also read:
https://superuser.com/questions/766269/how-to-change-content-transfer-encodi...
I think that link is wrong, it is not true that email is limited to 7 bits. My emails have:
Content-Type: text/plain; charset="utf-8"
and they clearly work.
Your emails are garbages-free!
-- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)
Closing down...
This message has the unsubscribe message at the bottom whereas all of your other ones had a string of garbage at the bottom. I'm used to it and just ignore it. Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/11/17 09:37 PM, Marco Calistri wrote:
Il 01/11/2017 23:32, Carlos E. R. ha scritto:
Content-ID:
On Thursday, 2017-11-02 at 01:26 -0000, Marco Calistri wrote:
Il 01/11/2017 19:25, Carlos E. R. ha scritto:
Yes it has not worked Carlos because I've missed one setting which now I think is right selected, but I would have the confirmation only after I send this email...
Cheers,
-- Marco Calistri Linux version : openSUSE Tumbleweed 20171028 Kernel: 4.13.10-1.gdb36cf8-default - Cinnamon 3.4.6 N?????r??y隊Z)z{.???r????????r??z?^?ˬz????(?֜???? >ޭ隊 Z)z{.???r????0???????Ǩ?
No, it did not work.
Content-Type: text/plain; charset="utf-8" Content-ID: <22B8FBBEEEDA2C48B4EF1033C44D6D5C@eurprd09.prod.outlook.com> Content-Transfer-Encoding: base64 <=========== Precedence: bulk
-- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)
:-( Yes I see that it has not worked! Strange, because on Windows, after I set the options in same manner as I set here on Linux, it has worked.
Well, now I'm tired, better go to sleep...
Best regards,
Curious
--39i3LBLqKXqNdS6rPlO5gigNUp3V4BXRL Content-Type: text/plain; charset=UTF-8 Content-Language: pt-BR Content-Transfer-Encoding: quoted-printable
I note that when it works for you (and for a couple of other people too) there isn't the list-inserted gumph at the bottom about how to unsubscribe. -- Perilous to all of us are the devices of an art deeper than we ourselves possess. -- Gandalf the Grey [J.R.R. Tolkien, "Lord of the Rings"] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2017-11-02 at 02:32 +0100, Carlos E. R. wrote:
On Thursday, 2017-11-02 at 01:26 -0000, Marco Calistri wrote:
Il 01/11/2017 19:25, Carlos E. R. ha scritto:
Content-Type: text/plain; charset="utf-8" Content-ID: <22B8FBBEEEDA2C48B4EF1033C44D6D5C@eurprd09.prod.outlook.com> Content-Transfer-Encoding: base64 <=========== Precedence: bulk
Try "setting "mail.strictly_mime" to true" https://support.mozilla.org/en-US/questions/1139872 - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAln6d4cACgkQtTMYHG2NR9VEDACcDD5NkECPSZBAZZ5N45XWQWMc Em4An0plc964WoILxuvxQ/NjVzbAJaep =axFi -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 01/11/2017 23:40, Carlos E. R. ha scritto:
On Thursday, 2017-11-02 at 02:32 +0100, Carlos E. R. wrote:
On Thursday, 2017-11-02 at 01:26 -0000, Marco Calistri wrote:
Il 01/11/2017 19:25, Carlos E. R. ha scritto:
Content-Type: text/plain; charset="utf-8" Content-ID: <22B8FBBEEEDA2C48B4EF1033C44D6D5C@eurprd09.prod.outlook.com> Content-Transfer-Encoding: base64 <=========== Precedence: bulk
Try "setting "mail.strictly_mime" to true"
https://support.mozilla.org/en-US/questions/1139872
-- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar>
That parameter is already set as true, I Googled enough today ;-) But I see my previous email has went well...No garbages! Very strange! Good night, -- Marco Calistri Linux version : openSUSE Tumbleweed 20171028 Kernel: 4.13.10-1.gdb36cf8-default - Cinnamon 3.4.6 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/11/2017 03:43, Marco Calistri wrote:
Il 01/11/2017 23:40, Carlos E. R. ha scritto:
On Thursday, 2017-11-02 at 02:32 +0100, Carlos E. R. wrote:
On Thursday, 2017-11-02 at 01:26 -0000, Marco Calistri wrote:
Il 01/11/2017 19:25, Carlos E. R. ha scritto:
Content-Type: text/plain; charset="utf-8" Content-ID: <22B8FBBEEEDA2C48B4EF1033C44D6D5C@eurprd09.prod.outlook.com> Content-Transfer-Encoding: base64 <=========== Precedence: bulk
Try "setting "mail.strictly_mime" to true"
https://support.mozilla.org/en-US/questions/1139872
-- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar>
That parameter is already set as true, I Googled enough today ;-) But I see my previous email has went well...No garbages!
Very strange!
Good night,
This one is also ok, you must have done something right. Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 2017-11-02 06:09, Dave Plater wrote:
Try "setting "mail.strictly_mime" to true"
That parameter is already set as true, I Googled enough today ;-) But I see my previous email has went well...No garbages!
This one is also ok, you must have done something right.
Well, can't really say that "sucking up to the software" can be considered right in a world where the power is supposed to lie within users ;-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 02/11/2017 03:09, Dave Plater ha scritto:
On 02/11/2017 03:43, Marco Calistri wrote:
Il 01/11/2017 23:40, Carlos E. R. ha scritto:
On Thursday, 2017-11-02 at 02:32 +0100, Carlos E. R. wrote:
On Thursday, 2017-11-02 at 01:26 -0000, Marco Calistri wrote:
Il 01/11/2017 19:25, Carlos E. R. ha scritto:
Content-Type: text/plain; charset="utf-8" Content-ID: <22B8FBBEEEDA2C48B4EF1033C44D6D5C@eurprd09.prod.outlook.com> Content-Transfer-Encoding: base64 <=========== Precedence: bulk
Try "setting "mail.strictly_mime" to true"
https://support.mozilla.org/en-US/questions/1139872
-- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar>
That parameter is already set as true, I Googled enough today ;-) But I see my previous email has went well...No garbages!
Very strange!
Good night,
This one is also ok, you must have done something right. Dave P
:-) Yes, after several attempts I've finally sorted it out! Thanks for your feedback! Best regards, -- Marco Calistri Linux version : openSUSE Tumbleweed 20171031 Kernel: 4.13.10-2.g951f578-default - Cinnamon 3.6.0 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Oct 31, Marco Calistri wrote:
Well, I was noticing a strange behavior which I don't yet discovered if it is due the Mail provider itself (outlook.com) or some setting on my Thunderbird mail client.
This is a bug in the opensuse.org listsoftware. If a message body is transfered with "Content-Transfer-Encoding: base64" it expecte by a MUA to have the entire body in "base64". The sending MUA, and perhaps some MTAs in between, handle this correctly. But the broken list software just appends a useless footer in plain ASCII, which is not valid "base64". As a result a MUA shows binary garbage when converting ordinary ASCII footer from "base64" to <whatever>. This bug can not be fixed in the list software. You must live with it for another decade. Olaf
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2017-11-02 at 10:59 +0100, Olaf Hering wrote:
On Tue, Oct 31, Marco Calistri wrote:
Well, I was noticing a strange behavior which I don't yet discovered if it is due the Mail provider itself (outlook.com) or some setting on my Thunderbird mail client.
This is a bug in the opensuse.org listsoftware.
To be exact, in mlmmj
This bug can not be fixed in the list software. You must live with it for another decade.
Well, I think it is in the works to change to another list software. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAln67m4ACgkQtTMYHG2NR9UPMACeMMi4tH7s0tHQAXCTrFiqf5EY fd4An2eMlxXPLcen2IIYM2ayW9fU+guY =npuX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-------- Original Message -------- From: Olaf Hering Sent: Thursday, Nov 2, 2017 7:59 AM GMT-0200 To: Marco Calistri Cc: opensuse-factory Subject: [opensuse-factory] Character Encoding and strange fonts below my signature
On Tue, Oct 31, Marco Calistri wrote:
Well, I was noticing a strange behavior which I don't yet discovered if it is due the Mail provider itself (outlook.com) or some setting on my Thunderbird mail client.
This is a bug in the opensuse.org listsoftware.
If a message body is transfered with "Content-Transfer-Encoding: base64" it expecte by a MUA to have the entire body in "base64". The sending MUA, and perhaps some MTAs in between, handle this correctly. But the broken list software just appends a useless footer in plain ASCII, which is not valid "base64". As a result a MUA shows binary garbage when converting ordinary ASCII footer from "base64" to <whatever>.
This bug can not be fixed in the list software. You must live with it for another decade.
Olaf
Hi Olaf, after several attempts, I have been able to lead with the broken mmlmj issue! Best regards, -- Marco Calistri Linux version : openSUSE Tumbleweed 20171031 Kernel: 4.13.10-2.g951f578-default - Cinnamon 3.6.0
participants (7)
-
Anton Aylward -
Carlos E. R. -
Dave Plater -
Jan Engelhardt -
Marco Calistri -
Olaf Hering -
Patrick Shanahan