From: Mahesh Padmanabhan <news@nospam.eml.cc>
Subject: RTF attachment problem
Date: Mon, 05 Aug 2002 01:01:58 GMT [thread overview]
Message-ID: <871y9e9kzi.fsf@nospam.eml.cc> (raw)
I was trying to send an RTF (which is the ASCII equivalent of the
Microsoft DOC format ) as an attachment to an email but the receiver
got it as a corrupted file. When I sent it, it asked me if the MIME
type should be application/msword and I said yes to that.
I then converted the RTF file to a DOC file and sent it in an
identical manner and this time the receiver got it correctly.
My questions are:
1) What does GNUS do if you give the wrong mime type,
i.e. application/msword for an RTF file ?
2) Why does it do it since I thought MIME type made no difference if
you saved the document at the receiving end and opened it ?
TIA,
--
Mahesh Padmanabhan
-------
Replace nospam with prana to email me.
next reply other threads:[~2002-08-05 1:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 1:01 Mahesh Padmanabhan [this message]
[not found] ` <iluvg6pppz8.fsf@latte.josefsson.org>
2002-08-05 15:30 ` Mahesh Padmanabhan
[not found] ` <vafy9blfrca.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <871y9dmipk.fsf@nospam.eml.cc>
2002-08-05 16:47 ` Kai Großjohann
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=871y9e9kzi.fsf@nospam.eml.cc \
--to=news@nospam.eml.cc \
/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).