Our discourse serves a wide community of different groups that do not interact regularly, but need to sometimes share information. The problem is that if someone forwards a received mail from one category to another category via email-in then the message ends up the the original topic instead of the category which email was used. Details: Running 2.9.0.beta1 We have email-in and reply-by-mail enabled in our instance Each category has an email assigned of the form discourse+CATEGORY@... Steps to reproduce: One receives an email notification of a new post in category A One forwards the received email to category B using it’s email discourse+CAT-B@... The forwarded message ends up in the original thread in category A Question: how to ensure the forwarded email ends up in the right category B? (without modifying any email header!)

Thanks for checking! Well, given that I reread the features of the mirror mail list option I guess it’s not a bug but intended as such: Usually find_related_post_with_key is enabled in the site settings. Disabling it for the whole site is not recommended, since it allows user impersonation based on email address. Incoming emails that were sent to the mailing list always use the email’s Message-ID to find related posts and disregard the value of that site setting. I mainly kept the option because of another point: Normally Discourse expects incoming emails to contain text formatted as Markdown. Mailing list users are usually unaware of that requirement, so Discourse doesn’t interpret any Markdown (except for code blocks enclosed in three backticks) or HTML within plain text emails and posts them with the original formatting intact. Which makes sense for people who have no idea of markdown :slight_smile:

[image] Artur L: The forwarded message ends up in the original thread in category B Do you mean it ends up in the originalte thread in category A? Again I’m answering knowing nothing and quite soon someone comes to tell how things really are — but AFAIK that should go that way and a reply doesn’t change to new topic just changing email.

true, thanks – fixed that! To clarify: the person does not reply to the email via reply-to, but forwards it setting the to: address manually to the discourse+cat-B@ email.

I can’t seem to reproduce this. These are my steps so far: Set up CategoryA and CategoryB, and assign them email-in addresses (categorya@[MyTestSite] and categoryb@[MyTestSite]) Set test_user to Watching for both categories Set email time window mins to 1 min (optional, but speeds things up) Admin posts topic to CategoryA Test_user receives notification email of new topic in CategoryA, and forwards it with message to CategoryB New topic is created in CategoryB (with a very ugly title :slightly_smiling_face: - Fwd: [JammyDodger's Test Site] [categorya] Topic for Category A), but only includes the added message, and not the intended forwarded information I can’t seem to replicate the issue where a forwarded email to a category ends up as a reply to an existing topic? Is there something extra I could try instead?

Thanks for trying! Could it have anything to do with the email client? I “blamed” discourse for grouping messages by the “in-reply-to” field rather than the “to” field..

ha, what do you have for that setting? [image]

[image] Artur L: Could it have anything to do with the email client? I “blamed” discourse for grouping messages by the “in-reply-to” field rather than the “to” field… I’m not sure? I used gmail for my tests, if that’s useful to know? [image] Artur L: ha, what do you have for that setting? I also have that as the default. :+1:

Nice spot @Moin :+1: [image]A mail reply may end up in the wrong category Here is how to reproduce the behavior on discourse 2.7.9: Create category A with mail a@example.com and category B with mail b@example.com Post a message in category A Reply via email and change the To: so that it is b@example.com The message ends up in category A, as a reply to the original message, instead of category B This is presumably because the mail headers have information that allow discourse to know this mail was sent as a reply from the original message. So it has to make a choice: should this message be sent to: I’ve just tried repro-ing this as well (a key difference seemed to be pressing ‘Reply’ and then manually changing the To address, rather than Forwarding), but mine ended up as a new topic in Category B again. Perhaps this does make it client specific? @artur Which are you using?

I just tried with my gmail but the mail still ended up in the original category. Weird – I’m surprised it worked for you! Could you check the headers of the forwarded mail? I see e.g. that the References contains the original topic id - could that have priority over the to: field?

Thanks for the link! Seems to be a similar situation except that in my case it’s about forwarding a mail and not replying. Hence I still don’t understand that behavior.

Email forward ends up in original topic

Product Support

Moin April 29, 2022, 10:47am 8

Reminds me of A mail reply may end up in the wrong category

Topic		Replies	Views
A mail reply may end up in the wrong category Product Support	7	856	December 15, 2021
Forwarding emails into Discourse without staging users Product Support	2	851	June 13, 2019
Configuring incoming email to create new topics with email forwarding? Product Support	0	123	August 8, 2024
Forwarding email from one discourse instance to another Feature	4	601	August 31, 2018
`enable_forwarded_emails` doesn't behave like conventional email forwarding Feature	18	3301	January 16, 2021

Email forward ends up in original topic

Related topics