On 21Apr2019 23:18, Paul Gilmartin <paulgboul...@aim.com> wrote:
On 2019-04-21, at 19:53:04, Cameron Simpson wrote:
...
and the content is definitely not Cyrillic:
0 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
0 10 20 30 40 50 60 70 80 90 a0 b0 c0 d0 e0 f0
0 0 & - � � � � � { } \ 0
1 1 � � / � a j ~ � A J 1
2 2 � � � � b k s � B K S 2
3 3 � � � � c l t � C L T 3
How are those listings obtained? Might the thing presenting those listings be
interpreting the iso8859-5 data as the local character encoding and thus
misrendering?
They're the Unicode "Replacement Character":
https://www.fileformat.info/info/unicode/char/fffd/index.htm
HTML Entity (hex) �
UTF-8 (hex) 0xEF 0xBF 0xBD (efbfbd)
That wasn't what I was getting at :-(
Is the listing above the content of the attachment? Or the result of
some dump tool?
Anything displayed on the terminal has been through various translations
(including the terminal itself), and I was wondering if you were looking
at your two outputs via different mechanisms.
But your other post suggests you've narrowed the issue to the AOL SMTP
service, which surprises me - it shouldn't be mucking with the message
internals at all. Of course, I'm using the word "should" here :-)
Can you deliver the same message attachments through 2 SMTP services
(AOL and another) and then diff what you receive? Or if AOL is your
email service, send the same message to 2 addresses - one AOL and one
not - and diff the two messages on receipt? I mean an actual command line
diff of the raw messages. It should isolate the nature of the message
mangling if it is occuring.
Cheers,
Cameron Simpson <c...@cskk.id.au>
