unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: HGV <hgv@fastmail.com>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: Help with sending mail from notmuch-emacs
Date: Mon, 30 May 2022 16:37:29 -0400	[thread overview]
Message-ID: <m27d62hi46.fsf@fastmail.com> (raw)
In-Reply-To: <87czgdwxon.fsf@tethera.net>

Thanks, David, for your continued help. I believe I have sorted this out and just
wanted to note what I found here for posterity in case others looking at the
archives have my same question.

Once I determined that indeed my issues with Content-Transfer-Encoding and
Content-Type headers happened with message-mode outside of notmuch, I read more
about how message-mode, MIME, and the rest of the sending chain all work
together. The problem seems to be that I was sending simple test emails to
myself that had only ASCII characters. Despite my own utf-8 encoding,
message-mode recognized that the files only had ASCII characters and set the
Content-Type header as just "text/plain" or "text/plain; charset=ascii" (still
not sure about the charset aspect). And with only one ASCII-only plain-text
part, Content-Transfer-Encoding was not necessary and therefore not set. When I
use a utf-8 character (e.g., Süßwasser), both the Content-Type and
Content-Transfer-Encoding were correctly set.

Thanks again for the tremendous software and help.

Yours kindly,
HGV\r

  reply	other threads:[~2022-05-30 20:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 21:54 Help with sending mail from notmuch-emacs hgv
2022-05-09 22:13 ` David Bremner
2022-05-09 22:51   ` hgv
2022-05-12 21:47 ` David Bremner
2022-05-13 22:38   ` hgv
2022-05-16 10:59     ` David Bremner
2022-05-30 20:37       ` HGV [this message]
2022-05-31  0:57         ` David Bremner

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://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m27d62hi46.fsf@fastmail.com \
    --to=hgv@fastmail.com \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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).