Hey Cameron, Many thanks for your contribution. Is I tried to explainin my original message my issue is not with _responding_ to messages coming from Discourse, but rather to not being able to identify them as such in the index because I can't make Mutt display an L for mailing list instead of the + it currently and inaccurately displays for Discourse posts sent by e-mail suggesting that these emails are addressed to me personnaly whereas this is obviously not the case.
Best, Seb. Cameron Simpson (2025/03/21 08:56 +1100): > I also receive Discourse forum posts via email. > > I don't make use of mutt's list stuff myself, so this advice may need some > adaption. Personally, I reply to all messages with "g" > (group-reply) and inspect the to/cc headers presented for correctness. > > Note that Discourse messages have a "Reply-To:" header. This contains the > email address which appends your reply to the correct message thread on the > Discourse forum. > > Have you tried an ordinary "nonlist" reply to such a message? Does it do > what you need already? > > For me it composes a new message to that address. Here's an example when I > reply to a Python Discourse message: > > From: Cameron Simpson <c...@cskk.id.au> > To: "Discussions on Python.org" > <incoming+83cadca6a412e454928b5a11601f2...@python1.discoursemail.com> > Cc: > Bcc: c...@cskk.id.au > Subject: Re: [Py] [Ideas] Abstract Base Class for `queue.Queue` and > `multiprocessing.Queue` > Reply-To: > In-Reply-To: <discourse/post/235...@discuss.python.org> > > So doing a nonlist reply might "just work" for you. > > Cheers, > Cameron Simpson <c...@cskk.id.au>
