From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Weird behaviour saving attachments.
Date: Sat, 24 Nov 2007 09:34:28 -0800 [thread overview]
Message-ID: <1195925357-sup-8894@south> (raw)
In-Reply-To: <1195899951-sup-7842@ausone.local>
Excerpts from nicolas.pouillard's message of Sat Nov 24 02:25:57 -0800 2007:
> Sometimes when I save attachment the file name is not properly
> unquoted and then save a file with double quotes in the name (e.g.
> "foo.bar").
Can you track down the MIME header in the raw message that names the
attachment?
If you save the message to disk with 's' and search the file for
"filename", you should see it. (Probably a Content-Disposition header.)
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-11-24 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 10:25 Nicolas Pouillard
2007-11-24 17:34 ` William Morgan [this message]
2007-11-25 11:28 ` Nicolas Pouillard
2007-11-26 20:11 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1195925357-sup-8894@south \
--to=wmorgan-sup@masanjin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox