Missing 'in-reply-to' in 6.1.8
Collapse
X
-
This should not be logged as a bug.
If it's very important for you you can add it to the code before the release. For 8 years we didn't have this feature.
Last edited by yuri; 08-06-2021, 03:50 PM.If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks. -
IIRC we use References header rather than In-Reply-To to detect what the email is related to. I'm not sure setting the in-reply-to header will help.If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.Comment
-
-
References used to link contact or account, not case.
If there was no in-Reply-To header, then the reply email is not linked to the original one and a new case is created.If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.Comment
-
I see 3 message header fields:
1. Message-Id - referenced to original linked entity
2. in-reply-to: used when imported to detect previsous email and detect create case or not, don't sended
3. references: used to detect referenced lead/contact/account, don't sendedComment
-
> 2. in-reply-to: used when imported to detect **** and detect create case or not
Can you point where In-Reply-To is used to detect whether to create case or not?
I believe that to fix your problem we need to send "Rererences' header rather than In-Reply-To. Message-ID of the replied email should be set in References header of the email being sent.
Last edited by yuri; 08-07-2021, 12:33 PM.If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.Comment
-
1. Define $replied by in-reply-to
EspoCRM – Open Source CRM Application. Contribute to espocrm/espocrm development by creating an account on GitHub.
2. Set received email parentType ParentId from $replied
EspoCRM – Open Source CRM Application. Contribute to espocrm/espocrm development by creating an account on GitHub.
3. Check parentType == 'Case' and skip emailToCase below
-
I see now. We didn't have this logic initially, it was added in some 4.x version. I forgot about its existence. In most cases a mail client sends References header and the parent is resolved by References. Anyway I will add the References header for replied emails in v7.0.0.
-
Comment