Helga

Q: Mail not sending in El Capitan on MacBook Pro

Ok, here it goes:

MacBookPro early 2011, El Capitan 10.11.2, however this started when she was still on Yosemite and I was hoping El Capitan would fix it.

 

I have tried all suggestions I have read so far.  My sister can get mail, however she cannot send any. (iCloud on the web works fine!)  I have logged out of iCloud, restarted the computer and logged back in.  No change.

 

I have her account on my MBP and all works fine.  I have checked all her settings and they match exactly.

 

I am thinking that some preference is corrupted, but I can't find one that seems to related to mail, other than some "mail shared.plist".  When I look in my "Mail folder in my library under MailData I cannot find anything that remotely seems to have anything to do with the SMPT server.

 

 

 

I am at a complete loss, and would appreciate any assistance anybody can provide.

 

Helga

MacBook Pro (15-inch Early 2011), OS X El Capitan (10.11.2)

Posted on Dec 28, 2015 12:33 PM

Close

Q: Mail not sending in El Capitan on MacBook Pro

  • All replies
  • Helpful answers

Previous Page 2
  • by Linc Davis,

    Linc Davis Linc Davis Jan 1, 2016 3:52 PM in response to Helga
    Level 10 (207,995 points)
    Applications
    Jan 1, 2016 3:52 PM in response to Helga

    The log extract that you posted on Dec. 30 showed that Mail was trying to connect to the server on port 465, which is not the right port. If you followed my last set of instructions, then it should now be connecting to port 587. Is that happening?

  • by Helga,

    Helga Helga Jan 2, 2016 11:51 AM in response to Linc Davis
    Level 2 (296 points)
    Apple TV
    Jan 2, 2016 11:51 AM in response to Linc Davis

    The port is definitely assigned 587 I just checked it again.

     

    Helga

  • by Linc Davis,

    Linc Davis Linc Davis Jan 2, 2016 3:42 PM in response to Helga
    Level 10 (207,995 points)
    Applications
    Jan 2, 2016 3:42 PM in response to Helga

    Please triple-click the word "telnet" in the line below on this page to select the whole line:

    telnet p10-smtp.mail.me.com 587

    Copy the selected text to the Clipboard by pressing the key combination command-C.

    Launch the built-in Terminal application in any one of the following ways:

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad and start typing the name.

    Paste into the Terminal window by pressing command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.

    You should almost instantly get three or more lines of output below what you entered, one of which is this:

    Escape character is '^]'.

    If there's no output within ten seconds, consider that a failure. If you get something different from the above, please post it in a reply. You can then quit Terminal.

  • by Helga,

    Helga Helga Jan 2, 2016 4:22 PM in response to Linc Davis
    Level 2 (296 points)
    Apple TV
    Jan 2, 2016 4:22 PM in response to Linc Davis

    I will try it tomorrow when I get into her computer. 

     

    Thanks

     

    Helga

  • by Helga,

    Helga Helga Jan 4, 2016 12:46 PM in response to Helga
    Level 2 (296 points)
    Apple TV
    Jan 4, 2016 12:46 PM in response to Helga

    Ok, so I posted your info in terminal and got the following:

     

    Trying 17.151.224.10...

     

    then I tried it again and got:

     

    Trying 17.151.224.10...

    telnet p10-smtp.mail.me.com 587

    telnet: connect to address 17.151.224.10: Operation timed out

    telnet: Unable to connect to remote host

    Irmis-MBP:~ username$ telnet p10-smtp.mail.me.com 587

    Trying 17.151.224.10...

     

    Of course when I attempt to quit terminal (which I finally did!) I am told there are processes running.

     

    Any other ideas or thoughts to mess with?

     

    Helga

  • by Linc Davis,

    Linc Davis Linc Davis Jan 5, 2016 2:41 PM in response to Helga
    Level 10 (207,995 points)
    Applications
    Jan 5, 2016 2:41 PM in response to Helga

    1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.

    The test works on OS X 10.7 ("Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.

    Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.

    2. If you don't already have a current backup, please back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.

    There are ways to back up a computer that isn't fully functional. Ask if you need guidance.

    3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.

    You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.

    In this case, however, there are ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone with the requisite skill can verify what it does.

    You may not be able to understand the script yourself. But variations of it have been posted on this website thousands of times over a period of years. The site is hosted by Apple, which does not allow it to be used to distribute harmful software. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.

    Another indication that the test is safe can be found in this thread, and this one, for example, where the comment in which I suggested it was recommended by one of the Apple Community Specialists, as explained here.

    Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.

    4. Here's a general summary of what you need to do, if you choose to proceed:

    ☞ Copy a particular line of text to the Clipboard.

    ☞ Paste into the window of another application.

    ☞ Wait for the test to run. It usually takes a few minutes.

    ☞ Paste the results, which will have been copied automatically, back into a reply on this page.

    These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.

    5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is intermittently slow, run the test during a slowdown.

    You may have started up in safe mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual before running it. If you can only test in safe mode, do that.

    6. If you have more than one user, and only one user is affected by the problem,, and the affected user is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.

    7. Load this linked web page (on the website "Pastebin.") Press the key combination command-A to select all the text, then copy it to the Clipboard by pressing command-C.

    8. Launch the built-in Terminal application in any one of the following ways:

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad and start typing the name.

    Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.

    9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.

    If the test is taking much longer than usual to run because the computer is very slow, you might be prompted for your password a second time. The authorization that you grant by entering it expires automatically after five minutes.

    If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.

    10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:

        Test started
            Part 1 of 4 done at: … sec
            …
            Part 4 of 4 done at: … sec
        The test results are on the Clipboard.
        Please close this window.

    The intervals between parts won't be exactly equal, but they give a rough indication of progress.

    Wait for the final message "Please close this window" to appear. If you don't see it within about 15 minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it. Then go to the next step. You'll have incomplete results, but still something. If you close the Terminal window while the test is still running, the partial results won't be saved and you'll have to start over.

    11. When the test is complete, or if you stopped it because it was taking too long, quit Terminal. The results will have been saved to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.

    At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "close this window" message. Please wait for it and try again.

    If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.

    12. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the software that runs this website. Please post the test results on Pastebin, then post a link here to the page you created.

    If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

    13. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you're told to do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.

    14. The linked UNIX shell script bears a notice of copyright. Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

  • by Helga,

    Helga Helga Jan 6, 2016 10:53 AM in response to Linc Davis
    Level 2 (296 points)
    Apple TV
    Jan 6, 2016 10:53 AM in response to Linc Davis

    Hi there, I haven't run the Unix shell script yet, because I am not sure that I can do it over screensharing, but I will try it later.

     

    Also, something new cropped up.  As I said, I can send emails via the web from my sister's account.  (iCloud) However, she is having a difficult time sending emails from there also.  We tested her router and with my niece all is well and responds quickly.  With my sister, all works (FaceTime, screensharing, iMessages) except for her email, which is now stumping me even more.  Oh, there is one other thing that will not work and that is AIM video.  Don't know if all that has anything to do with anything, but I thought I mention it.  And it all started around the same time (email and AIM) while still on Yosemite.

     

    Helga

  • by Helga,

    Helga Helga Jan 15, 2016 1:57 PM in response to Helga
    Level 2 (296 points)
    Apple TV
    Jan 15, 2016 1:57 PM in response to Helga

    The Test Results are now available:

    After the Test:

    Part 1 33 sec

    Part 2 208 sec

    Part 3 534 sec

    Part 4 780 sec

     

    Test Results:

     

       1  Start time: 22:36:20 01/15/16

       2 

       3  Revision: 1424

       4 

       5  Model Identifier: MacBookPro8,1

       6  Memory: 4 GB

       7  Boot ROM Version: MBP81.0047.B2C

       8  System Version: OS X 10.11.2 (15C50)

       9  Kernel Version: Darwin 15.2.0

      10  Time since boot: 5 days 19 minutes

      11 

      12  SerialATA

      13 

      14      TOSHIBA MK5065GSXF                     

      15 

      16  Energy impact, lifetime (relative)

      17 

      18      WindowServer (UID 88): 8.00

      19      Terminal (UID 501): 6.74

      20      Pages (UID 501): 5.08

      21      bash (UID 501): 4.41

      22      VTDecoderXPCService (UID 0): 2.71

      23 

      24  CPU usage, lifetime (ms/s)

      25 

      26      WindowServer (UID 88): 70.82

      27      Terminal (UID 501): 68.55

      28      kernel_task (UID 0): 58.05

      29      Pages (UID 501): 51.53

      30      bash (UID 501): 44.13

      31      VTDecoderXPCService (UID 0): 27.09

      32      coreaudiod (UID 202): 18.79

      33      com.apple.WebKit.Networking (UID 501): 16.68

      34 

      35  CPU usage, sampled (ms/s)

      36 

      37      kernel_task (UID 0): 21.96

      38      syslogd (UID 0): 4.87

      39      identityservicesd (UID 501): 4.56

      40      WindowServer (UID 88): 3.04

      41 

      42  Listeners

      43 

      44      kdc: kerberos

      45      launchd: afpovertcp

      46      launchd: microsoft-ds

      47      launchd: ssh

      48 

      49  Diagnostic reports

      50 

      51      2015-12-28 FaceTime crash

      52      2016-01-01 cloudd crash

      53      2016-01-02 Mail crash

      54 

      55  HID errors: 1

      56 

      57  Kernel log

      58 

      59      Jan 10 22:14:08 msdosfs_fat_uninit_vol: error 6 from msdosfs_fat_cache_flush

      60      Jan 10 22:18:27 IO80211ControllerMonitor::configureSubscriptions() failed to add subscriptionIO80211Controller::start _controller is 0xfe909b780f24fd21, provider is 0xfe909b780f27de21

      61      Jan 10 22:18:27 AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized

      62      Jan 10 22:18:55 **** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOReturnNotResponding error - retrying: 1

      63      Jan 10 22:43:34 **** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOReturnNotResponding error - retrying: 1

      64      Jan 11 16:26:58 msdosfs_fat_uninit_vol: error 6 from msdosfs_fat_cache_flush

      65      Jan 11 18:21:33 **** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOReturnNotResponding error - retrying: 1

      66      Jan 11 21:49:53 **** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOReturnNotResponding error - retrying: 1

      67      Jan 13 21:11:30 **** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOReturnNotResponding error - retrying: 1

      68      Jan 14 08:34:53 **** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOReturnNotResponding error - retrying: 1

      69      Jan 14 14:40:38 Limiting closed port RST response from 358 to 250 packets per second

      70      Jan 14 18:29:52 AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized

      71      Jan 14 18:29:58 MacAuthEvent en1   Auth result for: 84:db:ac:4a:11:59 Auth request tx failed

      72      Jan 14 19:49:47 **** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOReturnNotResponding error - retrying: 1

      73      Jan 14 20:49:21 MacAuthEvent en1   Auth result for: 84:db:ac:4a:11:59 Auth timed out

      74      Jan 14 20:49:21 MacAuthEvent en1   Auth result for: 84:db:ac:4a:11:5b Auth request tx failed

      75      Jan 14 20:54:25 MacAuthEvent en1   Auth result for: 84:db:ac:4a:11:5b Auth request tx failed

      76      Jan 14 21:23:34 Limiting closed port RST response from 421 to 250 packets per second

      77      Jan 14 22:05:44 **** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOReturnNotResponding error - retrying: 1

      78      Jan 15 22:30:56 Warning: IOSurface 00000025 modified by process WindowServer using the GPU while surface is write locked by process AppleVNCServer

      79      Jan 15 22:31:43 Warning: IOSurface 00000024 modified by process WindowServer using the GPU while surface is write locked by process AppleVNCServer

      80      Jan 15 22:33:09 Warning: IOSurface 00000025 modified by process WindowServer using the GPU while surface is write locked by process AppleVNCServer

      81      Jan 15 22:34:57 Warning: IOSurface 00000025 modified by process WindowServer using the GPU while surface is write locked by process AppleVNCServer

      82      Jan 15 22:35:32 Warning: IOSurface 00000024 modified by process WindowServer using the GPU while surface is write locked by process AppleVNCServer

      83      Jan 15 22:36:02 Warning: IOSurface 00000024 modified by process WindowServer using the GPU while surface is write locked by process AppleVNCServer

      84 

      85  System log

      86 

      87      Jan 15 22:05:00 networkd: nw_path_query_lqm Tried to query LQM on path with no interfaces

      88      Jan 15 22:05:00 symptomsd: -[NetworkAnalyticsEngine _writeJournalRecord:fromCellFingerprint:key:atLOI:ofKind:lqm:isFaulty:] Hashing of the primary key failed. Dropping the journal record.

      89      Jan 15 22:05:00 symptomsd: __73-[NetworkAnalyticsEngine observeValueForKeyPath:ofObject:change:context:]_block_invoke unexpected switch value 2

      90      Jan 15 22:05:02 mDNSResponder: mDNS_RegisterInterface: Frequent transitions for interface en1 (192.168.2.106)

      91      Jan 15 22:05:03 symptomsd: -[NetworkAnalyticsEngine _writeJournalRecord:fromCellFingerprint:key:atLOI:ofKind:lqm:isFaulty:] Hashing of the primary key failed. Dropping the journal record.

      92      Jan 15 22:05:03 symptomsd: __73-[NetworkAnalyticsEngine observeValueForKeyPath:ofObject:change:context:]_block_invoke unexpected switch value 2

      93      Jan 15 22:06:48 Safari: tcp_connection_tls_session_error_callback_imp 272 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

      94      Jan 15 22:08:06 FaceTime: GVA info: preferred scaler idx 0

      95      Jan 15 22:22:01 Safari: tcp_connection_tls_session_error_callback_imp 275 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

      96      Jan 15 22:28:36 SSInvitationAgent: IDSServiceController.m:588:-[IDSServiceController service:account:inviteReceivedForSession:fromID:withContext:]: inviteOptions == nil

      97      Jan 15 22:28:36 SSInvitationAgent: BlockedInvitersManager.m:415:-[BlockedInvitersManager isInviterIDBlocked:]: isInviterIDBlocked: mailto:EMAIL

      98      Jan 15 22:28:37 SSInvitationAgent: BlockedInvitersManager.m:433:-[BlockedInvitersManager isInviterIDBlocked:]: User is not blocked

      99      Jan 15 22:29:54 SSInvitationAgent: IDSServiceController.m:588:-[IDSServiceController service:account:inviteReceivedForSession:fromID:withContext:]: inviteOptions == nil

    100      Jan 15 22:29:54 SSInvitationAgent: BlockedInvitersManager.m:415:-[BlockedInvitersManager isInviterIDBlocked:]: isInviterIDBlocked: mailto:EMAIL

    101      Jan 15 22:29:54 SSInvitationAgent: BlockedInvitersManager.m:433:-[BlockedInvitersManager isInviterIDBlocked:]: User is not blocked

    102      Jan 15 22:29:57 SSInvitationAgent: IDSSessionControllerBase.m:413:-[IDSSessionControllerBase userNotificationCenter:didDismissAlert:]: User accepted invitation

    103      Jan 15 22:30:00 aslmanager: -[CacheDeleteServiceListener servicePeriodic:info:replyBlock:]:124 periodic callback is NULL

    104      Jan 15 22:30:10 SSInvitationAgent: IDSSessionControllerBase.m:480:-[IDSSessionControllerBase doAcceptIDSInvitation]: Called [IDSSession acceptInvitation]

    105      Jan 15 22:30:29 SSInvitationAgent: IDSSessionControllerBase.m:413:-[IDSSessionControllerBase userNotificationCenter:didDismissAlert:]: User accepted invitation

    106      Jan 15 22:31:03 fseventsd: Logging disabled completely for device:1: /Volumes/Recovery HD

    107      Jan 15 22:31:19 authd: Sandbox denied authorizing right 'system.install.app-store-software.standard-user' for authorization created by '/System/Library/CoreServices/Software Update.app/Contents/Resources/SoftwareUpdateConfigData' [1389]

    108      Jan 15 22:31:19 authd: Sandbox denied authorizing right 'system.install.app-store-software.standard-user' for authorization created by '/System/Library/CoreServices/Software Update.app/Contents/Resources/SoftwareUpdateConfigData' [1389]

    109      Jan 15 22:31:19 UserEventAgent: Failed to send message because the port couldn't be created.

    110      Jan 15 22:31:20 UserEventAgent: Failed to send message because the port couldn't be created.

    111      Jan 15 22:37:03 Safari: tcp_connection_tls_session_error_callback_imp 278 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

    112 

    113  launchd log

    114 

    115      Jan 10 22:17:56 : Failed to remove file or directory: name = dyld_shared_cache_x86_64, error = 1: Operation not permitted. Further logging suppressed.

    116      Jan 10 22:18:15 com.apple.airplaydiagnostics.server: Unrecognized MachService property: ResetAtClose

    117      Jan 10 22:43:34 com.apple.xpc.launchd.user.domain.501.100006.Aqua: Could not import service from caller: path = /System/Library/LaunchAgents/com.apple.CommCenter-osx.plist, caller = loginwindow.92, error = 138: Service cannot be loaded on this hardware

    118      Jan 10 22:43:35 com.apple.xpc.launchd.user.domain.501.100006.Aqua: Could not import service from caller: caller = otherbsd.256, service = com.apple.photostream-agent, error = 119: Service is disabled

    119      Jan 10 22:43:35 com.apple.xpc.launchd.user.domain.501.100006.Aqua: Could not import service from caller: caller = otherbsd.256, service = com.getdropbox.dropbox.loginhelper, error = 119: Service is disabled

    120 

    121  System services loaded

    122 

    123      com.apple.Kerberos.kdc

    124      - status: 1

    125      com.apple.logd

    126      - status: 1

    127      com.apple.watchdogd

    128      com.google.keystone.daemon

    129 

    130  Login services loaded

    131 

    132      com.google.keystone.system.agent

    133 

    134  User login items

    135 

    136      iTunesHelper

    137      - /Applications/iTunes.app/Contents/MacOS/iTunesHelper.app

    138      Dropbox

    139      - /Applications/Dropbox.app

    140 

    141  iCloud errors

    142 

    143      cloudd 123

    144      Photos 32

    145      bird 6

    146      comapple.CloudPhotosConfiguration 1

    147      Safari 1

    148      Finder 1

    149      CallHistorySyncHelper 1

    150 

    151  Bad permissions: 1274

    152 

    153  Lockfiles: 2

    154 

    155  Applications

    156 

    157      /Applications/Google Earth.app

    158      - com.Google.GoogleEarthPlus

    159      /Users/USER/Desktop/Google Earth.app

    160      - com.Google.GoogleEarthPlus

    161 

    162  Bundles

    163 

    164      /Users/USER/Library/Address Book Plug-Ins/SkypeABCaller.bundle

    165      - com.skype.SkypeABCaller

    166      /Users/USER/Library/Address Book Plug-Ins/SkypeABChatter.bundle

    167      - com.skype.SkypeABChatter

    168      /Users/USER/Library/Address Book Plug-Ins/SkypeABDialer.bundle

    169      - com.skype.SkypeABDialer

    170      /Users/USER/Library/Address Book Plug-Ins/SkypeABSMS.bundle

    171      - com.skype.SkypeABSMS

    172 

    173  Bundles (new)

    174 

    175      /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle

    176      - com.google.Keystone

    177 

    178  Library paths

    179 

    180      /Library/SystemMigration/History/MigrationUUID/QuarantineRoot/System/Library/St agedFrameworks/Safari/WebKit.framework/NetworkProcess.app 1/Contents/MacOS/SecItemShim.dylib

    181      /Library/SystemMigration/History/MigrationUUID/QuarantineRoot/System/Library/St agedFrameworks/Safari/WebKit.framework/PluginProcess.app 1/Contents/MacOS/PluginProcessShim.dylib

    182      /Library/SystemMigration/History/MigrationUUID/QuarantineRoot/System/Library/St agedFrameworks/Safari/WebKit.framework/WebProcess.app 1/Contents/MacOS/WebProcessShim.dylib

    183      /Library/SystemMigration/History/MigrationUUID/QuarantineRoot/System/Library/St agedFrameworks/Safari/WebKitLegacy.framework/WebKitPluginHost.app 1/Contents/MacOS/WebKitPluginHostShim.dylib

    184 

    185  App extensions

    186 

    187      com.getdropbox.dropbox.garcon

    188 

    189  Bad kernel extensions

    190 

    191      /System/Library/Extensions/AppleOSXUSBNCM.kext

    192 

    193  Installations

    194 

    195      Google Earth: 07.01.16, 13:00

    196 

    197  Elapsed time (sec): 780

  • by Helga,

    Helga Helga Jan 28, 2016 1:54 PM in response to Helga
    Level 2 (296 points)
    Apple TV
    Jan 28, 2016 1:54 PM in response to Helga

    I was hoping for a response, please Linc Davis.

     

    Thank you!

  • by Martin Blaha,Helpful

    Martin Blaha Martin Blaha May 8, 2016 10:21 AM in response to Helga
    Level 1 (14 points)
    May 8, 2016 10:21 AM in response to Helga

    Hi Helga,

     

    I had a very similar problem with my Email. At the end I had to change the configuration of my router to accept my Email SMTP server as a safe host. I've got a Deutsche Telekom Speedport Hybrid router. After that change everything worked fine again.

    Martin

  • by Helga,

    Helga Helga May 8, 2016 10:24 AM in response to Martin Blaha
    Level 2 (296 points)
    Apple TV
    May 8, 2016 10:24 AM in response to Martin Blaha

    Thanks for the information.   I kept telling my sister that it was her router, and finally, when my niece's mail went down also, they fixed it.  I would think that Deutsche Telekom helped along, but unfortunately she didn't tell me what they changed or how they did it.

     

    Helga

Previous Page 2