troutmak
asked on
Question mark in OWA when sending new or replying to email messages.
I saw that a work around was posted, but I am actually looking for a fix.
I have a pc that will not allow a user to send emails from Outlook Web Access without getting this "?" in the body of the message.
I installed the S/Mime and it appears to resolve the issue, but now the issue appears to be more than a couple of users. Your thoughts?
I have a pc that will not allow a user to send emails from Outlook Web Access without getting this "?" in the body of the message.
I installed the S/Mime and it appears to resolve the issue, but now the issue appears to be more than a couple of users. Your thoughts?
LeeDerbyshire
Did you install the S/MIME control only on the server? If so, I think you will find that each of your affected users must now download it via OWA.
ASKER
I installed this on each affected user and this resolved the problem. The only issue I have is out of the 250 people on the various servers, 2 are affected and now I am up to 10 users affected with nothing changing on the network.
Thanks
Keith
Thanks
Keith
THe question marks are replacements for unknown characters. I am assuming that your users are beginning to correspond with some foreign language customers - typically an eastern character set. The problem is that the original message comes into your exchange environment with the characters represented faithfully, but as a user internally who does not have the full character set touches (ie fowards, replies...) the message it loses its encoding.
What the S/MIME control is doing for you is forcing the client to use the UTF-8 encoding standard which is capable of faithfully retaining and displaying these character sets.
What the S/MIME control is doing for you is forcing the client to use the UTF-8 encoding standard which is capable of faithfully retaining and displaying these character sets.
ASKER
This is happening when they attempt to send emails to anyone. I can understand if this issue was a Language settings on the workstation not being available, however all settings have been confirmed.
If I login as them on another computer - works fine, if I login to their computer - then I am stuck with the same fate as they are, but only on that machine.
As it started as a couple of people - the Mime thing is a good work around. But as it is increasing - I need to look for the cause of the problem.
As our company is USA based - we do nothing with other Language markets, so outside of possible a spam message with foreign characters - I can't see how it would have switched for a select amount of users.
Thanks
Keith
If I login as them on another computer - works fine, if I login to their computer - then I am stuck with the same fate as they are, but only on that machine.
As it started as a couple of people - the Mime thing is a good work around. But as it is increasing - I need to look for the cause of the problem.
As our company is USA based - we do nothing with other Language markets, so outside of possible a spam message with foreign characters - I can't see how it would have switched for a select amount of users.
Thanks
Keith
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, This is what I found on another forum...
This is a fairly common problem and there several solutions. The first one you should try is to install S/MIME from OWA's Options. Make sure that the client has all of the latest IE updates, then use OWA to download the latest version of the S/MIME control. This will fix it in most cases.
If installing the S/MIME control doesn't fix it, it's possible that another application installed a downreved dhtmled.ocx and triedit.dll. The install program probably just looked in the Windows\System32 directory, did not see the files, so it installed them and registered them. The ones you need to use are located in C:\Program Files\Common Files\Microsoft Shared\Triedit. Open a command prompt, change directory to C:\Program Files\Common Files\Microsoft Shared\Triedit and then use regsvr32 to re-register the correct versions of dhtmled.ocx and triedit.dll. You can then go delete the older versions that are probably located in your windows\system32.
If neither of these solutions corrects the problem, does the client have a product called SolarWinds Professional edition installed on their desktop? This is a known cause and it's possible there are other programs that may also cause it. If other computers can send using OWA and not add question marks to the message body, compare the applications installed on each in an attempt to identify the cause.
This is a fairly common problem and there several solutions. The first one you should try is to install S/MIME from OWA's Options. Make sure that the client has all of the latest IE updates, then use OWA to download the latest version of the S/MIME control. This will fix it in most cases.
If installing the S/MIME control doesn't fix it, it's possible that another application installed a downreved dhtmled.ocx and triedit.dll. The install program probably just looked in the Windows\System32 directory, did not see the files, so it installed them and registered them. The ones you need to use are located in C:\Program Files\Common Files\Microsoft Shared\Triedit. Open a command prompt, change directory to C:\Program Files\Common Files\Microsoft Shared\Triedit and then use regsvr32 to re-register the correct versions of dhtmled.ocx and triedit.dll. You can then go delete the older versions that are probably located in your windows\system32.
If neither of these solutions corrects the problem, does the client have a product called SolarWinds Professional edition installed on their desktop? This is a known cause and it's possible there are other programs that may also cause it. If other computers can send using OWA and not add question marks to the message body, compare the applications installed on each in an attempt to identify the cause.