Public bug reported:

I have a mail with one attachment, a text/plain description and a
text/html description. Both are encoded quoted printable.

munpack then decides to use tempdesc.txt as the filename for both. Then
when the second "create" fails, it deletes it, before the first instance
tries to rename the temporary file to the final name. So I end up with
zero copies of this part of the message !

Here are the headers of the offending sections:

--_=_swift_v4_1610361155_46f6fc1bde3c04b14e70acf1e9545649_=_
Content-Type: multipart/alternative;
 boundary="_=_swift_v4_1610361155_d8cc678205fe4ba833b0afd55797d773_=_"


--_=_swift_v4_1610361155_d8cc678205fe4ba833b0afd55797d773_=_
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

--_=_swift_v4_1610361155_d8cc678205fe4ba833b0afd55797d773_=_
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable


This is on 20.04 
mpack:
  Installed: 1.6-8.2
  Candidate: 1.6-8.2
  Version table:
 *** 1.6-8.2 500
        500 http://nl.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
        100 /var/lib/dpkg/status

* I expected it to provide me with both versions of the message text, getting 
either one would've been better than neither. 
* I would have wanted it to provide me with each part of the message in a 
separate file, allowing my script to further handle each part as appropriate. 

* The good news: In the case at hand I was going to ignore BOTH missing
message/parts, I'm only interested in the third... :-)

** Affects: mpack (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910991

Title:
  munpack has trouble with duplicate filenames.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mpack/+bug/1910991/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to