From: Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de>
Subject: sgnus-0.36 + tm-7.41.1 == strange interaction
Date: 06 Feb 1996 11:25:45 +0100 [thread overview]
Message-ID: <vaflomghhsm.fsf@dusty.informatik.uni-dortmund.de> (raw)
Hi,
composing MIME mails with tm from within sgnus, I see the following
strange interaction regarding Gcc processing. I write a mail that
contains umlaut characters and a Gcc header.
I then try to send the mail using three different methods: hit C-c
C-c; hit C-c C-x C-z (thus exiting MIME mode), then C-c C-c; hit C-c
C-x C-z, then M-x gnus-mail-send-and-exit RET. Here's what happens:
(1) C-c C-c: The Gcc processing is done before tm converts the umlaut
characters to quoted-printable. Thus, the mail sent is
quoted-printable encoded, but the mail written to disk (by Gcc
processing) is not in MIME format.
(2) C-c C-x C-z, then C-c C-c: No Gcc processing is done! The mail
sent is correctly encoded in quoted-printable, of course. Please
note that the mail still contains the Gcc header after C-c C-x C-z
has been invoked.
(3) C-c C-x C-z, then M-x gnus-mail-send-and-exit RET: same as (2).
What's wrong here? I've had to revert to Bcc :-(
tia,
kai
--
Life is hard and then you die.
reply other threads:[~1996-02-06 10:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=vaflomghhsm.fsf@dusty.informatik.uni-dortmund.de \
--to=grossjoh@charly.informatik.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).