Your message dated Sat, 12 Feb 2005 19:02:19 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#285914: fixed in metamail 2.7-47
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 16 Dec 2004 12:14:16 +0000
>From [EMAIL PROTECTED] Thu Dec 16 04:14:16 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mail.sklad.bacon.ru (elbereth.sklad.bacon.ru) [81.1.198.156]
(root)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CeuWN-0001H6-00; Thu, 16 Dec 2004 04:14:15 -0800
Received: from kogan.sklad.bacon.ru ([EMAIL PROTECTED])
by elbereth.sklad.bacon.ru (8.12.3/8.12.3/Debian-6.6) with ESMTP id
iBGCDU1F029924;
Thu, 16 Dec 2004 18:13:31 +0600
Received: from kogan.sklad.bacon.ru ([EMAIL PROTECTED] [127.0.0.1])
by kogan.sklad.bacon.ru (8.12.9/8.12.9/Debian-3) with ESMTP id
iBGCDUS0032106;
Thu, 16 Dec 2004 18:13:30 +0600
Received: (from [EMAIL PROTECTED])
by kogan.sklad.bacon.ru (8.12.9/8.12.9/Debian-3) id iBGCDTEb032105;
Thu, 16 Dec 2004 18:13:29 +0600
Message-Id: <[EMAIL PROTECTED]>
Content-Type: multipart/mixed; boundary="===============70493051481385138=="
MIME-Version: 1.0
From: Sergey Kogan <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: metamail: 8-bit encoding is supported by metamail but not by metasend
script
X-Mailer: reportbug 2.10.1
Date: Thu, 16 Dec 2004 18:13:29 +0600
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
This is a multi-part MIME message sent by reportbug.
--===============70493051481385138==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: metamail
Version: 2.7-46
Severity: normal
Tags: patch
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux kogan 2.4.25 #18 Mon Jun 28 16:55:20 OMSST 2004 i686
Locale: LANG=ru_RU.koi8r, LC_CTYPE=ru_RU.koi8r
Versions of packages metamail depends on:
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libncurses5 5.4-3 Shared libraries for terminal hand
-- no debconf information
8-bit text/plain e-mail are common in ex-USSR countries. Metamail itself
works with 8-bit transfer-encoding just fine, but metasend script treats
-e "8bit" like -e "quoted-printable". Attached patch should fix this
problem.
--===============70493051481385138==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="metasend.diff"
*** metasend.old Thu Dec 16 17:55:09 2004
--- metasend.new Thu Dec 16 17:58:57 2004
***************
*** 135,144 ****
--- 135,145 ----
encode=$1
case "$encode" in
"base64") encodingprog="mimencode -b";;
"x-uue") encodingprog="uuencode \$datafile";;
"7bit") encodingprog=cat;;
+ "8bit") encodingprog=cat;;
*) encodingprog="mimencode -q"
encode=quoted-printable ;;
esac
shift ;;
***************
*** 322,331 ****
--- 323,333 ----
echo "Do you want to encode this data for sending
through the mail?"
echo " 1 -- No, it is already in 7 bit ASCII"
echo " 2 -- Yes, encode in base64 (most efficient)"
echo " 3 -- Yes, encode in quoted-printable (less
efficient, more readable)"
echo " 4 -- Yes, encode it using uuencode (not
standard, being phased out)"
+ echo " 5 -- No, it is 8 bit extended ASCII"
read encode
looping=0
case "$encode" in
1) encodingprog=cat
encode=7bit ;;
***************
*** 333,342 ****
--- 335,346 ----
encode=base64 ;;
3) encodingprog="mimencode -q"
encode=quoted-printable ;;
4) encodingprog="uuencode $datafile"
encode=x-uue ;;
+ 5) encodingprog=cat
+ encode=8bit ;;
*) echo Unrecognized answer, please try again.
looping=1 ;;
esac
done
fi
***************
*** 423,432 ****
--- 427,437 ----
else
case "$encode" in
base64) encodingprog="mimencode -b" ;;
x-uue) encodingprog="uuencode $datafile" ;;
7bit) encodingprog=cat ;;
+ 8bit) encodingprog=cat ;;
*) encodingprog="mimencode -q"
encode=quoted-printable ;;
esac
fi
fi
--===============70493051481385138==--
---------------------------------------
Received: (at 285914-close) by bugs.debian.org; 13 Feb 2005 00:10:15 +0000
>From [EMAIL PROTECTED] Sat Feb 12 16:10:15 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D07L5-0003Je-00; Sat, 12 Feb 2005 16:10:15 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1D07DP-0003kc-00; Sat, 12 Feb 2005 19:02:19 -0500
From: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#285914: fixed in metamail 2.7-47
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sat, 12 Feb 2005 19:02:19 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 4
Source: metamail
Source-Version: 2.7-47
We believe that the bug you reported is fixed in the latest version of
metamail, which is due to be installed in the Debian FTP archive:
metamail_2.7-47.diff.gz
to pool/main/m/metamail/metamail_2.7-47.diff.gz
metamail_2.7-47.dsc
to pool/main/m/metamail/metamail_2.7-47.dsc
metamail_2.7-47_i386.deb
to pool/main/m/metamail/metamail_2.7-47_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Anibal Monsalve Salazar <[EMAIL PROTECTED]> (supplier of updated metamail
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sun, 13 Feb 2005 10:43:55 +1100
Source: metamail
Binary: metamail
Architecture: source i386
Version: 2.7-47
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <[EMAIL PROTECTED]>
Changed-By: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Description:
metamail - implementation of MIME
Closes: 184410 245647 249823 285914
Changes:
metamail (2.7-47) unstable; urgency=low
.
* QA Group upload by Anibal Monsalve Salazar.
* Fixed "Add/Improve SEE ALSO section for splitmail/mimeit" (Closes:
#245647). Patch by Helge Kreutzmann <[EMAIL PROTECTED]>.
* Fixed "8-bit encoding is supported by metamail but not by metasend script"
(Closes: #285914). Patch by Sergey Kogan <[EMAIL PROTECTED]>.
* Fixed "additional option when handling unrecognized content types"
(Closes: #249823). Patch by Daniel Kraft <[EMAIL PROTECTED]>.
* Fixed "debug message 'pre access' left in released version
(Closes: #184410). Patch by <[EMAIL PROTECTED]>.
Files:
05cac31b16008b4a457c867339a35b5e 582 mail optional metamail_2.7-47.dsc
57e512353a8e01f202506da2e7c942c7 340278 mail optional metamail_2.7-47.diff.gz
d6c1df15429cc7ea59b37e6dfdf46e15 148474 mail optional metamail_2.7-47_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFCDpbWgY5NIXPNpFURAnQNAJ9XBYYRDoBY7HO8ho+2uDuSaGPrvQCeLfqR
0X+6vyxI21ioRezjj1NjDiw=
=wZGy
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
