<literal>Subject</literal> and
<literal>Body</literal> header fields, which are the only requirement
specified by the
- <literal>mailto:</literal>specification in RFC2368.</para>
+ <literal>mailto:</literal>specification in RFC2368, and
+ the <literal>Cc</literal>, <literal>In-Reply-To</literal>,
+ <literal>References</literal> headers to aid with replies to
+ mailing lists.</para>
</sect1>
</chapter>
.IP
These commands allow the user to modify the list of allowed header
fields in a \fImailto:\fP URL that Mutt will include in the
-the generated message. By default the list contains only
-\fBsubject\fP and \fBbody\fP, as specified by RFC2368.
+the generated message. By default the list contains
+\fBsubject\fP and \fBbody\fP, as specified by RFC2368; and
+\fBcc\fP, \fBin-reply-to\fP, and \fBreferences\fP to aid with
+mailto links from mailing lists.
.SH PATTERNS
.PP
In various places with mutt, including some of the above mentioned
*/
add_to_list(&MailtoAllow, "body");
add_to_list(&MailtoAllow, "subject");
+ /* Cc, In-Reply-To, and References help with not breaking threading on
+ * mailing lists, see https://github.com/neomutt/neomutt/issues/115 */
+ add_to_list(&MailtoAllow, "cc");
+ add_to_list(&MailtoAllow, "in-reply-to");
+ add_to_list(&MailtoAllow, "references");
if (!Muttrc)
{