Sorry for answering that late. Let me know if it’s necessary to create a new thread.
I am using Claws-mail client under Ubuntu GNU/Linux and so far I haven’t had this problem with other websites and mailing lists.
I will show how Google groups deals with headers “Message-id”, “In-Reply-To” and “References”
and contrast it to how Discourse does it.
1) Original Post
Date: Thu, 30 Jun 2016 21:49:11 -0700 (PDT)
Subject: [elixir-talk:13407] Workflow in mix / iex
Message-Id: <2efa495f-d3d0-44f0-9cf1-e029d8e2be94@googlegroups.com>
2) Answer to no. 1
Date: Fri, 1 Jul 2016 08:13:54 +0100
Subject: Re: [elixir-talk:13407] Workflow in mix / iex
Message-ID: <CAM-pwt51kB_6yn3YHbo6Wa5VyUDytqPhfzfRRTdSaqsLiYsLJg@mail.gmail.com>
In-Reply-To: <2efa495f-d3d0-44f0-9cf1-e029d8e2be94@googlegroups.com>
References: <2efa495f-d3d0-44f0-9cf1-e029d8e2be94@googlegroups.com>
3) Answer to no. 2
Date: Fri, 1 Jul 2016 06:10:35 -0700 (PDT)
Subject: Re: [elixir-talk:13408] Workflow in mix / iex
Message-Id: <2b3de36a-2a6c-45cb-a199-0fcf11bfae1b@googlegroups.com>
In-Reply-To: <CAM-pwt51kB_6yn3YHbo6Wa5VyUDytqPhfzfRRTdSaqsLiYsLJg@mail.gmail.com>
References: <2efa495f-d3d0-44f0-9cf1-e029d8e2be94@googlegroups.com>
<CAM-pwt51kB_6yn3YHbo6Wa5VyUDytqPhfzfRRTdSaqsLiYsLJg@mail.gmail.com>
and this is how Discourse does it
1) Original Post
Date: Sat, 17 Sep 2016 04:52:11 +0000
From: Paul <noreply@elixirforum.com>
Reply-To: Elixir Forum <mailserver+b4b32a98d201ecf58eef9e4c7510b978@elixirforum.com>
Message-ID: <topic/1689/10607@elixirforum.com>
In-Reply-To: <topic/1689@elixirforum.com>
References: <topic/1689@elixirforum.com>
Subject: [Elixir Forum] [Elixir Help] Semi-Manual backpressure
2) Answer to no. 1
Date: Sat, 17 Sep 2016 14:04:13 +0000
From: José Valim <noreply@elixirforum.com>
Reply-To: Elixir Forum <mailserver+81161440220741d3b07fff9c53460ba1@elixirforum.com>
Message-ID: <topic/1689/10618@elixirforum.com>
In-Reply-To: <topic/1689@elixirforum.com>
References: <topic/1689@elixirforum.com>
Subject: [Elixir Forum] [Elixir Help] GenStage Semi-Manual backpressure
3) Answer to no. 2
Date: Sat, 17 Sep 2016 14:59:21 +0000
From: José Valim <noreply@elixirforum.com>
Reply-To: Elixir Forum <mailserver+5a396d7011668a282e6465a58028ae8a@elixirforum.com>
Message-ID: <topic/1689/10623@elixirforum.com>
In-Reply-To: <topic/1689@elixirforum.com>
References: <topic/1689@elixirforum.com>
Subject: [Elixir Forum] [Elixir Help] GenStage Semi-Manual backpressure
And this is how I think it should be the Discourse version (changes in bold)
> 1) Original Post
> Date: Sat, 17 Sep 2016 04:52:11 +0000
> From: Paul <noreply@elixirforum.com>
> Reply-To: Elixir Forum <mailserver+b4b32a98d201ecf58eef9e4c7510b978@elixirforum.com>
> Message-ID: <topic/1689/10607@elixirforum.com>
> **In-Reply-To: [SHOULD NOT BE PRESENT]**
> **References: [SHOULD NOT BE PRESENT]**
> Subject: [Elixir Forum] [Elixir Help] Semi-Manual backpressure
> 2) Answer to no. 1
> Date: Sat, 17 Sep 2016 14:04:13 +0000
> From: José Valim <noreply@elixirforum.com>
> Reply-To: Elixir Forum <mailserver+81161440220741d3b07fff9c53460ba1@elixirforum.com>
> Message-ID: <topic/1689/10618@elixirforum.com>
> **In-Reply-To: <topic/1689/10607@elixirforum.com>**
> **References: <topic/1689/10607@elixirforum.com>**
> Subject: [Elixir Forum] [Elixir Help] GenStage Semi-Manual backpressure
> 3) Answer to no. 2
> Date: Sat, 17 Sep 2016 14:59:21 +0000
> From: José Valim <noreply@elixirforum.com>
> Reply-To: Elixir Forum <mailserver+5a396d7011668a282e6465a58028ae8a@elixirforum.com>
> Message-ID: <topic/1689/10623@elixirforum.com>
> **In-Reply-To: <topic/1689/10618@elixirforum.com>**
> **References: <topic/1689/10607@elixirforum.com>, <topic/1689/10618@elixirforum.com>**
> Subject: [Elixir Forum] [Elixir Help] GenStage Semi-Manual backpressure
based on the idea that <topic/1689@elixirforum.com>
is an ID of a message that never existed (let’s call it “topic message id”)
I think there are few things causing trouble:
- setting in the original post a “In-Reply-To” HEADER, with a reference to the non-existant topic message id.
- setting references to non-existant IDs
- and setting always only one reference
- In reply to does not contain the message id of the message it’s replying to, but the non-existant topic message id, so making it impossible for some email clients to build the thread.
here’s a page that lists and references each message header.
https://www.cs.tut.fi/~jKorpela/headers.html
RFC 822
4.6. REFERENCE FIELDS
4.6. REFERENCE FIELDS
4.6.1. MESSAGE-ID / RESENT-MESSAGE-ID
This field contains a unique identifier (the local-part address unit) which refers to THIS version of THIS message. The uniqueness of the message identifier is guaranteed by the host which generates it. This identifier is intended to be machine readable and not necessarily meaningful to humans. A message identifier pertains to exactly one instantiation of a particular message; subsequent revisions to the message should each receive new message identifiers.
4.6.2. IN-REPLY-TO
The contents of this field identify previous correspondence which this message answers. Note that if message identifiers are used in this field, they must use the msg-id specification format.
4.6.3. REFERENCES
The contents of this field identify other correspondence which this message references. Note that if message identifiers are used, they must use the msg-id specification format.
RFC 1036
i cannot post more than 2 links so look for it in the first link
2.2.5. References
This field lists the Message-ID’s of any messages prompting the submission of this message. It is required for all follow-up messages, and forbidden when a new subject is raised. Implementations should provide a follow-up command, which allows a user to post a follow-up message. This command should generate a “Subject” line which is the same as the original message, except that if the original subject does not begin with "Re: " or "re: ", the four characters "Re: " are inserted before the subject. If there is no “References” line on the original header, the “References” line should contain the Message-ID of the original message (including the angle brackets). If the original message does have a “References” line, the follow-up message should have a “References” line containing the text of the original “References” line, a blank, and the Message-ID of the original message.
The purpose of the “References” header is to allow messages to be grouped into conversations by the user interface program. This allows conversations within a newsgroup to be kept together, and potentially users might shut off entire conversations without unsubscribing to a newsgroup. User interfaces need not make use of this header, but all automatically generated follow-ups should generate the “References” line for the benefit of systems that do use it, and manually generated follow-ups (e.g., typed in well after the original message has been printed by the machine) should be encouraged to include them as well.
It is permissible to not include the entire previous “References” line if it is too long. An attempt should be made to include a reasonable number of backwards references.
Looking forward to hearing from you.