Your message dated Tue, 17 Aug 2021 04:24:08 +0000
with message-id <[email protected]>
and subject line Bug#985464: fixed in libpst 0.6.76-1
has caused the Debian Bug report #985464,
regarding Libpst converts filename to rfc2231 format in outputted .msg files
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
985464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985464
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: readpst, libpst4
Version: 0.6.75
Tags: patch
Source: libpst
When extracting an email with attachments from a pst to .eml and .msg files,
the PR_ATTACH_LONG_FILENAME property for the attachments in the .msg file is
encoded as a UTF-8 string in rfc2231 format (i.e., it’s prefixed with
“utf-8’’”), which it shouldn’t be. The reason is that when saving the MIME
format .eml file, the pst_item_attach.filename2 field (the internal
representation of the PR_ATTACH_LONG_FILENAME) is converted to rfc2231 in place
before the attachment is encoded into a MIME part (the package seems to do a
lot of in-place string conversions, which is a bad idea unless you really know
you’re never going to need the original string again). When the .msg file is
subsequently created, it saves that previously rfc2231 encoded filename2 string
in the attachment’s PR_ATTACH_LONG_FILENAME property.
I suggest encoding the filename to rfc2231 into a separate temporary buffer,
rather than in place, so that the internal attachment structure maintains the
original, utf-8 encoded file name for use when saving the .msg file. Patch
attached.
This impacts both the readpst package, which is where the .eml and .msg files
are created, and libpst4, which contains the rfc2231 conversion function (not
sure why, since it only appears to be used from readpst).
This is probably really an upstream bug, but the libpst website, such as it is,
does not provide for bug reports, and it looks like the Debian maintainer has
made relatively recent commits to the upstream codebase, so I’m filing here.
pst-utils.patch
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: libpst
Source-Version: 0.6.76-1
Done: Paul Wise <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libpst, which is due to be installed in the Debian FTP archive.
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.
Paul Wise <[email protected]> (supplier of updated libpst 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: SHA512
Format: 1.8
Date: Tue, 17 Aug 2021 11:42:55 +0800
Source: libpst
Architecture: source
Version: 0.6.76-1
Distribution: unstable
Urgency: medium
Maintainer: Paul Wise <[email protected]>
Changed-By: Paul Wise <[email protected]>
Closes: 985464
Changes:
libpst (0.6.76-1) unstable; urgency=medium
.
* New upstream release.
- Fixes encoding attachment filenames (Closes: #985464)
* Add patches to fix header detection (See: #984581)
* Document why some upstream files are not installed
* Use watch file version 4
* Document compliance with Debian Policy 4.5.1
* Lengthen the libpst package description
* Switch to latest debhelper compat level of 13
Checksums-Sha1:
7bab5a9719d89ea973a87f9262fc3bf6916d9e12 1993 libpst_0.6.76-1.dsc
a540d778a808a450d909cded0e52f7f4175c690c 12886768 libpst_0.6.76.orig.tar.gz
4b8922de7ce4cb531e86e1e37bd2277b7d62e665 7400 libpst_0.6.76-1.debian.tar.xz
Checksums-Sha256:
f3a88bd3269f3c731d19f4d9eda3db55f8bc2a7c34d7b6f853bbcdba5c1b7ae6 1993
libpst_0.6.76-1.dsc
3d291beebbdb48d2b934608bc06195b641da63d2a8f5e0d386f2e9d6d05a0b42 12886768
libpst_0.6.76.orig.tar.gz
a40e02548c317366bc44df74a4f38fdfb83e352871a7c6f2275f94d77820cc33 7400
libpst_0.6.76-1.debian.tar.xz
Files:
0bf976867314728f211bd722bde8bd21 1993 utils optional libpst_0.6.76-1.dsc
e821b94e8d7790ee314059f751182ebf 12886768 utils optional
libpst_0.6.76.orig.tar.gz
f00a3a9a97b8e821b0edec07ea7d28f9 7400 utils optional
libpst_0.6.76-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAmEbM04ACgkQMRa6Xp/6
aaMKQg//axhMrg4sey2p7sfBZTJ/e6lgPD/UNBTgbOa8ncIRxmeioFbJLPVwmNOL
RtqqOiGET0MHZRUZ6vVCH9nhtlO9evaq2JegdMHcLCg/4nNXu/vPaJdqxwbVOBVb
dn4M8Stc7fbzzgKp7fifwLpPkX+CjVqrhkwkoF/nP2MkYZQwW6MZ3sb3Ucfg71rS
2tNg/AVli9zs5jxtGBEk4xIMDyWxXUP+nKipbsxD1hQEb02AJTsjKMxHJEbSvkBe
gHuoLBa4srrfYHF8XzGW6z/OFykU1Yxd5E951hOiI3omFloDJGK7RM1/WWWocupD
aQV14BnTUxz+l9LQFb6Eil7LCnLCDiOBdwP1kC4MtnlUp+mycsBqlO4QjONx/anz
Et1ujDPwFtrZRkG3pPgDm/lmnWgRKixIo6JI06FvApeNRqFVHy3WYqoL/35+LGfz
ZMJBvCtEocrccO1yfqcmNzjbD6ce/Ctsse/F7HsQSvccCdWQ4rvtWfFtzU5JWeQe
WXYUx6/Qn2lPsjfNiAuUuUpOmaYTuX43FGMieCRnlttIK13g4ATewiHGPaAkG3KY
XDFWIl7LdLPsdVwEVFKgH3UImL7kKLAICHeajSDfgc6P9wZnlrUFTO0cpvgLVHUo
yayRmoyNOKM3+Sm1UuBG7JA73otSn1yXFTm5Itzf/N8HpRXFpP4=
=R6oH
-----END PGP SIGNATURE-----
--- End Message ---
