Hi! Do any body no, how to make the HP Servise Desk server to receive an e-mail messages whith a graphics inserted into message body? HP SD 4.5 with SP19 can receive it, but save the graphics in a different txt-file. It`s inconveniently, to copy these files to local disk and rename to *.jpg.
Hi Evgeniy. This is a problem for SD - split correctly pictures from text. I test it before on MS Exchenge, in Exchenge server possible set on emails domain convert to plaint text , that working correctly. Try if you have Exchenge.
...but it only prompt Outlook to display all messages as plain-text. If you delete this DWORD, all messages, including sent with this DWORD, should be display as html again. Also it is impossibly to set all users to send all messages anly in plain text.
We recently upgraded our Exchange OS ie from Exchange 2003 on Windows 2000 to Exchange 2003 on Windows 2003. When we did this, the embedded images in html messages to SD no longer attached and the body of the email failed to get into the information field. The smtp service is supplied by Windows not exchange so I believe there is some differences between Windows 2000 and Windows 2003 smtp service.
I resolved this by changing the character set from US-ASCII to Western European Character Set. You could try Western European just to see if it is an issue with the Cyrillic character set not properly converting to plain text (which I assume is non trivial?) and then take this to Microsoft.
PS: Embedded images in "Rich Text" emails still fail to attach for us but the body of the message at least makes it to the information field - so we are happy with that.
I have select the Western European Character Set - nothing happens. The message recived after this is same as before. Content type and Character Set in this messages is same. This converting function is not works and i do not know, how to resolve this. I have try it on Exch 6.5(build 6544.4) and Exch 6.5 (build 7226.6: SP1) - nothing.
We are 6.5 build 7638.2 Service Pack 2. But the SMTP service is a windows service so I think the Exchange build is irrelevant.
However I did just recheck your settings and I noticed that you have Exchange Rich Text Format - always use. If this message format is only for Service Desk then you should have "never use" for Rich Text Format.
You would only have a message format with "Always Use" for Rich text format for an email domain that you are sure have MS Exchange and you want to preserve Rich text formatting for messages to that email domain. Service Desk will definitely dislike Rich Text format.
Thank you, David! Yes, I have already understand that the rich text format is unsuitable for HP SD. But it is only one setting in "Internet message options" that have any effect. Other settings are not change the message format - and this is cause of my headache. I think, I should setup an mail filter on freeBSD platform to convert mail to plain text.
I am a bit confused? I have attached the settings from your previous post that I think is wrong? OVSD cannot accept Rich Text emails - they must be converted to plain text. The setting Rich Text would only be used if your message format definition was for another Exchange based email domain.
However, as I said even with this the embedded graphics in Rich Text does not work but html should. Attachments in rich text and html should also be OK.
Send me an html email with an embedded graphic and if it looks good for me then maybe HP needs to help out. My address is David.Borojevic@education.tas.gov.au. If need be create a message format for *.education.tas.gov.au and make the settings the same as your service desk message format.
I got your email and replied to it but got a NDR (non deliverable report) and so here is the essence of the reply.
I tested your email forwarding to our test OVSD server and it failed. I tried numerous settings on the Message Format including those that work for us. Your html message uses a Russian character set and I suspect either Microsoft or HP are letting you down. I don't know which.
Good to see you have a Java solution working - though it is a shame you have to resort to that. You should log it with HP.