From: Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de>
Subject: pgnus-0.33: multipart/mixed: usage of filename?
Date: 25 Sep 1998 11:29:59 +0200 [thread overview]
Message-ID: <vafogs48rqg.fsf@ramses.cs.uni-dortmund.de> (raw)
Hi all,
our fax software sends me multipart/mixed messages where each fax page
is a part, with headers like so:
,-----
| Content-Type: image/g3n
| Content-Disposition: inline; filename="/var/spool/fax/incoming/fn608ec94ya-_-+49-231-7552130_.01"
| Content-Transfer-Encoding: base64
`-----
After this header comes the fax itself, base64-encoded. When wanting
to view this file, Emacs tells me:
,-----
| Opening output file: no such file or directory, /var/spool/fax/incoming/fn608ec94ya-_-+49-231-7552130_.01 [2 times]
`-----
It seems that Gnus tries to write into that file, but as the directory
doesn't exist (it's a directory name from our fax server), that's
bound to fail.
Shouldn't Gnus write the file in /tmp as usual, disregarding the
filename, when *viewing* such stuff? I'd be happy with Gnus using the
filename as default when *saving* the stuff, but why is it used at all
for viewing?
kai
--
OOP: object oriented programming; OOPS: object oriented mistakes
next reply other threads:[~1998-09-25 9:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-25 9:29 Kai Grossjohann [this message]
1998-09-25 9:31 ` Kai Grossjohann
1998-09-28 9:14 ` Robert Bihlmeyer
1998-09-29 10:40 ` Lars Magne Ingebrigtsen
1998-09-29 12:59 ` Jan Vroonhof
1998-10-01 2:40 ` Lars Magne Ingebrigtsen
1998-10-01 9:02 ` Jan Vroonhof
1998-10-01 14:18 ` Lars Magne Ingebrigtsen
1998-10-01 18:33 ` Edward J. Sabol
1998-10-02 2:47 ` Lars Magne Ingebrigtsen
1998-10-02 10:48 ` grossjohann
1998-10-02 12:29 ` Simon Josefsson
1998-10-10 21:45 ` Lars Magne Ingebrigtsen
1998-10-02 9:01 ` Jan Vroonhof
1998-10-10 21:41 ` Lars Magne Ingebrigtsen
1998-10-10 23:28 ` Kai Grossjohann
1998-10-11 0:17 ` Lars Magne Ingebrigtsen
1998-10-12 9:52 ` Jan Vroonhof
1998-10-12 13:10 ` 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=vafogs48rqg.fsf@ramses.cs.uni-dortmund.de \
--to=grossjohann@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).