|
|
|
|
Re: Kerio Connect cannot correctly render Outlook templates [message #127919 is a reply to message #118621] |
Fri, 12 February 2016 18:32   |
 |
Justice
Messages: 17 Registered: February 2016 Location: Bakersfield, CA
|
|
|
|
This is a major problem for us as well. Outlook Templates are a huge time saver for our organization and the lack of HTML functionality by Kerio is surprising. This should be a relatively simple fix for the development team. Templates are already allowed. They just save in Plain Text format (which looks unprofessional). I've already put in my vote on the Admin side with Kerio to fix this. There have to be others that are frustrated with this as well but just don't have the time to hound Kerio over it.
|
|
|
|
Re: Kerio Connect cannot correctly render Outlook templates [message #127998 is a reply to message #127996] |
Wed, 17 February 2016 19:50   |
 |
Justice
Messages: 17 Registered: February 2016 Location: Bakersfield, CA
|
|
|
|
Hello and thank you for your response. I appreciate it! Here is the process I have been using.
1) Create email in HTML format within Outlook
2) Save as .OFT file to Personal Templates folder
3) Select Template to Use
Ever since we switched to Kerio, the Template once saved converts to Plain Text even though it was created in HTML.
|
|
|
|
Re: Kerio Connect cannot correctly render Outlook templates [message #128167 is a reply to message #128124] |
Thu, 25 February 2016 19:50  |
 |
Justice
Messages: 17 Registered: February 2016 Location: Bakersfield, CA
|
|
|
|
To any and all who are looking to use this functionality and not getting a response from Kerio, here is a workaround I discovered:
1) When saving the .OFT, save it Rich Text Format
2) The template will save and render correctly but once sent will convert back to Plain Text format.
3) To get it to send as intended, change the format button back to HTML before sending and it will go through properly.
Hopefully, Kerio can find some time to get their connector to restore this functionality back to Outlook without the workaround - but for now, at least we have something that works.
If you find a better workaround, please do not hesitate to share!
|
|
|