From: Barry Margolin <barmar@alum.mit.edu>
Subject: Re: Rmail does not put a Content-type header
Date: Mon, 17 Jul 2006 21:14:20 -0400 [thread overview]
Message-ID: <barmar-FD576E.21142017072006@comcast.dca.giganews.com> (raw)
In-Reply-To: ur70jn8y1.fsf@jasonrumney.net
In article <ur70jn8y1.fsf@jasonrumney.net>,
jasonr (Jason Rumney) @ f2s.com wrote:
> maillaxa@gmail.com writes:
>
> >> > All my friends report problems when reading my mails :(
> >
> > Lucky you :) I tried several times to convert them but Thunderbird and
> > mutt are definetely their choices ...
>
> Thunderbird and Mutt do not have problems with plain text mails.
>
> What is the actual problem they are reporting?
He mentioned previously (maybe in a different thread) that he's sending
mail with non-ASCII characters (e.g. accented characters). These *do*
need a Content-type header to indicate the encoding scheme.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
next prev parent reply other threads:[~2006-07-18 1:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 23:26 Rmail does not put a Content-type header maillaxa
2006-07-15 14:23 ` maillaxa
2006-07-15 20:30 ` Eli Zaretskii
[not found] ` <mailman.4128.1152995462.9609.help-gnu-emacs@gnu.org>
2006-07-15 22:29 ` maillaxa
2006-07-16 3:12 ` Eli Zaretskii
2006-07-17 22:49 ` Jason Rumney
2006-07-18 1:14 ` Barry Margolin [this message]
2006-07-18 9:40 ` Xavier Maillard
2006-07-17 20:54 ` Kevin Rodgers
2006-07-17 22:47 ` Xavier Maillard
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=barmar-FD576E.21142017072006@comcast.dca.giganews.com \
--to=barmar@alum.mit.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).