Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Fwd: E-mail attachments and local names
Date: 27 Aug 1999 23:57:47 +0200	[thread overview]
Message-ID: <m3g114zy1w.fsf@quimbies.gnus.org> (raw)
In-Reply-To: dsg@mitre.org's message of "27 Jul 1999 10:48:14 -0400"

dsg@mitre.org (David S. Goldberg) writes:

> I thought that too.  Then I tried it :-) Unfortunately, the name tag
> gets copied to the Content-Type part rather than Content-Disposition,
> where the filename tag goes.  The latter gets preference for the
> suggested filename when saving.  The former just shows up as a label
> in the button.  What's needed is either an option that says if both
> name and filename are specified in MML, then after using filename to
> load the content, the filename tag in the Content-Disposition header
> gets the value of the name tag; or, invent a new tag if overloading
> name is a bad idea.  I started to make a pass at doing just that
> (called `filesuggestion' for lack of a better idea) yesterday.  I'll
> post a patch once its ready and I've had a chance to try it out.

I think if people compose a Word document called
They-Are-Going-To-Go-Broke-If-They-Sign-This-Contact.doc and send it
off, they deserve having the recipient seeing what the name of the
document is.  (And in the case of Word files, the name of the file is
also stored inside the file itself.  Ha!)

But, sure, adding a new parameter -- displayfilename, for instance --
would be OK.  If you send me a patch, I'll apply it.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


      reply	other threads:[~1999-08-27 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-24 14:22 Robert Bihlmeyer
1999-07-26 16:58 ` Hrvoje Niksic
1999-07-27 12:29   ` Kai Großjohann
1999-07-27 14:48     ` David S. Goldberg
1999-08-27 21:57       ` Lars Magne Ingebrigtsen [this message]

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=m3g114zy1w.fsf@quimbies.gnus.org \
    --to=larsi@gnus.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).