Hello Erik,
Am 04.02.22 um 08:48 schrieb Erik Thiele:
...
As you see something is wrong when receiving attachments that contain a
slash (/) in their name.
When you investigate thunderbird with strace like this:
strace -ffff thunderbird working.eml 2>strace_working.txt
then click on the attachment and quit thunderbird
then do
strace -ffff thunderbird not_working.eml 2>strace_not_working.txt
then click on the attachment and quit thunderbird
then do:
grep pdf strace_working.txt |grep open
you will see:
[pid 17250] openat(AT_FDCWD, "/tmp/doc.pdf", O_WRONLY|O_CREAT...
compare this to:
grep pdf strace_not_working.txt |grep open
you will see no try of even saving the attachment.
The way I created the not-working email with a text editor may seem
the source of the problem, but it isn't. I regularly get emails with
slashes in attachment names. I simply did not find a way to create such
an email with commandline tools. All seem to dislike slashes in
attachment names. But since I am regularly receiving this kind of
emails in real life, there must be some (non-unix?) mail program
creating such (bad) attachments.
in no way a backslash character is a valid character for filenames no
matter which OS you are. And normally any application wouldn't need to
take care about such invalid strings of filenames. So I would not
consider this a "real" issue within Thunderbird.
Even on Windows a backslash isn't a valid character for filenames. Some
guy has collected some information about invalid characters on Windows
systems within this GitHub gist.
https://gist.github.com/doctaphred/d01d05291546186941e1b7ddc02034d3
The next Thunderbird version did some more improvements on work around
such attachments which have invalid filenames. Might be your problem
with broken attachments filenames is then mostly gone away.
https://bugzilla.mozilla.org/show_bug.cgi?id=1747977
If not you should move over to the Mozilla Bugtracker and open a report
there. Within the Debian packaging there is quite nothing we can do
about that, nor should we because this needs to get fixed upstream first.
--
Regards
Carsten
