Since moving to our new Exchange 2010 server all e-mails to the KBox have a winmail.dat attached to it. Also embedded pictures no longer work. Is there anyone else who has had this issue?

I am on 5.3 if it matters.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
You need to send email to the KBOX in plain-text format.

http://support.microsoft.com/kb/138053
Answered 08/09/2011 by: airwolf
Tenth Degree Black Belt

Please log in to comment
0
Changed to Plain Text, HTML, and Rich Text and all 3 show up as Winmail.dat

So I need another solution.
Answered 08/17/2011 by: Capt.Morgan
Orange Belt

Please log in to comment
0
Could be a 5.3 bug... You may want to contact Dell KACE support.
Answered 08/17/2011 by: airwolf
Tenth Degree Black Belt

Please log in to comment
0
We have had this from the beginning (winmail.dat attachment) and we are on 5.2 (started with 5.1). You can get a free file opener that will open .dat files. Your ticket should display the original email, the .dat file is just the email saved in the ticket.
Answered 08/22/2011 by: TexasRose
Orange Senior Belt

Please log in to comment
0
Are you running Exchange 2007/2010?

We have done the same thing but it is a pain since we have hundred tickets a day.
Answered 08/24/2011 by: Capt.Morgan
Orange Belt

Please log in to comment
0
You could write a custom ticket rule to remove the file. With a grain of salt... The query might be something like this:

select HD_TICKET_CHANGE.ID from HD_TICKET, HD_TICKET_CHANGE
WHERE HD_TICKET.ID=HD_TICKET_ID
and DESCRIPTION like '%winmail.dat%'

the update would be something like:

UPDATE HD_TICKET_CHANGE
SET DESCRIPTION=REPLACE(DESCRIPTION,'winmail.dat','Attachement deleted by rule')
WHERE HD_TICKET_CHANGE.ID IN (<TICKET_IDS>)
Answered 08/24/2011 by: cblake
Red Belt

Please log in to comment
1
We have resolved this issue.

For Exchange 2010 we did the following:

1) Open Exchange Management Consoel
2) Expand Organization Configuration
3) Select Hub Transport
4) Double Click Default under Remote Domains
5) Select Message Format (2nd Tab)
6) Under Exchange rich-text format select Never Use.
Answered 09/06/2011 by: Capt.Morgan
Orange Belt

  • We had the same issue but instead of changing the policy for the whole domain. You can change this at the contact level for the kbox. (help@help.mycompany.com.)Right click the contact go to properties and select Use MAPI rich text format to Never and that will fix the issue.
Please log in to comment
0

Or to further enhance Capt.Morgan's answer, we added a new Remote Domain to handle emails to Kace so it didn't effect all emails.

For Exchange 2010 we did the following:

1) Open Exchange Management Consoel
2) Expand Organization Configuration
3) Select Hub Transport
4) Under Actions on Remote Domains tab (far right), Click New Remote Domain.
5) Give the Remote Domain a Name and Domain name. You may or may not need to tick the "include all subdomains". Click New to complete.
6) Double click your newly created Remote domain from the list under Remote Domains.
7) ClickSelect Message Format (2nd Tab)
8) Under Exchange rich-text format select Never Use.

Job Done! =)

Answered 12/11/2012 by: designworks
Senior Yellow Belt

Please log in to comment
0
I know this is an old question, but I just recently ran into this problem and then figured out a solution, and I wanted to share in case it helps someone else.

Our setup: Exchange 2010, K1000 v5.5

I set up our system by creating an Exchange Mail Contact itsupport@k1000.[mydomain].com, then a distribution list itsupport@[mydomain].com that had the mail contact as its only member. We give out the itsupport@[mydomain].com address as the one for people to submit tickets to.

Everything was working fine with attachments, they all made it through ok. Then one user complained that all his attachments were turned into winmail.dat. Eventually I figured out that he was e-mailing itsupport@k1000.[mydomain].com directly. Once he switched to the distribution list e-mail itsupport@[mydomaion].com, his attachments made it through correctly.

It doesn't matter if we send in attachments with e-mails that are plain text, RTF or HTML, they all work fine when submitted through the distribution list.

Hope that helps someone.
Answered 09/04/2014 by: Pulpitude
Senior White Belt

Please log in to comment
Answer this question or Comment on this question for clarity