On 06/07/2012 02:02 PM, Rob Steinmetz wrote:
>
>
> Paul B. Gallagher wrote:
>> Rob Steinmetz wrote:
>>
>>> I have one user who is getting occasional emails from different people.
>>> They look like the text below (if it comes through) Anyone have any
>>> ideas what is happening?
>>>
>>> ��z{i���{�jy,~����-�+&���'��ƹ��iX�x�'^��EI��>�)z�r
>>> ����Ot�(�rW�����Z�ֆ}7�����v�N�
>>> ��z{Z��r�+ z֢��}�����t�ꮊ����+�W�jg�z�+��b�}}KM86k'������
>>> i���ܢ�Kh��(��4�M
>>> [����܈ [�\� �ܚ� \�[ܛ�[��HCB�B�[�[��Y\��CB��X�H �\�Y[�B����][ ��\� H��B��Z]H
>>>
>>>
>>
>>
>> Encoding not correctly interpreted by receiving program (name and
>> version?).
>
> The Receiving Program is Seamonkey 2.9.1
>>
>> In the full headers, what does the recipient see for these lines?
>>
>> MIME-Version:
>> Content-Type:
>> Content-Transfer-Encoding:
>>
>> For example, your posting here has:
>>
>> MIME-Version: 1.0
>> Content-Type: text/plain; charset=UTF-8; format=flowed
>> Content-Transfer-Encoding: 8bit
>>
>
> This is the original header information.
>
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: base64
> MIME-Version: 1.0
>
> The odd thing is it's only a few emails from a few people that we
> communicate with regularly.
The base64 decoding is not working properly, or the encoding is not
correct. For example, if you cut & paste content of the message in a
base64 decoder, you should be able to see the message in standard plain
text format. To see if the problem is decoding:
http://www.base64decode.org/
Now past the following into the top box:
U29sdmVkLCB0aGFua3MgdG8gTm9PcCBoaW50LCBmaWd1cmVkIG91dCB0aGF0ICouYWZtIGFyZSBt
aXNzaW5nIGF0IEdlbnRvby4KRm9udCBpcyB3b3JraW5nLCBhbHRob3VnaCBubyBwcmV2aWV3IGlu
IGRyb3AgZG93biBhcyBpbiB0aGUgZm9udCBJCmNvbnZlcnRlZCB0byBUVEYuCkJ1dCB0aGlzIGlz
and press the green 'DECODE' button.
What you should see is:
===
Solved, thanks to NoOp hint, figured out that *.afm are missing at Gentoo.
Font is working, although no preview in drop down as in the font I
converted to TTF.
But this is
===
That is from an actual
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
message. When I read it in SeaMonkey, I see the plain text. However, if
I view the source (Ctrl-u), what is see is the base64 gibberish above.
So, SeaMonkey is decoding the base64 properly so I can view/understand
the contents.
Now also do the same with a snippet from the raw message (ctrl-u or
View|Message Source).
These may be of some help/use:
<http://support.microsoft.com/kb/323489>
<https://en.wikipedia.org/wiki/Base64>
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
