From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Cc: Norbert Goevert <goevert@amaunet.informatik.uni-dortmund.de>
Subject: strange CTE header
Date: 29 Dec 1998 19:37:25 +0100 [thread overview]
Message-ID: <86u2yesska.fsf@slowfox.cs.uni-dortmund.de> (raw)
Outgoing messages with Latin 1 characters (äöü) are sent with CTE 8bit
rather than quoted-printable, even though
mm-content-transfer-encoding-defaults is
,-----
| mm-content-transfer-encoding-defaults's value is
| (("text/.*" quoted-printable)
| ("message/rfc822" quoted-printable)
| ("application/emacs-lisp" 8bit)
| ("application/x-patch" 8bit)
| (".*" base64))
|
|
| Documentation:
| Alist of regexps that match MIME types and their encodings.
`-----
What can I do?
kai
--
Just because I'm paranoid doesn't mean they're not out there to get me!
next reply other threads:[~1998-12-29 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-29 18:37 Kai.Grossjohann [this message]
1998-12-30 9:33 ` Lars Magne Ingebrigtsen
1998-12-30 17:56 ` Kai.Grossjohann
1999-01-02 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=86u2yesska.fsf@slowfox.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=goevert@amaunet.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).