Users are reporting an issue where Discourse is rejecting manually sent emails from Gmail due to headers indicating the mail is auto-generated, specifically citing Precedence: list and Auto-Submitted: auto-generated, even though the emails are typed manually. Andro notes the presence of mailing list headers like List-ID and List-Post, which Discourse seems to interpret as automated. steinjer explains that since the latest release, Discourse now requires users to “Reply to list” (not just “Reply”) due to a code change that adds the List-Post header, effectively making Discourse behave like a mailing list server—even if not explicitly configured as one. The change stems from this PR, specifically an if clause modification in lib/email/sender.rb. martin questions whether this means users must “Reply to All” and asks for clarification on which code change caused the behavior, noting that the only altered condition appears to involve .to_s. steinjer confirms the new List-Post header is now always added, and provides screenshots showing the visual and header differences before and after the update. The core issue is that Discourse now treats all reply emails as mailing list messages, which interferes with manual replies from external clients.
I am hand sending inbound emails from Gmail. But Discourse rejects with complaints that Precedence is set to list, and that the mail is auto-generated - but it is not: I typed it.
Since the current release, mail replies always require a reply to “Reply to list”. A simple reply by clicking on “Reply” in the mail programme no longer works.
New in Mailheader is this line: List-Post: <mailto:replies+0d953a3a06191ea09a38f1f4f62129c4@forum.example.org>
Since this is added in Code (changed if clause) our discourse works as a mailinglist server but we didn’t choose this option.
Do you mean you have to “Reply to All”? I am not sure what you mean by “Reply to list”. What code in that PR would have changed this behaviour? The only if clause I can see that changed is this:
But I cannot see how that would have changed the behaviour just by adding to_s?