unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "Antoine Beaupré" <anarcat@orangeseeds.org>, notmuch@notmuchmail.org
Subject: Re: [RFC] writing HTML email with notmuch
Date: Mon, 25 Feb 2019 16:18:03 -0500	[thread overview]
Message-ID: <87o96zpnxw.fsf@fifthhorseman.net> (raw)
In-Reply-To: <875zt8zlav.fsf@curie.anarc.at>

[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]

Hi Antoine--

thanks for an entertaining and thoughtful read.

Your elisp rendered really strangely for me in notmuch mode in emacs:

     (widen)
     (save-excursion
       (set-buffer output-buffer-name)
       (markdown-add-xhtml-header-and-footer ""))
     (insert "
 [ multipart/alternative ]
  [ text/plain ]
  \n")
      (end-of-buffer)
      (insert "
  [ text/html (hidden) ]
\n") (insert-buffer output-buffer-name) (insert "
 [ text/plain ]
     ;; remove Markdown <pre> markings
     (goto-char signature-position)

(note the []-delimited emacs buttons above)

The issue here appears to be that the MIME boundaries in your message (i
won't repeat them here because i don't want to break my own message) are
getting mixed up/confused somehow with the mime boundaries you include
in the elisp.

I'd be happy to compare raw files with you at some point if you want to
try to make sense of this.  I'm hoping that the error is in the message
generation (that your sending MUA garbled your elisp) rather than in the
receipt, because if the receiving side is at fault it's a much worse
security risk.

On Sun 2019-02-24 20:52:40 -0500, Antoine Beaupré wrote:
> PPS: I remember reading about someone wanting to declare a text/markdown
> mimetype for email, and remembering it was all backwards and weird and I
> can't find the reference anymore. If some lazyweb magic person could
> forward the link to me I would be grateful.

https://tools.ietf.org/html/rfc7763 -- I'm sure Sean Leonard (the author
of this informational RFC) would be open to discussion about what's
missing or what could be improved.

        --dkg

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2019-02-25 22:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-25  1:52 [RFC] writing HTML email with notmuch Antoine Beaupré
2019-02-25 18:22 ` Istvan Marko
2019-02-25 18:56 ` Brian Sniffen
2019-02-25 22:58   ` Antoine Beaupré
2019-02-25 21:18 ` Daniel Kahn Gillmor [this message]
     [not found]   ` <87lg23ldrl.fsf@curie.anarc.at>
2019-02-25 23:01     ` Antoine Beaupré
2019-02-25 23:15       ` Daniel Kahn Gillmor
2019-02-26  5:33         ` non-ascii email forwarding failures Antoine Beaupré
2019-02-26  5:56           ` Daniel Kahn Gillmor
2019-02-26  7:51             ` Antoine Beaupré
2019-02-26 10:56           ` David Edmondson
2019-02-26 15:43             ` Antoine Beaupré
     [not found] <mailman.1.1551124801.2659.notmuch@notmuchmail.org>
2019-02-28  7:23 ` [RFC] writing HTML email with notmuch Jayanth R Varma

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=87o96zpnxw.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=anarcat@orangeseeds.org \
    --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).