[GH-ISSUE #251] Support mailto links including subject, body, cc, bcc #212

Closed
opened 2026-02-25 21:34:27 +03:00 by kerem · 7 comments
Owner

Originally created by @ulfgebhardt on GitHub (Jan 9, 2018).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/251

Originally assigned to: @jasonmunro on GitHub.

[Feature Request]

Please support the subject, body and other parameters, which are standard for mailto-links.

Here is a Testpage to demonstrate diferent parameters for mailto-links.

Some more Info about compatibility.

Grüße Ulf

<3

Originally created by @ulfgebhardt on GitHub (Jan 9, 2018). Original GitHub issue: https://github.com/cypht-org/cypht/issues/251 Originally assigned to: @jasonmunro on GitHub. [Feature Request] Please support the subject, body and other parameters, which are standard for mailto-links. Here is a [Testpage](http://www.scottseverance.us/mailto.html) to demonstrate diferent parameters for mailto-links. Some more Info about [compatibility](http://mc-computing.com/HTML_Examples/MailTo.htm). Grüße Ulf <3
kerem 2026-02-25 21:34:27 +03:00
Author
Owner

@dumblob commented on GitHub (Jan 9, 2018):

I believe this is a specific feature just for the html content type as discussed in https://github.com/jasonmunro/cypht/issues/12 .

<!-- gh-comment-id:356437535 --> @dumblob commented on GitHub (Jan 9, 2018): I believe this is a specific feature just for the html content type as discussed in https://github.com/jasonmunro/cypht/issues/12 .
Author
Owner

@jasonmunro commented on GitHub (Feb 7, 2018):

@dumblob I don't know why this would not apply to plain text messages as well. Should be relatively easy to code up support for this.

<!-- gh-comment-id:363928272 --> @jasonmunro commented on GitHub (Feb 7, 2018): @dumblob I don't know why this would not apply to plain text messages as well. Should be relatively easy to code up support for this.
Author
Owner

@dumblob commented on GitHub (Feb 9, 2018):

@jasonmunro there are more reasons for that (basically the first one says it all, but for demonstration...):

  1. mailto links are defined in the HTML standard (and probably in similar XML-like standards) and nowhere else - i.e. they are expected on certain places, but absolutely not on other places
  2. plain text uses deliberately the word plain to show, that there is no distinction for the user between any two data chunks/files (disregarding what the content is - one can see e.g. an HTML document as plain text)
  3. plain text has no semantics, but adding this feature would add some very specific semantics - in that case we should definitely rather use an additional "view type" like "smart text"
  4. plain text has no syntax - why should the string mailto:"clickable text hiding some address"<this.will@be.hidden> or mailto:some@address.com?subject=%C5%BD%C3%A1dost%20o%20partnerstv%C3%AD&body=V%C3%A1%C5%BEen%C3%AD%20z%20OpenAlt%20z.s.%2C%0A%0Ar%C3%A1di%20bychom%20se%20stali%20partnerem%20Va%C5%A1%C3%AD%20konference%20OpenAlt.%20Kontaktujte%20n%C3%A1s%20pros%C3%ADm%20prost%C5%99ednictv%C3%ADm%20n%C4%9Bkter%C3%A9ho%20z%20n%C3%A1sleduj%C3%ADc%C3%ADch%20kan%C3%A1l%C5%AF%3A%0A%0AEmail%3A%0Aatd.%0A%0AS%20pozdravem%2C%0A%0AJm%C3%A9no%0A be treated differently than e.g. mailfrom:test@test2.org? It just doesn't make absolutely any sense.
  5. why not to use a mailto-compatible standard (e.g. HTML) to be able to use it? Why would I want to mix some standards to produce another non-standard view/format (most probably just Cypht-specific)?
  6. it's actually not so easy to code support for the full mailto specification
  7. ... lots of other reasons (mainly derived from the above 😉)

This rant is of course valid for addition of any specific meaning to chosen syntax constructs in plain text. Disregarding whether it's the mailto URI scheme or any other URI scheme or anything else.

<!-- gh-comment-id:364434692 --> @dumblob commented on GitHub (Feb 9, 2018): @jasonmunro there are more reasons for that (basically the first one says it all, but for demonstration...): 1. mailto links are defined in the HTML standard (and probably in similar XML-like standards) and nowhere else - i.e. they are expected on certain places, but absolutely not on other places 2. plain text uses deliberately the word **plain** to show, that there is no distinction for the user between any two data chunks/files (disregarding what the content is - one can see e.g. an HTML document as plain text) 3. plain text has no semantics, but adding this feature would add some very specific semantics - in that case we should definitely rather use an additional "view type" like "smart text" 4. plain text has no syntax - why should the string `mailto:"clickable text hiding some address"<this.will@be.hidden>` or `mailto:some@address.com?subject=%C5%BD%C3%A1dost%20o%20partnerstv%C3%AD&body=V%C3%A1%C5%BEen%C3%AD%20z%20OpenAlt%20z.s.%2C%0A%0Ar%C3%A1di%20bychom%20se%20stali%20partnerem%20Va%C5%A1%C3%AD%20konference%20OpenAlt.%20Kontaktujte%20n%C3%A1s%20pros%C3%ADm%20prost%C5%99ednictv%C3%ADm%20n%C4%9Bkter%C3%A9ho%20z%20n%C3%A1sleduj%C3%ADc%C3%ADch%20kan%C3%A1l%C5%AF%3A%0A%0AEmail%3A%0Aatd.%0A%0AS%20pozdravem%2C%0A%0AJm%C3%A9no%0A` be treated differently than e.g. `mailfrom:test@test2.org`? It just doesn't make absolutely any sense. 5. why not to use a mailto-compatible standard (e.g. HTML) to be able to use it? Why would I want to mix some standards to produce another non-standard view/format (most probably just Cypht-specific)? 6. it's actually not so easy to code support for the full [mailto specification](https://tools.ietf.org/html/rfc2368 ) 7. ... lots of other reasons (mainly derived from the above :wink:) This rant is of course valid for addition of any specific meaning to chosen syntax constructs in plain text. Disregarding whether it's the mailto [URI scheme](https://en.wikipedia.org/wiki/Mailto ) or any other URI scheme or anything else.
Author
Owner

@jasonmunro commented on GitHub (Feb 9, 2018):

@dumblob i'm not suggesting we use mailto links in a plain text E-mail. Cypht supports starting a new E-mail from a mailto link - either in an HTML formatted message you are reading, or in another webpage if you allow Cypht to be your mailto link handler in your browser. The ask here is to support the other mailto fields and not just the To field. The only content type issue is what type of outbound message format you are using. If the body field in a mailto link supports markup, we will need to do a little conversion before we populate the compose page depending on what your outbound mail format is.

<!-- gh-comment-id:364475422 --> @jasonmunro commented on GitHub (Feb 9, 2018): @dumblob i'm not suggesting we use mailto links in a plain text E-mail. Cypht supports starting a new E-mail from a mailto link - either in an HTML formatted message you are reading, or in another webpage if you allow Cypht to be your mailto link handler in your browser. The ask here is to support the other mailto fields and not just the To field. The only content type issue is what type of outbound message format you are using. If the body field in a mailto link supports markup, we will need to do a little conversion before we populate the compose page depending on what your outbound mail format is.
Author
Owner

@dumblob commented on GitHub (Feb 10, 2018):

Oh, then I'm sorry for the clutter - I misunderstood.

<!-- gh-comment-id:364643651 --> @dumblob commented on GitHub (Feb 10, 2018): Oh, then I'm sorry for the clutter - I misunderstood.
Author
Owner

@jasonmunro commented on GitHub (Apr 15, 2018):

Full mailto link support is pushed to the master branch. Thanks for the suggestion!

<!-- gh-comment-id:381437502 --> @jasonmunro commented on GitHub (Apr 15, 2018): Full mailto link support is pushed to the master branch. Thanks for the suggestion!
Author
Owner

@ulfgebhardt commented on GitHub (May 18, 2018):

<3 ur the best - just confirming that this works

<!-- gh-comment-id:390197012 --> @ulfgebhardt commented on GitHub (May 18, 2018): <3 ur the best - just confirming that this works
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cypht#212
No description provided.