I *AM* sending the document as a word document attachment.  That is what I 
said in my original post.  It leaves my computer as a regular email (html 
formatted)  with a word document attachment.  It comes back to my computer 
as the same.  It is viewable out on Mediacom's web mail as a word 
document.  However, on my phone with k9 the file attachment is no longer a 
.doc but now a wimail.dat file.

Cindy

On Friday, May 15, 2015 at 9:08:52 AM UTC-5, John F. Eldredge wrote:

> As far as I know, Microsoft has never publicly released the details of 
> their proprietary email format. Certain companies have been able to license 
> this information, but have no doubt had to pay a substantial amount of 
> money and agree to non-disclosure agreements. If the full formatting needs 
> to be preserved, the best solution would likely be to send the document as 
> an attachment. 
>
>
>
> On May 13, 2015 6:24:31 AM CDT, Seth Holmes <[email protected] 
> <javascript:>> wrote: 
> > On 5/12/15 6:09 PM, Cindy wrote: 
> > > I do a lot of MS word documents/contracts on my computer to send to 
> > clients. 
> > > I always send myself a copy of it too.  So when it is coming from 
> > me, to me, I 
> > > can guarantee it is leaving as a .doc, and it comes back as a .doc 
> > online but 
> > > on my phone it comes in as a winmail.dat. 
> > > 
> > >   I used to be able to open and read my own .doc contracts on my 
> > phone but it 
> > > changed a while back (can't tell you the exact date it changed) but 
> > something 
> > > has changed with k9 to cause this problem since the document is fine 
> > out on 
> > > the web and when it comes into my desktop.  Since k9 used to be able 
> > to open 
> > > these just fine, I know that they should be able to fix whatever is 
> > causing 
> > > the problem now. 
> > > 
> > > Even if no one has the answer at present, k9 needs to look into 
> > changes they 
> > > have made that might be causing the issue and fix it back to the way 
> > it was. 
> > > Are the k9 coders reading these posts to know of the problem? 
> > 
> > The rest of the Internet recognizes that a winmail.dat file is a 
> > specific 
> > Microsoft proprietary format and that Microsoft has gone through great 
> > lengths 
> > to make it proprietary. 
> > 
> > It really does depend on the client you are using and whether or not 
> > it 
> > supports winmail.dat. The list is small. I know Outlook is on the 
> > list. I 
> > don't know what you use to access your e-mail over the web, but 
> > whatever it is 
> > probably supports winmail.dat files. Maybe is mchsi.com uses Exchange 
> > on the 
> > back end, it can handle winmail.dat files for you. There are some 
> > third party 
> > add-ons for Thunderbird that supposedly do this as well. But 
> > Thunderbird 
> > (arguably one of the most popular desktop clients on the Internet) 
> > does not 
> > support it. 
> > 
> > Here's what Microsoft has to say on the subject: 
> > 
> > https://support.microsoft.com/en-us/kb/278061 
> > 
> > SYMPTOMS 
> > You receive an email message that contains a winmail.dat attachment. 
> > This 
> > issue may occur if all of the following conditions are true: 
> > The email message is sent to you by someone using Microsoft Outlook. 
> > The format of the message is Rich Text format (RTF). 
> > 
> > This issue is more common when the email message is sent to you over 
> > the Internet. 
> > 
> > CAUSE 
> > The Winmail.dat file is used to preserve Rich Text formatting. Outlook 
> > uses it 
> > when sending a Rich Text-formatted message. During transport, the 
> > content of 
> > the message may be changed, preventing the receiving client from being 
> > able to 
> > read the formatting instructions. In other cases, the receiving client 
> > does 
> > not use or recognize the winmail.dat file. 
> > 
> > RESOLUTION 
> > The data in a winmail.dat file is not usable. To resolve this issue, 
> > ask the 
> > sender to re-send the message in plain text format. The following 
> > methods can 
> > be used by sender to prevent sending Rich Text messages encapsulated 
> > in the 
> > Transport Neutral Encapsulation Format (TNEF). 
> > 
> > Method 1: Change the default message format 
> > 
> > The sender can change the format of the email messages that they send 
> > by using 
> > the following steps: 
> > On the Tools menu, click Options, and then click Mail Format. 
> > In Compose in this message format, click to select Plain Text, and 
> > then click OK. 
> > NOTE: To send to certain recipients that use RTF format and others 
> > recipients 
> > that use plain text format, the sender must set the option for the 
> > recipient 
> > in either the Personal Address Book or the recipient's contact record. 
> > 
> > Method 2: Modify the recipient's entry in the Personal Address Book 
> > 
> > The sender can use the following steps to remove the RTF format from 
> > the 
> > recipient attribute in the Personal Address Book: 
> > On the Tools menu, click Address Book. 
> > In Show Names From, click the Personal Address Book. 
> > Select the addressee that you want to set as plain text, and then 
> > click 
> > Properties on the File menu. 
> > In the SMTP-General tab, click to clear the Always send to this 
> > recipient in 
> > Microsoft Exchange rich text format check box, and then click OK. 
> > 
> > Method 3: Change the specific contact format 
> > 
> > The sender can use the following steps to set plain text in the 
> > recipient's 
> > contact record: 
> > Open the recipient's record in the Contacts folder. 
> > Double-click the recipient's e-mail address. 
> > In the E-Mail Properties dialog box, click Send Plain Text only under 
> > Internet 
> > Format. 
> > 
> > Method 4: Set the Outlook Rich Text Format Internet e-mail setting 
> > 
> > In Outlook 2003 and Outlook 2007, click Options on the Tools menu. 
> > Click the Mail Format tab. 
> > Click Internet Format. 
> > Under Outlook Rich Text options, click either Convert to HTML format 
> > or 
> > Convert to Plain Text format. 
> > 
> > 
> > 
> > 
> > 
> > But I think it's more likely something changed on your end than 
> > something 
> > changed on K-9s end. I don't know that K-9 has ever supported 
> > winmail.dat 
> > files. Anyone know? Since it's possible for an administrator on a 
> > Windows 
> > network to modify your settings without your knowledge, it's very 
> > possible 
> > something changed without your knowledge. 
> > 
> > I'm a little more concerned you're sending legal documents to your 
> > e-mail 
> > address outside of your organization's system. 
> > 
> > 
> > 
> > But hey, the rest of the community could be wrong. I'm sure it's 
> > happened before. 
>
> -- 
> John F. Eldredge -- [email protected] <javascript:> (615) 299-6451 
> "Darkness cannot drive out darkness; only light can do that. Hate cannot 
> drive out hate; only love can do that." -- Martin Luther King, Jr. 
>

-- 
-- 
You received this message because you are subscribed to the K-9 Mail Users List.
To post to this group, send email to [email protected]
To unsubscribe, email [email protected]
To report an issue with K-9 Mail, visit 
http://code.google.com/p/k9mail/issues/list
For more options, visit this group at http://groups.google.com/group/k-9-mail

--- 
You received this message because you are subscribed to the Google Groups "K-9 
Mail" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to