Am 2001-06-13 um 10:10 h BST hat Vadim Snurnikov geschrieben:
> I used an internet based mailing program: http://freemail.web.de/ --
> and downloaded the e-mail from there.

As I said before: mail-HTTP interfaces tend to corrupt messages
by not properly decoding them.

> I am sending you a relevant part of the header and a line with the
> Russian text.
...
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
> boundary="----=_NextPart_000_000C_01C0F20D.6A1A9EC0"

In case of "Content-Type: multipart", you must interpret the
additional MIME headers next to the several part boundaries,
as every part may have a different content-type, charset,
and content-transfer-encoding. You have not sent these.

Still, from your text samples, the particular error committed by your
Freenet provider can easily be guessed:
- It has undone the original content-transfer-encoding (probaly
  quoted-printable), but it has ignored the charset (apparently UTF-8),
  effectively interpreting the UTF-8 bytewise as ISO 8859-1 bytes. This
  has corrupted your message.
- As ISO 8859-1 does not use the codepoints 80 through 9F, your
  provider has not undone the content-transfer-encoding for those;
  rather it has sent them as-is, viz. in quoted-printable encoding.

Hence, in your example,
> Ð=9FÑ=80Ð=B8Ð=B2Ð=B5Ñ=82, Ð=92Ð=B0Ð=B4Ð=B8Ð=BC!
you have to
1. Undo the remaining quoted-printable encodings, such as "=9F".
2. Interpret the resulting byte sequence as UTF-8.

This will yield the sentence (in cyrillic; I transliterated it,
so it won't be corrupted, again):
  Privet, Vadim! (in English: "Greetings, Vadim!")

I have attached a table you can use to decipher the erroneous
Freenet encoding. Enjoy!

Best wishes (or should I say: "Privet"?),
  Otto Stolz