From: Lars Ingebrigtsen <larsi@gnus.org>
To: info-gnus-english@gnu.org
Subject: Re: Faking filenames for attachments
Date: Wed, 05 Mar 2014 14:29:45 +0100 [thread overview]
Message-ID: <87eh2gwz7a.fsf@building.gnus.org> (raw)
In-Reply-To: <mailman.14370.1391946212.10748.info-gnus-english@gnu.org>
Tim Landscheidt <tim@tim-landscheidt.de> writes:
> usually, if I attach a file /a/b/c.e to a message, it gets
> MIME headers:
>
> | Content-Type: mime/type
> | Content-Disposition: attachment; filename=c.e
>
> However, I want to pretend the filename is d.e.
Yeah, there is no easy way to do that.
I've now added `recipient-filename' to the MML tag so that you can
specify whatever file name (for the recipient) that you want. This is
in Ma Gnus only, so it won't be included in the next Emacs release
(since that's in a feature freeze now).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next parent reply other threads:[~2014-03-05 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.14370.1391946212.10748.info-gnus-english@gnu.org>
2014-03-05 13:29 ` Lars Ingebrigtsen [this message]
2014-02-09 11:43 Tim Landscheidt
2014-02-12 10:00 ` Thien-Thi Nguyen
2014-02-12 10:44 ` Tim Landscheidt
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=87eh2gwz7a.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=info-gnus-english@gnu.org \
/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;
as well as URLs for NNTP newsgroup(s).