Webdav in Mountain Lion

Hey all,
I've been attempting to setup Webdav in Mountain Lion but am not sure if I'm doingit right. Basically, I have setup our OS X server on our existing Windows network. I've configured Profile Manager which works fine (apart from some odd DNS issues on iPads but that's for another day). I'm now trying to get Webdav going but with limited success. Here's what I've done so far.
Created a new user in the Server App to test with (local network user).
Turned on the wiki and websites service and ticked the 'Enable WebDav access to Wiki files'. Not sure if this is needed but if it's disabled servername/webdav doesn't even prompt me for a username and password.
Connected to 'servername' on an iPad which brings up the server page with 'Documents, Wiki' and all that jazz.
Hit the login button and type the credentials of the afforementioned user I created.
iPad pauses for 10 seconds then goes back to the server page, still says I'm an unauthenticated user and I can't access anything.
Chances are I'm doing something wrong here as this is the first time I'v set this up. I've had a quick search but can't find anything yet.
If anyone has any advice I'd be very grateful.
Many Thanks
Pete

After more searching I went to check /etc/apache2/httpd_webdavsharing_sharepoints.conf. but noticed this file does not exist! Methinks I haven't configured this properly. If anyone has any tips I'd be grateful :-)

Similar Messages

  • When i browse OS X Server (Mountain Lion) Wiki through webdav i can't open any files and they all are 4kb in size?!

    When i browse OS X Server (Mountain Lion) Wiki through webdav i can't open any files and they all are 4kb in size?!
    Why is this ... is my configuration wrong in some way? I just put a tick mark in the

    They seem to open fine from Numbers and Pages on the iPad.
    This only happens on OS X macbook pro when i "Connect to server" from Finder.

  • Issue Mountain Lion accessing WebDAV

    Dear beekeepers,
    looks as if there might be an issue of Mountain Lion accessing beehive over WebDAV.
    This [post |https://discussions.apple.com/thread/4139087?start=0&tstart=0] sounds very similar.
    The post is talking about inserting a directive
    BrowserMatch "^WebDAVFS/2.0" redirect-carefully
    into the WebDAV configuriation, but I don't think this can be easily done in Beehive.
    Anyone seen this issue in his/her installation?
    Regards, Tom

    a user of OS X 10.8.4 reports the following picture when trying
    to access beehive 2.0.1.7 TWS through WebDAV:
    Mac OS X "native", cadaver and Cyberduck do not work. He doesn't
    even get to the password prompt.
    Cadaver reports "SSL handshake failed"
    ForkLift works without problems, and Safari, Firefox and Chrome
    can access Zimbra without an issue (so the SSL handshake works
    there).
    Seems as if newer versions of OS X face more than the zero-bytes
    issue when accessing beehive WebDAV.
    Please share your own experiences with OS X and WebDAV.
    Thanks, Tom

  • Server App can't connect to a Mountain Lion server

    Hi,
    I installed OS X Mountain Lion Server (2.2.1) on a 2012 Mac Mini running OS X 10.8.4. I am able to access all the options using the Server.app on the Mini. Then I installed the Server.app (2.2.1) on a 2010 MacBook Pro running 10.8.4. On trying to configure the Server options on the Mac Mini from the MacBook Pro by providing the correct Mac Mini admin credentials, the password is not validated correctly. This happens when both the systems are on the same network or on different networks.
    I am certain that the username / password provided is correct, since using the same credentials I can successfully remote into the Mac Mini using Apple Remote Desktop (3.6.1) when both the systems are on the same network or on different networks.
    My situation supersedes the resolution provided in http://support.apple.com/kb/TS3960?locale=en_US. Note that the command sudo launchctl list | grep -q com.apple.servermgrd && echo loaded || echo not loaded returns loaded on the Mac Mini.
    Please help!

    I am having exactly the same setup and exactly the same problem - nevertheless I would like to add some more information in order to hopefully find / get help from other readers in here.
    I am using DynDNS - not a dedicated domain. I do not utilize an AirPort Extreme for port forwarding and else. All the necessary port forwardings were triple checked!
    - First of all "Apple Remote Desktop" is able to connect to my server over the internet (screen sharing) and locally in my LAN. No troubles here.
    - My iOS devices can connect using various VNC clients without any troubles.
    - VNC connections started within Safari (MacBook Pro) do work very well, too.
    - All kinds of WebDAV connections are working like a charme.
    - When connecting with "Server.app" from my MacBook Pro it asks if I would like to trust the self-signed certificate before I can enter name and password. After trusting that certificate it doesn't matter which account information I am entering: none is accepted. It does not make any difference if I am using a local user account or a user network account (both configured as being allowed to administer that server). "Server.app" does not accept any information provided.
    I've been following the KB advice, too that c xavier mentioned. "servermgrd" is loaded!
    For some odd yet unknown reason neither WAN nor LAN FTP login does work, too. It just gives me a time out, as already mentioned WebDAV is working fine.
    Sorry I could not help You, c xavier! I just thought that some additional information could help...

  • Mountain Lion Server - Folder names intermittently change between Upper and Lowercase names on some user's iMacs

    Hi,
    Sorry if I'm posting in the wrong group, but I couldn't find a Mountain Lion server specific group.
    I have a new Mac Mini Server running 10.5.8 that serves Mac only users. The Mac Mini has a 4tb Promise Pegasus RAID attached via thunderbolt. Today, some of the users on the network reported that a folder on the RAID was quickly alternating displaying it's sub-folders as all capital letters then upper and lowercase - I witnessed this and it happened 2-3 times a second. I have run a propogate permissions fix on the folder, then the whole volume from within Server App and also copied the contents of this folder to my Mac, then I deleted the original from the server and created a brand new folder with the correct name and copied the contents back.
    The problem still persists. Server App does not report any issues and other folders don't exhibit this behaviour. I've looked to see if there are any weird characters in folder names that would do this. The volume is shared via AFP only (SMB and WEBdav are off).
    Any ideas as to what could be going on?
    Thanks in advance!

    Hi.
    I solved this problem. I fixed permissions on the Mac's that the users were using to access the server and this has fixed the problem. The server folder giving the problems had many nested folders totalling over 5000 items inside and this seemed to corrupt the permissions on the user's macs.
    Hope this helps anyone with similar issues.

  • Password problem after migrating to Mountain Lion Server

    Hello everyone,
    Yesterday, I migrated our Lion Server to Mountain Lion Server. Everything seemed to work fine. Except since this morning, none of the network user cannot connect to their calendar, reminders, and wiki. They can connect to their account and to their mails. The following line appears multiple times in ApplePasswordServer.Error.log:
    Aug 16 2012 16:52:50 700250us    client response doesn't match what we generated
    It seems that only web services are concerned (vpn, mobile accounts, and mails are working). My initial guess is that the hash computed on the basis of the user password is not computed on the same way on the client machine (which is running Mountain Lion by the way) and on the server. On the other hand, this would be very surprising, since all this stuff is based on standards and unlikely to have changed since Lion.
    I tried to create a new "Test" user. Even this new user, created after the migration, cannot connect to its calendar, etc. I also tried to reset my user password using the Server App. It makes no difference, the same lines appear in the logs.
    Is anyone experiencing a similar problem ? Does anyone have a clue of what to try next ?
    Thanks a lot !

    I found out the following:
    After looking at the contents of the password server database using the slot numbers of several user accounts, it seems that all users where WEBDAV-DIGEST authentication is failing, have two entries for the digest method "*cmusaslsecretDIGEST". This is obviously wrong. All users who can authenticate successfully have only one such entry.
    Deleting and recreating the user account has no effect. In fact, updating the password server with a new entry may actually trigger this error. It could be that all users where this is failing have changed their passwords after the server was updated to Mountain Lion.
    It would be interesting to know if you also see duplicate entries for "*cmusaslsecretDIGEST" in the database. You can display a password server record via the user account's slot number (in your example, the 0xd6ace...) using the command
    sudo mkpassdb -dump <slot-number>
    At the end of the record dump, you should see 10 digest entries with their method identifiers.

  • Mountain Lion slow network

    We recently started using Mountain Lion at work, installed it fresh on a formatted server and we're having some terrible problems with the network. We have reinstalled twice and the problem persists;
    Its running terribly slow on the local network. Downloading a small (~2MB) PDF is taking around 30 - 60 seconds. Internet is running fine, downloading goes at a realistic speed, on both the server and the machines we are trying to connect locally.
    The server is connected via ethernet, the other machines we have connected via ethernet and WiFi with no difference. Everything is running slow, Wiki Server, Profile Manager, WebDAV, etc.. Initially we thought it was due to the server memory, as it was running around 90% usage, but after upgrading it we're still having the same issues. A lion server in the exact same situation works fine.
    Any advice would be appreciated.

    Here are the netstat results.
    tcp:
              5131921 packets sent
                        3586548 data packets (2802548362 bytes)
                        20066 data packets (30331998 bytes) retransmitted
                        0 resends initiated by MTU discovery
                        1331930 ack-only packets (752 delayed)
                        0 URG only packets
                        16 window probe packets
                        61026 window update packets
                        133333 control packets
                        0 data packets sent after flow control
              4844274 packets received
                        2781491 acks (for 2785694807 bytes)
                        293105 duplicate acks
                        0 acks for unsent data
                        1633476 packets (20872370 bytes) received in-sequence
                        38414 completely duplicate packets (134623 bytes)
                        1 old duplicate packet
                        12 packets with some dup. data (4093 bytes duped)
                        1692 out-of-order packets (2322772 bytes)
                        16 packets (16 bytes) of data after window
                        16 window probes
                        73943 window update packets
                        20428 packets received after close
                        1 bad reset
                        0 discarded for bad checksums
                        0 discarded for bad header offset fields
                        0 discarded because packet too short
              53153 connection requests
              49928 connection accepts
              5221 bad connection attempts
              617 listen queue overflows
              96449 connections established (including accepts)
              103163 connections closed (including 15261 drops)
                        1723 connections updated cached RTT on close
                        1723 connections updated cached RTT variance on close
                        524 connections updated cached ssthresh on close
              6153 embryonic connections dropped
              2781238 segments updated rtt (of 2039724 attempts)
              2029 retransmit timeouts
                        46 connections dropped by rexmit timeout
                        0 connections dropped after retransmitting FIN
              18 persist timeouts
                        0 connections dropped by persist timeout
              5084 keepalive timeouts
                        0 keepalive probes sent
                        29 connections dropped by keepalive
              244119 correct ACK header predictions
              1546225 correct data packet header predictions
              2696 SACK recovery episodes
              17545 segment rexmits in SACK recovery episodes
              24059497 byte rexmits in SACK recovery episodes
              138780 SACK options (SACK blocks) received
              1600 SACK options (SACK blocks) sent
              0 SACK scoreboard overflow
    udp:
              724172 datagrams received
              0 with incomplete header
              0 with bad data length field
              0 with bad checksum
              23199 dropped due to no socket
              4747 broadcast/multicast datagrams dropped due to no socket
              1 dropped due to full socket buffers
              0 not for hashed pcb
              696225 delivered
              719607 datagrams output
    ip:
              3118895 total packets received
              0 bad header checksums
              0 with size smaller than minimum
              0 with data size < data length
              0 with ip length > max ip packet size
              0 with header length < data size
              0 with data length < header length
              0 with bad options
              0 with incorrect version number
              0 fragments received
              0 fragments dropped (dup or out of space)
              0 fragments dropped after timeout
              0 packets reassembled ok
              3109539 packets for this host
              1679 packets for unknown/unsupported protocol
              0 packets forwarded (0 packets fast forwarded)
              7057 packets not forwardable
              527 packets received for unknown multicast group
              0 redirects sent
              2959671 packets sent from this host
              0 packets sent with fabricated ip header
              0 output packets dropped due to no bufs, etc.
              1039 output packets discarded due to no route
              0 output datagrams fragmented
              0 fragments created
              0 datagrams that can't be fragmented
              0 tunneling packets that can't find gif
              0 datagrams with bad address in header
              0 packets dropped due to no bufs for control data
    icmp:
              23292 calls to icmp_error
              0 errors not generated 'cuz old message was icmp
              Output histogram:
                        echo reply: 576
                        destination unreachable: 23292
              0 messages with bad code fields
              0 messages < minimum length
              0 bad checksums
              0 messages with bad length
              0 multicast echo requests ignored
              0 multicast timestamp requests ignored
              Input histogram:
                        destination unreachable: 1672
                        echo: 576
              576 message responses generated
              ICMP address mask responses are disabled
    igmp:
              7 messages received
              0 messages received with too few bytes
              0 messages received with wrong TTL
              0 messages received with bad checksum
              0 V1/V2 membership queries received
              0 V3 membership queries received
              0 membership queries received with invalid field(s)
              0 general queries received
              0 group queries received
              0 group-source queries received
              0 group-source queries dropped
              7 membership reports received
              0 membership reports received with invalid field(s)
              7 membership reports received for groups to which we belong
              0 V3 reports received without Router Alert
              8 membership reports sent
    ipsec:
              0 inbound packets processed successfully
              0 inbound packets violated process security policy
              0 inbound packets with no SA available
              0 invalid inbound packets
              0 inbound packets failed due to insufficient memory
              0 inbound packets failed getting SPI
              0 inbound packets failed on AH replay check
              0 inbound packets failed on ESP replay check
              0 inbound packets considered authentic
              0 inbound packets failed on authentication
              0 outbound packets processed successfully
              0 outbound packets violated process security policy
              0 outbound packets with no SA available
              0 invalid outbound packets
              0 outbound packets failed due to insufficient memory
              0 outbound packets with no route
    ip6:
              2460980 total packets received
              0 with size smaller than minimum
              0 with data size < data length
              0 with bad options
              0 with incorrect version number
              39 fragments received
              0 fragments dropped (dup or out of space)
              1 fragment dropped after timeout
              0 fragments that exceeded limit
              19 packets reassembled ok
              2459520 packets for this host
              0 packets forwarded
              890 packets not forwardable
              0 redirects sent
              2955232 packets sent from this host
              0 packets sent with fabricated ip header
              0 output packets dropped due to no bufs, etc.
              5328 output packets discarded due to no route
              64 output datagrams fragmented
              128 fragments created
              0 datagrams that can't be fragmented
              0 packets that violated scope rules
              890 multicast packets which we don't join
              Input histogram:
                        hop by hop: 55
                        TCP: 1861327
                        UDP: 598808
                        fragment: 39
                        ICMP6: 695
              Mbuf statistics:
                        1015622 one mbuf
                        two or more mbuf:
                                  lo0= 1421891
                        23465 one ext mbuf
                        0 two or more ext mbuf
              0 packets whose headers are not continuous
              0 tunneling packets that can't find gif
              0 packets discarded due to too may headers
              0 failures of source address selection
              0 forward cache hit
              0 forward cache miss
              0 packets dropped due to no bufs for control data
    icmp6:
              1 call to icmp_error
              0 errors not generated because old message was icmp error or so
              0 errors not generated because rate limitation
              Output histogram:
                        router solicitation: 19
                        neighbor solicitation: 47
                        neighbor advertisement: 45
                        MLDv2 listener report: 31
              0 messages with bad code fields
              0 messages < minimum length
              0 bad checksums
              0 messages with bad length
              Input histogram:
                        neighbor solicitation: 46
                        neighbor advertisement: 464
              Histogram of error messages to be generated:
                        0 no route
                        0 administratively prohibited
                        0 beyond scope
                        0 address unreachable
                        0 port unreachable
                        0 packet too big
                        0 time exceed transit
                        1 time exceed reassembly
                        0 erroneous header field
                        0 unrecognized next header
                        0 unrecognized option
                        0 redirect
                        0 unknown
              0 message responses generated
              0 messages with too many ND options
              0 messages with bad ND options
              0 bad neighbor solicitation messages
              0 bad neighbor advertisement messages
              0 bad router solicitation messages
              0 bad router advertisement messages
              0 bad redirect messages
              0 path MTU changes
    ipsec6:
              0 inbound packets processed successfully
              0 inbound packets violated process security policy
              0 inbound packets with no SA available
              0 invalid inbound packets
              0 inbound packets failed due to insufficient memory
              0 inbound packets failed getting SPI
              0 inbound packets failed on AH replay check
              0 inbound packets failed on ESP replay check
              0 inbound packets considered authentic
              0 inbound packets failed on authentication
              0 outbound packets processed successfully
              0 outbound packets violated process security policy
              0 outbound packets with no SA available
              0 invalid outbound packets
              0 outbound packets failed due to insufficient memory
              0 outbound packets with no route
    rip6:
              0 messages received
              0 checksum calcurations on inbound
              0 messages with bad checksum
              0 messages dropped due to no socket
              0 multicast messages dropped due to no socket
              0 messages dropped due to full socket buffers
              0 delivered
              0 datagrams output
    pfkey:
              6 requests sent to userland
              304 bytes sent to userland
              histogram by message type:
                        register: 3
                        x_spdadd: 2
                        x_spddump: 1
              0 messages with invalid length field
              0 messages with invalid version field
              0 messages with invalid message type field
              0 messages too short
              0 messages with memory allocation failure
              0 messages with duplicate extension
              0 messages with invalid extension type
              0 messages with invalid sa type
              0 messages with invalid address extension
              7 requests sent from userland
              800 bytes sent from userland
              histogram by message type:
                        register: 3
                        x_spdadd: 2
                        x_spddump: 2
              0 messages toward single socket
              0 messages toward all sockets
              0 messages toward registered sockets
              0 messages with memory allocation failure
    Activity monitor is looking fine. Safari Web Content jumps up if we accidently leave Safari running, other than that nothing is even high.

  • How can I connect my Early 2011" Macbook Pro 13" inch, with a generic Mini Display Port to HDMI connector, to a LG 32LD340 LCD TV, using Mountain Lion 10.8.2?

    I have an Early 2011" macbook pro 13 inch (core i5 2.3ghz 4gb ram 320hdd) with Mountain Lion 10.8.2, and I want to connect it via Mini DP to HDMI connector, and a HDMI cable to a LCD TV LG 32LD340. When I had Lion OS, I had no problems at all.

    If you have an external drive equal to or larger than your internal HD, clone your internal to it with either Carbon Copy Cloner or Super Duper. Test the clone to make sure it's bootable. Then upgrade either one. Try it out first.

  • TS3147 After installing Mountain Lion, I tried to scan from my Canon MX870 and received the message: "MP Navigator EX quit unexpectedly. Click Reopen to open the application again. A report will be sent to Apple,"

    After installing Mountain Lion, I tried to scan from my Canon MX870 and received the message: "MP Navigator EX quit unexpectedly. Click Reopen to open the application again. A report will be sent to Apple,"  This problem happened right after I installed Mountain Lion. I then downloaded Canon's upgraded software and drivers for the MX 870 and the problem was resolved. Now one month later, the problem has returned.

    rjliii wrote:
    Solved problem with original Canon software.  When I downloaded Canon software upgraded for OS X 10.8, I got all by Navigator Ex. Noticed that on Canon's site, the upgraded version is 3.1; my app was 2.1. Upgraded to 3.1 for Nav. Ex, and it works.
    You should still use Image Capture IMHO.  If it was my gear, that's what I would do.  No need to worry about software upgrades.

  • Cannot see my G5 server after upgrading to Mountain Lion.  Help!

    Hi everyone!
    I upgraded to Mountain Lion on my MBP and now my G5 Power PC that I have as a Media Server with all my iTunes movies and music is no longer visible!!  Really frustrating because there is a LOT on there.  It worked fine with Lion!  Am I going to have to downgrade to keep it working?
    Please advise.
    I have an iMac which is running Lion and it sees it fine.  Apple TV sees it too.  Not a connectivity issue.

    can it be something related to wi-fi?  I have read other posts talking about loss of connection using wifi.  I'm connecting my G5 through an airport express which is expanding my wifi generated from my Apple Time Capsule. It is quite difficult for me to relocate the server close to the Time Capsule and vice versa but if it works, at least that would be something.  It was working with Lion about 3 months ago - showing up in Finder, etc.

  • IPhoto update impossible after upgrading to Mountain Lion?

    I upgraded from Snow Leopard to Mountain Lion today and when I subsequently went into the iCloud settings I was surprised to learn my version (9.1.3) of iPhoto was not capable of supporting iCloud. The information stated if iPhoto had not been installed from the App Store, then one should go the the apple icon in the top left corner and select "Software Update" from there. When I do that, it is reported I do not have an update available. However, if I open iPhoto and check for an update from its menu, it indicates an update (two, actually) is available but when I click the "Open Software Update" button, I am directed back to the App Store where...no update available is the information provided.
    I would really like to use iCloud Photo Stream and is one of the reasons I ponied up $20 to "upgrade" to Mountain Lion. Could someone tell me what I am doing wrong? I have been a MS/Windows user for 20+ years and this initial exposure to difficulties with the Mac OS is not what I expected.
    Thanks.

    Please read this whole message before doing anything. This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it. The purpose of this test is to determine whether your problem is caused by third-party system modifications that load automatically at startup or login. Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows: 
    Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
    When you see the gray Apple logo, release the shift key.
    If you are prompted to log in, type your password, and then hold down the shift key again as you click  Log in.
     *Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode. Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs. The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Try the download while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

  • Thinking about upgrading to Mountain Lion. Family members use different devices, but all on one apple account.

    Will we be able to view our individual facebook accounts on our individual devices, all have our individual games with Mountain Lion or will it automatically synchronise to the same thing? If so, what do we need to do to separate our devices? Would we have to purchase separate Mountain Lions for each device if we did separate them?

    Will we be able to view our individual facebook accounts on our individual devices, all have our individual games with Mountain Lion or will it automatically synchronise to the same thing? If so, what do we need to do to separate our devices? Would we have to purchase separate Mountain Lions for each device if we did separate them?

  • I downloaded mountain lion and then the new office suite (word, ppt, excel) but now when I try to display one of my ppt's it says 'ppt cannot open the file...the file may be corrupt, in use, not a type recognized by ppt etc.." how can I fix it?? HELP

    I downloaded mountain lion and then the new office suite (word, ppt, excel) but now when I try to display one of my ppt's it says 'ppt cannot open the file...the file may be corrupt, in use, not a type recognized by ppt etc.." how can I fix it?? HELP

    Did you try to open teh fle by double-clicking its icon? If the file was made with an older version of Office, you may get that message. Try opeing PP and, from its "File" menu, see if you can open the ppt. I've foundthat often gets around that message and then yo ucan save the file from the newer version.
    If that doesn't work, consider asking in the Microsoft Office: Mac forums here:
    Office for Mac forums
    PowerPoint is not an Apple product and it seems a lot of people around here avoid Office.

  • How do you stop Mountain Lion from making endless copies and backups of everything?!

    I already have a similar topic on this when I needed to figure out how to stop Mountain Lion from making endless copies of my text edit files and I was going to try the disabling of it that someone in that thread suggested, but I can't find where the Versions backups are being stored.
    Anyway, tonight I cam across a new problem, when I went into "about this Mac" and looked at my Storage, I had almost 1gb of data in the "backups" section. I just happened to have Finder open when I went into the Time Machine in the status bar and when it entered Time Machine, I had dozens of copies of my desktop. Thing is, I don't have my Time Machine hard drive connected and I don't have a Time Capsule router/hard drive. And don't give me this garbage about how "It's not real backups, it's just a snapshot" or whatever, because the ONLY things that I have stored on my computer that I have altered since I got mountain lion is two Text Edit files and the Finder Desktop (and yes, I have checked almost all the programs I use, and of the things that Time Machine will open in, those are the only things that have backups listed that I can access) and almost 1gb is being taken up completely needlessly with the computer backing up things onto itself. Obviously these are more than just snapshots and are obviously the real files because after throwing EVERYTHING on my desktop into a file, that file is only 3.8mb in size, so that almost 1GB in backups is coming from SOMEWHERE.
    The solution I aluded to in my first sentence also depends on going into the Terminal to make each individual app stop auto saving Versions, however, since my desktop is being backed up, there's no program to stop Mountain Lion from doing that.
    Can anyone help me figure out how to make it stop backing up? Seriously, almost 1 gb is being totally wasted on a series of desktop items that are 3.8mb in size, one Text Edit file that is 250kb in size, and another text edit file that is 41kb in size. What person in Apple would possibly have thought this endless backing up of files onto the main hard drive would have been a good idea? So in a year if I did nothing but go on the internet, save one picture to one file on my desktop and did nothing else with my computer, would I have 200 gb of desktop backups that the computer saved onto itself? Are you kidding me? OR failing that, can anyone tell me how to find this damned backup file and delete it? I'm not an idiot, I know how to plug in a hard drive or flash drive and backup my information, I don't need my computer to be making hundreds of copies of every single file on my computer that I change slightly onto itself that not only needlessly eats up it's own space, but if the hard drive died, all those "backups" would be gone too because it wrote the backups to itself.
    I am so frustrated by this totally ridiculous and wasteful "feature" they put in, it does nothing but waste hard drive space with it's hundreds of copies of everything you alter slightly. And I am absolutely not starting any video editing projects until I figure out how to turn this off. If around 4mb of total text and desktop backups add up to almost 1gb in a few weeks, what the heck is a video editing project going to end up in with size? Am I the only one completely flustered by this ridiculousness? Is there any point in writing into Apple to complain or are they just going to say "No, we're brilliant, we think this is an amazing feature so you just have to deal iwth it and when your hardd drive fills up, too bad, jerk!"?? Help! Thanks!

    Well as I pointed out in my post, "Sadly, my Text Edit documents are still all there, every single time I opened them and made a small change, there is another copy stretching all the way back to the day I installed Mountain Lion." so if you can explain to me how July 26 - Aug 16 is a week, I will concede that it is a good idea. Short of that, no I have been capable of making my own backups since I was 16 years old (16 years ago) I don't need my computer to endlessly do it for me in a way I am completely unable to shut off. That's what I have external hard drives, flash drives, a DVD burner, Drop Box, E-mail (as in emailing copies to myself) and icloud for. If I am doing something and I don't have access to a single one of those options, I don't know why I brought my computer with me in the first place. And I don't see how you can say it's an illusory gain in disk space, hundreds of copies of text documents, garageband files, Final Cut files, Motion Files and basically any program that makes files onto my comptuer that I can myself make incremental changes to, those all need to be stored somehow. Again, if you can explain to me how July 26 - Aug 16 is a week, I will agree with you that that is a good thing because IF it only saved for a week, it wouldn't be an issue. Sadly, no matter how many links you post, I still have text edit backups stretching from today back to July 26. They're not going away and I have no reason to beleive any other file I edit is going to go away either since they haven't been. They're all there eating up HD space and this imaginary "week" limit is simply not coming into effect. I hate it and there needs to be a simple way to simply shut it off. I didn't spend hundreds of dollars on external drives just for my main hard drive to be filled up with hundreds un useless, undeletable backups of stuff I already have backed up.

  • Emails from one account don't appear in the Inbox of Mail since upgrading to Mountain Lion

    I have a couple of email accounts - one is Gmail and one is a domain for my business. Previously Mail would show the Inbox and then a subfolder for each account under Inbox. Any messages received in the accounts would appear in both their own subfolder and also the Inbox. All my rules worked properly and life was good. Now, try as I might I cannot get my domain email account messages to show in the global/unified Inbox.
    Originally the domain email folder was totally separate to the Inbox. By changing the IMAP Prefix (removing 'Inbox') I was able to get the folder at least under Inbox.
    I purchased a new iMac and used Migration Assistant to move everything, therefore the problem persists. I had additional problems that my address book, rules and On My Mac folders didn't appear - but I solved that by finding the Containers folder and it is like a duplicate of Mail. I moved things from there to the Library/Mail and those particular issues resolved. But for the inbox issue, I have removed data from the Users/Library/Mail and from Library/Containers and started afresh - even deleted the Mail App and reinstalled from my original disc, but as soon as I set up the account it happens again.
    Recently I have also started receiving errors when sending to use the Connection Doctor. I don't know if all this is related to a bug in Mountain Lion, the way I have things set up, or my domain/ISP.
    Any suggestions on what to try, what it may be or ways around it would be great. I do have a Smart Mailbox for a Total Inbox, but of course the Rules don't work automatically on it. I'm getting sick of running Rules manually. Help please!!

    I called the support service and she told me to delete my email address and re-enter it. I have no problem since then on receiving and sending emails.

Maybe you are looking for