From: "Georg C. F. Greve" <greve@gnu.org>
Subject: wrong MIME composing
Date: 21 Nov 2000 16:19:30 +0100 [thread overview]
Message-ID: <m3vgthqrnh.fsf@reason.gnu-hamburg> (raw)
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
Hi Everyone!
I got the other problems fixed by now... as usual they were caused by
interference effects with third party software. Oh well.
But there are two things that are quite disturbing:
- When sending out a crypto/signed mail with attachments, the
attachments do not get encrypted/signed
- The unsigned/unencrypted attachments get the wrong content
type.
Later,
Georg
--
Georg C. F. Greve <greve@gnu.org>
the monthly GNU forum in English, German,
French, Spanish and Japanese. Check it out
at http://brave-gnu-world.org/
[-- Attachment #2: Type: application/pgp-signature, Size: 268 bytes --]
next reply other threads:[~2000-11-21 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 15:19 Georg C. F. Greve [this message]
2000-11-21 15:32 ` ShengHuo ZHU
2000-11-21 23:28 ` Georg C. F. Greve
2000-11-22 1:07 ` ShengHuo ZHU
2000-11-22 10:42 ` Georg C. F. Greve
2000-11-22 13:48 ` ShengHuo ZHU
2000-11-22 14:39 ` Georg C. F. Greve
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=m3vgthqrnh.fsf@reason.gnu-hamburg \
--to=greve@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).