You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
This is a fresh install and I am a new user of FreeScout testing for a quite small setup. E-mail fetching is working fine and tickets are registered. When I write a response to these tickets through the UI, they are sent as expected, with history included as configured, to the user who opened it, but although the body is clearly HTML, all email clients (tested with Outlook on Web, Outlook for Desktop and Thunderbird) show the context as plain text, including all markup.
How can I either (1) make sent messages display as HTML in the remote clients (something I have not enabled maybe) or (2) prepare the e-mail body as plain text so that it matches the headers?
I installed from zip on a cPanel host that is owned and operated by me, so I have full root access to anything and everything, meaning something might not be enabled that "commonly" would, and stuff like that, but Joomla and other types of webapp have installed without too much hassle.
The text was updated successfully, but these errors were encountered:
Hello.
This is a fresh install and I am a new user of FreeScout testing for a quite small setup. E-mail fetching is working fine and tickets are registered. When I write a response to these tickets through the UI, they are sent as expected, with history included as configured, to the user who opened it, but although the body is clearly HTML, all email clients (tested with Outlook on Web, Outlook for Desktop and Thunderbird) show the context as plain text, including all markup.
How can I either (1) make sent messages display as HTML in the remote clients (something I have not enabled maybe) or (2) prepare the e-mail body as plain text so that it matches the headers?
I installed from zip on a cPanel host that is owned and operated by me, so I have full root access to anything and everything, meaning something might not be enabled that "commonly" would, and stuff like that, but Joomla and other types of webapp have installed without too much hassle.
The text was updated successfully, but these errors were encountered: