DAT files i e-mails

Hi. When I receive a Mail with wordfiles, excel files or PDF files, they sometimes show up as a DAT file which I can not open. Is the problem in the computer of the one senind the file or is it in my iPad? If it is in my iPad, how can I correct it or open/convert the file to something I can read?

See this page : http://support.apple.com/kb/TS1506 - you need to get the sender to re-send the emails in plain text or HTML, not rich text

Similar Messages

  • Windows .jpeg attachment is received as windat.file in Mac mail

    Is there a setting I need to change so that .jpeg attachments sent from Windows are not received as win.dat files in Mac Mail?

    Are you sending the files, sbertochi?
    If so, there's some older advice on this page:
    http://www.modemhelp.net/newsletter/email/winmaildat.shtml
    If that doesn't seem applicable to your setup, what application (and version of the application) are you using to send the emails with the troublesome jpegs?

  • Pdf extension changes to .dat when send a file via e-mail from adobe acrobat 9

    to convert a file from microsoft word 2007 to PDF and send as an attachment via e-mail from adobe 9, the file is received with the extension changed to. dat, so recipients can not open it.
    Can anyone help me with this.

    What is the OS of the sending computer?
    What mail client?
    I receive plenty of files on my PC as .dat files, which come from Mac user(s), rename the extension to what I think they ought to be and have no further problem. (I cannot change the senders email settings where the problem originates)
    If the receiver knows it is a pdf file, they can drag it into Acrobat, but renaming the extension serves future use.

  • Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)

    Fresh installation of Exchange Server 2013 on Windows Server 2012.
    Our first test account cannot access their email via Outlook but can access fine through OWA. The following message appears - "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize
    your folders with your Outlook data file (.ost)" is displayed.
    If I turn off cached Exchange mode, setting the email account to not
    cache does not resolve the issue and i get a new error message - "Cannot open your default e-mail folders. The file (path\profile name).ost is not an Outlook data file (.ost). Very odd since it creates its own .ost file when you run it for the first
    time.
    I cleared the appdata local Outlook folder and I tested on a new laptop that has never connected to Outlook, same error message on any system.
    Microsoft Exchange RPC Client Access service is running.
    No warning, error or critical messages in the eventlog, it's like the healthiest server alive.
    Any help would be greatly appreciated. I haven't encountered this issue with previous versions of Exchange.

    So it looks like a lot of people are having this issue and seeing how Exchange 2013 is still new (relatively to the world) there isn't much data around to answer this. I've spend ALOT of time trying to figure this out.
    Here is the answer. :) - No I don't know all but I'm going to try to give you the most reasonable answer to this issue, in a most logical way.
    First thing I did when I was troubleshooting this issue is that I ignored Martina Miskovic's suggestion for Step4 http://technet.microsoft.com/library/jj218640(EXCHG.150)because it didn't make sense to me because I was trying to connect
    Outlook not outside the LAN but actually inside. However, Martina's suggestion does fix the issue if it's applied in the correct context.
    This is where the plot thickens (it's stew). She failed to mention that things like SSL (which I configure practically useless - anyone who ever worked in a business environment where the owner pretty much trusts anyone in the company, otherwise they don't
    work there - very good business practice in my eyes btw, can confirm that...) are some sort of fetish with Microsoft lately. Exchange 2013 was no exception.
    In exchange 2003, exchange 2007 and exchange 2010 - you could install it and then go to outlook and set it up. And when outlook manual Microsoft Exchange profile would ask you for server name, you would give it and give the name of the person who you setting
    up - as long as machine is on the domain, not much more is needed. IT JUST WORKS! :) What a concept, if the person already on premises of the business - GIVE HIM ACCESS. I guess that was too logical for Microsoft. Now if you're off premises you can use things
    like OutlookAnywhere - which I might add had their place under that scenario.
    In Exchange 2013, the world changed. Ofcourse Microsoft doesn't feel like telling it in a plain english to people - I'm sure there is an article somewhere but I didn't find it. Exchange 2013 does not support direct configuration of Outlook like all of it's
    previous versions. Did you jaw drop? Mine did when I realized it. So now when you are asked for your server name in manual outlook set up and you give it Exchange2013.yourdomain.local - it says cannot connect to it. This happens because ALL - INTERNAL AND
    EXTERNAL connection are now handled via OutlookAnywhere. You can't even disable that feature and have it function the reasonable way.
    So now the question still remains - how do you configure outlook. Well under server properties there is this nice section called Outlook anywhere. You have a chance to configure it's External and Internal address. This is another thing that should be logical
    but it didn't work that way for me. When I configured the external address different from the internal - it didn't work. So I strongly suggest you get it working with the same internal address first and then ponder how you want to make it work for the outside
    users.
    Now that you have this set up you have to go to virtual directories and configure the external and internal address there - this is actually what the Step 4 that Martina was refering to has you do.
    Both external and internal address are now the same and you think you can configure your outlook manually - think again. One of the most lovely features of Outlook Anywhere, and the reason why I had never used it in the past is that it requires a TRUSTED
    certificate.
    See so it's not that exchange 2013 requires a trusted certificate - it's that exchange 2013 lacks the feature that was there since Windows 2000 and Exchange 5.5.
    So it's time for you to install an Active Direction Certificate Authority. Refer to this wonderful article for exact steps - http://careexchange.in/how-to-install-certificate-authority-on-windows-server-2012/
    Now even after you do that - it won't work because you have to add the base private key certificate, which you can download now from your internal certsrv site, to Default Domain Policy (AND yes some people claim NEVER mess with the Default Domain Policy,
    always make an addition one... it's up to you - I don't see direct harm if you know what you want to accomplish) see this: http://technet.microsoft.com/en-us/library/cc738131%28v=ws.10%29.aspx if you want to know exact steps.
    This is the moment of ZEN! :) Do you feel the excitement? After all it is your first time. Before we get too excited lets first request and then install the certificate to actual Exchange via the gui and assign it to all the services you can (IIS, SMTP and
    there is a 3rd - I forgot, but you get the idea).
    Now go to your client machine where you have the outlook open, browse to your exchange server via https://exchang2013/ in IE and if you don't get any certificate errors - it's good. If you do run on hte client and the server: gpupdate /force This will refresh
    the policy. Don't try to manually install the certificate from Exchange's website on the client. If you wanna do something manually to it to the base certificate from the private key but if you added it to the domain policy you shouldn't have to do it.
    Basically the idea is to make sure you have CA and that CA allows you to browse to exchange and you get no cert error and you can look at the cert and see that's from a domain CA.
    NOW, you can configure your outlook. EASY grasshoppa - not the manual way. WHY? Cause the automatic way will now work. :) Let it discover that exachange and populate it all - and tell you I'm happy! :)
    Open Outlook - BOOM! It works... Was it as good for you as it was for me?
    You may ask, why can't I just configure it by manual - you CAN. It's just a nightmare. Go ahead and open the settings of the account that got auto configed... How do you like that server name? It should read something like [email protected]
    and if you go to advanced and then connection tab - you'll see Outlook Anywhere is checked as well. Look at the settings - there is the name of the server, FQDN I might add. It's there in 2 places and one has that Mtdd-something:Exchange2013.yourdomain.local.
    So what is that GUID in the server name and where does it come from. It's the identity of the user's mailbox so for every user that setting will be different but you can figure it out via the console on the Exchange server itself - if you wish.
    Also a note, if your SSL certs have any trouble - it will just act like outlook can't connect to the exchange server even though it just declines the connection cause the cert/cert authority is not trusted.
    So in short Outlook Anywhere is EVERYWHERE! And it has barely any gui or config and you just supposed to magically know that kind of generic error messages mean what... Server names are now GUIDs of the [email protected] - THAT MAKES PERFECT
    SENSE MICROSOFT! ...and you have to manage certs... and the only place where you gonna find the name of the server is inside the d*** Outlook Anywhere settings in the config tab, un it's own config button - CAN WE PUT THE CONFIG ANY FURTHER!
    Frustrating beyond reason - that should be Exchange's new slogan...
    Hope this will help people in the future and won't get delete because it's bad PR for Microsoft.
    PS
    ALSO if you want to pick a fight with me about how SSL is more secure... I don't wanna hear it - go somewhere else...

  • E-mail are received as DAT file instad of PDF

    Hi All,
    Please try to assist in this strange topic:
    When I try to send an e-mail via the SBO (press on the envelope button and choose u2018yesu2019 when
    the option u2018Would you like to attach an edited report to the e-mail?u2019 is display), the receiver is received a file with u2018DATu2019 extension and not with PDF extension and the receiver canu2019t open the file.
    I have tried to uninstall the acrobat reader 9 and install instead Foxit 3.1, but the problem still
    persists.
    In addition, I have found the this issue is reproduced only when the customer is using the Hebrew interface of SBO and the PDF file name is in Hebrew.
    When I switched to English interface of SBO, then the PDF file name is in English and the file is received correct (As PDF file).
    Another thing is that when you send the e-mail via the SBO (with the attached PDF) and open it
    on outlook (e.g. 2007), the file is received as DAT file,
    However If you open the e-mail on web mail (e.g. GMAIL), the file is received as correct PDF file, But when you send a regular e-mail (not via the SBO) with the attached PDF file and open it on outlook, the file is received As PDF file.
    Thanks,
    Erez

    I am afraid that there is a syntax or some codes in the interface that make the pdf converted into DAT file. You should ask the technical consultant or someone that developed the interface to make sure about it.
    If not, probably,  there is a problem with your current SAP B1 version. You could try to upgrade to the latest PL version of your current B1 application and then try again this case. if this is happened in the latest version, log a message to SAP Support.
    JimM

  • When I send out mail from MS Outlook enterprise account in the office to my Mac at home they are received as "winmail.dat" files.  Even if I perform a "save as" to the correct file name the file format is still not recognized.  Why is this happening!?

    When I send out mail from MS Outlook enterprise account in the office to my Mac at home they are received as "winmail.dat" files.  Even if I perform a "save as" to the correct file name the file format is still not recognized.  Why is this happening!?

    http://www.joshjacob.com/mac-development/tnef.php

  • I am having problems interacting with Microsoft Office programs since the last update:cannot create a pdf through the 'print' menu in exel and both Word and Exel docs sent in Mac Mail end up being received as .dat files.

    I am having problems interacting with Microsoft Office programs since the last update:cannot create a pdf through the 'print' menu in exel and both Word and Exel docs sent in Mac Mail end up being received as .dat files.
    Both these situations have cropped up on my MacBook Pro since the last update.
    Thanks for your help.
    Cheers
    Bob

    The 'Winmail.dat' problem has been extensively covered in these forums, I would search for that (a Google search works well) and unfortunately I have not seen the pdf print problem before, but assuming the software is current and functions normally (other than the pdf print problem) I have no suggestion other than the obvious (but time consuming) re-installation of Office.
    I wish I had more

  • Mail Adapter : Receiving a Dat file

    Hi,
    I am sending an error message to MAIL adapter during a IDOC->XI<->HTTP Receive.
    I am getting the error message to my email id in the form of .DAT file(an attachment)
    The "Keep Attachments" is unchecked.
    Why is that i am not able to get this within the body of the email?
    Thanks,
    Tirumal

    hi,
    These blogs help me send an email with attachments which i do not want.
    I am getting the message in .DAT file which i have to open in an editor but i want the contents to be the body of the email.
    e.g.
    <email_text>
         <id>123</id>
         <name>123Test</name>
         <datesent>06/06/06</datesent>
    </email_text>
    I need to see the contents of the email as <id>, <name> and <datesent> in the body.
    I am on SP16.
    Thanks again,
    Tirumal

  • How do you convert win mail.dat files back to MS office files?

    Microsoft files (e.g. excel) when forwarded as attachments and received by MacBook Winmail, get converted to winmail.dat files.  However, MS Office products cannot open these winmail.dat files.  Does anyone have a solution for this "bug"?

    The fault lies with Microsoft Outlook, the email client you are using on your PC. 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.
    The data in a winmail.dat file is not usable (without conversion see below). To resolve this issue within Outlook, send the messages in plain text format.  You can change the format of the email messages that you send from Outlook 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.
    Did I mention that I detest Outlook. It's not your fault. The gentlemen idiots at Microsoft make the egregious assumption that all your recipients all use Outlook, and don't adequately inform users that they have to change settings to communicate with the rest of the world.
    You can also use TNEF "enough" (which is easier than getting your senders to behave LOL)
    http://www.macupdate.com/app/mac/12705/tnefs-enough

  • Opening Winmail.dat files in Mail on iPad (Ms Windows Word, Excel, Ppt)

    I thought I'd share my findings on what to do if your Word, Excel, Powerpoint attachments come into your Mail as winmail.dat files. In my experience I downloaded the following Apps:
      Pages
      Numbers
      DocsToGo
    WinMailViewer
      Letter Opener
    To open the winmail.dat file hold the icon until asked how you want to open the file: WinMailViewer or Letter Opener (assuming you've previously downloaded both Apps).
    WinMailViewer is exactly what it says ... a 'viewer' of the file.  The file is sent to the relevant App which you subsequently open to see a list of the files.
    Letter Opener will bring up the attachment(s) in a separate window and gives you choices on which App you'd like to use to open or view the file with. Depending on what Apps you've previously downloaded:
      For Excel it might list: Quick Look, DocsToGo, Csv File Editor, PDFReaderLite
      For Word, it might list: Pages, DocsToGo, PDFReaderLite
    DocsToGo is an excellent option for working on Word, Excel files (N.B. If you have a big Excel file with 'frozen' window panes, I recommend clicking on the 4th tool (bottom toolbar) UnFreezing the panes while you work or move around the file as I haven't figured how to work with it on!!)
    Pages is the best option to use for editing Word files.
    Numbers is probably the best option to use for editing Excel files.
    Csv File Editor is another Excel editing option.
    I hope that helps.

    I should further say the files I sent are .xlsx and .docx files.  They look fine my end and I send such files all the time without problems.
    However, I did try to cheat by going in via the Safari onto my 'live' online email account and the Safari automatically transfers them to winmail.dat files with the same result.
    Ahh - have just been on using my PC this time and you are right, it seems that the service provider does the transfer and then when my outlook opens the file (on the PC), it must reconvert to .xlsx etc again.
    Very strange.
    Ergo, I guess the question should be how I open wimail.dat files ??

  • 10.4.9 update 'deletes' mail, bookmarks, data files

    My programs work fine, EXCEPT all the data files are missing:
    Entourage calendar and e mail
    Safari bookmarks
    I Tunes music library
    Voodoo Pad pages
    I've repaired the permissions. The Entourage database is 4.7MB, I just can't access it.

    Repairing permissions has no effect on items in your home folder.
    Do you get any error messages when you try accessing any of those items?

  • I have an iPad 1. Using e-mail why do all my received attachments end up as winmail.dat files?

    I have an iPad 1. Using e-mail why do all my received attachments end up as winmail.dat files?

    http://support.apple.com/kb/TS1506
     Cheers, Tom

  • How to secure e-mailed data file

    Is there a way when a user clicks on Submit via E-Mail a completed form that the data file that is being e-mailed to me can be encrypted....or in the alternative is there a way to set a default password to secure the data file which I would then have to use to open the data file?
    I don't want users to have to purchase Digital IDs, etc. to secure the data file that's being e-mailed to me--I'm looking at a simpler solution for the end user.
    Thanks,
    Steve

    When a PDF form, or an HTML (web page) form is submitted, it is sent
    to a web server. On the server, a web programmer has made a script to
    deal with the received information: store it, e-mail it, throw it
    away...
    Submitting to an http server isn't secure, but a secure server running
    https is secure. Of course, the server must not e-mail what it
    receives, but should have a protected script for access. A security
    expert should be involved to make sure the interests of the end user
    and legal privacy requirements are properly observed.
    Aandi Inston

  • Is Lion, Mail now able to handle .DAT files?

    Tonight I had to purchase third party software to allow me to read the content of .DAT files  created but Microsoft Outlook
    I just wonder if anyone knows if the new Mail application in Lion can now decipher .DAT files ?
    Would be nice if I would not need a third party plug in to Mail.

    Unfortunately, no, the SHTML plugin for iWS (as of 4.1 SP9 and 6.0 SP2) does not support arbitrary MIME content types.

  • I cannot open a wind mail.dat file. Any software recommendation?

    I cannot open a "windmail.dat" file. Any software recommendation.

    Try:
    How do I open winmail.dat files?

Maybe you are looking for