[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#247637: marked as done (kmail: unable to handle base64)

Your message dated Fri, 19 May 2006 11:12:21 +0200
with message-id <20060519091221.GA17457@mad.intersec.fr>
and subject line kmail: unable to handle base64
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kmail
Version: 4:3.2.2-2
Severity: normal

Apparently Kmail is not able to handle base64 encoded messages like
this:

--qC1cgMVBgZ
Content-Type: text/plain; charset=UTF-8
content-transfer-encoding: base64

VGVzdA==
--qC1cgMVBgZ--

I'm not sure this way of formatting mail is standard, however it
begins to be more and more usual with phone that send mails like
imode. Is there anything that could be done in order to make these
mails readable. Some mail software seems capable to handle that, like
IMP (web client).

Regards,


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.26
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro

Versions of packages kmail depends on:
ii  kdebase-kio-plugins         4:3.2.2-1    KDE I/O Slaves
ii  kdelibs4                    4:3.2.2-2    KDE core libraries
ii  ktnef                       4:3.2.2-2    KDE TNEF viewer
ii  libart-2.0-2                2.3.16-5     Library of functions for 2D graphi
ii  libc6                       2.3.2.ds1-12 GNU C Library: Shared libraries an
ii  libfam0c102                 2.7.0-5      client library to control the FAM 
ii  libgcc1                     1:3.3.3-6    GCC support library
ii  libice6                     4.3.0-7      Inter-Client Exchange library
ii  libjpeg62                   6b-9         The Independent JPEG Group's JPEG 
ii  libkcal2                    4:3.2.2-2    KDE calendaring library
ii  libkdenetwork2              4:3.2.2-2    KDE Network library
ii  libkdepim1                  4:3.2.2-2    KDE PIM library
ii  libksieve0                  4:3.2.2-2    KDE mail/news message filtering li
ii  libmimelib1                 4:3.2.2-2    KDE mime library
ii  libpcre3                    4.5-1.1      Perl 5 Compatible Regular Expressi
ii  libpng12-0                  1.2.5.0-6    PNG library - runtime
ii  libqt3c102-mt               3:3.2.3-2    Qt GUI Library (Threaded runtime v
ii  libsm6                      4.3.0-7      X Window System Session Management
ii  libstdc++5                  1:3.3.3-6    The GNU Standard C++ Library v3
ii  libx11-6                    4.3.0-7      X Window System protocol client li
ii  libxext6                    4.3.0-7      X Window System miscellaneous exte
ii  libxrender1                 0.8.3-7      X Rendering Extension client libra
ii  xlibs                       4.3.0-7      X Window System client libraries m
ii  zlib1g                      1:1.2.1-5    compression library - runtime

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 4:3.5.0

On Thu, May 06, 2004 at 08:15:04AM +0200, Mathieu Roy wrote:
> Package: kmail
> Version: 4:3.2.2-2
> Severity: normal
> 
> Apparently Kmail is not able to handle base64 encoded messages like
> this:
> 
> --qC1cgMVBgZ
> Content-Type: text/plain; charset=UTF-8
> content-transfer-encoding: base64
> 
> VGVzdA==
> --qC1cgMVBgZ--
> 
> I'm not sure this way of formatting mail is standard, however it
> begins to be more and more usual with phone that send mails like
> imode. Is there anything that could be done in order to make these
> mails readable. Some mail software seems capable to handle that, like
> IMP (web client).
> 
> Regards,

  this now works as expected.

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: