freescout
freescout copied to clipboard
creating a new conversation, adds RE: to the sent email
Hi Team,
When I creating a new conversation via FreeScout, script automaticaly adds RE: prefix to the sent email. I think it's malfunction.
I think this is a malfunction. Such a prefix should only be added to the answer, not new message.
Regards to all!
We can't confirm the issue. Try to write a step-by-step instruction on how to reproduce it.
Hello,
it's just a step to creating a new conversation through the FreeScout panel.
So I log in to the FreeScout Panel - then select New conversation - fill in the fields and send a message.
When I look at the message in my mailbox, I have the prefix with RE: as in response to a report, but it's a new conversation, not a reply.
Can you reproduce it on demo.freescout.net?
Do you have any non-official modules active?
Sure, I sent an e-mail.
But I haven't received @ gmail.com in my account yet.
I have only no-reply module.
demo.freescout.net does not send outgoing emails. Can you make some screenshots or video?
So I cannot reproduce this, because outgoing emails has set this prefix.
Check the screenshot please - as you can see in send mail I have a prefix "Odp:" - it means the same "RE:"
It must be your email client. In FreeScout code there is not such text as "Odp".
I am explaining that this translation into Polish - FreeScout adds the prefix "RE:" to the message sent and it means the same as in Polish "Odp:"
Check this from RoundCube. It'a also my mail client? :)
Try to post here original text of the email - something like "Show original".
It's original text . I only post "*" to hide my data.
From: ******** Subject: Re: prefix To: *******@icloud.com MIME-Version: 1.0 Content-Type: TEXT/html; CHARSET=US-ASCII
prefix test
-- Regards, Your Support
What version of FreeScout are you using? Can you show where you are creating the conversation.
All what you need in attachment.
We'll leave it as help wanted - maybe someone will be able to reproduce and fix it.
Can somebody experiencing this issue please reproduce in the latest version 1.8 or later?
Closing for no activity.