Author Topic: Problems decoding base64 and quoted-printable  (Read 3148 times)

Offline rjel

  • Newbie
  • *
  • Posts: 8
Problems decoding base64 and quoted-printable
« on: October 23, 2007, 01:35:49 AM »
Hello!

I have problems decoding base64 and quoted-printable.

A mail that looks like this.

From - Mon Oct 22 18:59:53 2007
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Subject: =?ISO-8859-1?B?5eT2?=
To: "Jonas Lindskog"
Date: Mon, 22 Oct 2007 15:52:02 +0200
Message-ID:
From: "Niklas Magnusson"
Content-Transfer-Encoding: base64
Content-Type: text/html;
   charset=ISO-8859-1
MIME-Version: 1.0
Importance: Normal
X-Priority: 3 (Normal)
MIME-Version: 1.0
X-MIMETrack: Serialize by Notes Server on TRINITY/SRV/MSC(Release 6.5.1|January 21, 2004) at
 2007-10-22 15:52:02,Serialize complete at 2007-10-22 15:52:02,Itemize by Notes Server on TRINITY/SRV/MSC(Release 6.5.1|January 21, 2004) at
 2007-10-22 15:52:02
X-Antivirus: avast! (VPS 000783-0, 2007-10-21), Inbound message
X-Antivirus-Status: Clean

PGZvbnQgc2l6ZT0iMiI+VGphITxicj48YnI+TuVnb24gaWTpIGFuZyDl5PY/PGJyPjxicj5KYWcg
aGl0dGFyIHR1c2FuIHbkbGRpZ3QgZOVsaWd0IHDlIHRyaWxsaWFuIHPlIGphZyB25WdhciBpbnRl
IHRyaXhhIG1lZCBjb25mLWZpbGVybmE8YnI+PC9mb250Pg==


Comes out like

PGZvbnQgc2l6ZT0iMiI+VGphITxicj48YnI+TuVnb24gaWTpIGFuZyDl5PY/PGJyPjxicj5KYWcg
aGl0dGFyIHR1c2FuIHbkbGRpZ3QgZOVsaWd0IHDlIHRyaWxsaWFuIHPlIGphZyB25WdhciBpbnRl
IHRyaXhhIG1lZCBjb25mLWZpbGVybmE8YnI+PC9mb250Pg==


and a mail that looks like

From - Tue Oct 23 07:33:15 2007
...
Date: Tue, 23 Oct 2007 07:33:09 +0200
From: Jonas Lindskog
To: Jonas Lindskog
Subject: Testar med
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-SoftScan-Status: clean
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0

text som inneh=E5ller =F6n och =E5n

comes out like

text som inneh=E5ller =F6n och =E5n


What have i missed?




Offline rjel

  • Newbie
  • *
  • Posts: 8
Re: Problems decoding base64 and quoted-printable
« Reply #1 on: October 23, 2007, 04:27:24 PM »
Problem disappeared when I installed RC2.