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

Bug#190033: marked as done (kmail: message/rfc822 attachment MUST NOT use a Content-Transfer-Encoding)

Your message dated Fri, 8 Jun 2007 08:48:17 -0400
with message-id <9f694b820706080548v47674332oae2a0971890bf3ad@mail.gmail.com>
and subject line closing old bug in Debian BTS #190033 "kmail: message/rfc822 attachment MUST NOT use a Content-Transfer-Encoding"
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.1.1-1
Severity: important

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

[important because it makes mail bounce with some mail systems, including 
 ABUSE@NIC.IT]

when I forward a mail as attachment, kmail adds a
Content-Transfer-Encoding header to the MIME header for the
message/rfc822 message part, which, as far as I understand the rfc, MUST
NOT be done. It is supposed that the attached message has to be properly
encoded.

I can see that some might consider this a stupid requirement, but kmail
didn't write the standards...

cheers
- -- vbi


- -- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux altfrangg 2.4.19 #1 SMP Wed Sep 25 19:59:59 CEST 2002 i686
Locale: LANG=C, LC_CTYPE=en_US.UTF-8

Versions of packages kmail depends on:
ii  kdebase-kio-plugins        4:3.1.1-1     KDE I/O Slaves
ii  kdelibs4                   4:3.1.1-1     KDE core libraries
ii  libart-2.0-2               2.3.11-3      Library of functions for 2D graphi
ii  libc6                      2.3.1-16      GNU C Library: Shared libraries an
ii  libfam0c102                2.6.9-4       client library to control the FAM 
ii  libgcc1                    1:3.2.3-0pre6 GCC support library
ii  libjpeg62                  6b-7          The Independent JPEG Group's JPEG 
ii  libkdenetwork2             4:3.1.1-1     KDE Network (common libraries)
ii  libmimelib1                4:3.1.1-1     KDE network mime library
ii  libpng12-0                 1.2.5-10      PNG library - runtime
ii  libqt3c102-mt              3:3.1.1-7     Qt GUI Library (Threaded runtime v
ii  libstdc++5                 1:3.2.3-0pre6 The GNU Standard C++ Library v3
ii  xlibs                      4.2.1-3       X Window System client libraries
ii  zlib1g                     1:1.1.4-11    compression library - runtime

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: get my key from http://fortytwo.ch/gpg/92082481

iKcEARECAGcFAj6kDU1gGmh0dHA6Ly9mb3J0eXR3by5jaC9sZWdhbC9ncGcvZW1h
aWwuMjAwMjA4MjI/dmVyc2lvbj0xLjMmbWQ1c3VtPTE0Y2E2MTZmMTQ2ODJhODJj
YjljYzI1YzliMzRhMTBkAAoJEIukMYvlp/fWRwIAoNhHPTuaKM0A9EgtQRkIuSlA
bpwaAJ457LGmznbxrAp3y7tgNL8JWYw3nQ==
=yp/c
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Hi,
This bug has been fixed in 3.5 by upstream.
Closing this report.
Thanks,
Olivier Vitrat

--- End Message ---
Reply to: