From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: Juergen Freitag <jf@amaunet.cs.uni-dortmund.de>,
Christian Altenschmidt <altensch@amaunet.cs.uni-dortmund.de>,
Joachim Biskup <biskup@amaunet.cs.uni-dortmund.de>
Subject: Re: `name' parameter for MIME attachments?
Date: 07 Sep 1999 13:56:20 +0200 [thread overview]
Message-ID: <vaf7lm37x5n.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Toby Speight's message of "07 Sep 1999 12:46:04 +0100"
Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:
> "name" isn't a valid parameter for application/postscript. Generating
> invalid MIME is not something I want Gnus to be doing. Why not fix
> dtmail instead?
Oops, I didn't know that. Hm. Surely we don't want Gnus to produce
invalid MIME.
kai
--
I like BOTH kinds of music.
next prev parent reply other threads:[~1999-09-07 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-07 11:30 Kai Großjohann
1999-09-07 11:46 ` Toby Speight
1999-09-07 11:56 ` Kai Großjohann [this message]
1999-09-25 8:31 ` Lars Magne Ingebrigtsen
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=vaf7lm37x5n.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=altensch@amaunet.cs.uni-dortmund.de \
--cc=biskup@amaunet.cs.uni-dortmund.de \
--cc=jf@amaunet.cs.uni-dortmund.de \
/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).