slovie64

Q: All messages I send using iMessage suddenly have a "Not Delivered" status. What's going on?

For months and months I was able to connect with my daughter using iMessage. Suddenly, since the new year, everything we try to send to one another is marked "Not Delivered." I've tried logging out and back in but nothing seems to work. Help!

Mac mini, OS X Yosemite (10.10.5)

Posted on Mar 16, 2016 6:37 AM

Close

Q: All messages I send using iMessage suddenly have a "Not Delivered" status. What's going on?

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Mar 16, 2016 6:54 AM in response to slovie64
    Level 10 (207,963 points)
    Applications
    Mar 16, 2016 6:54 AM in response to slovie64

    Please launch the Console 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.

    The title of the Console window should be All Messages. If it isn't, select

              SYSTEM LOG QUERIES ▹ All Messages

    from the log list on the left. If you don't see that list, select

              View ▹ Show Log List

    from the menu bar at the top of the screen.

    Click the Clear Display icon in the toolbar. Then take an action that isn't working the way you expect. Select any lines that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

    The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

    Please don't indiscriminately dump thousands of lines from the log into this discussion.

    Please don't post screenshots of log messages—post the text.

    Some private information, such as your name or email address, may appear in the log. Anonymize before posting.

    When you post the log extract, 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 forum software. Please post the text 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.

  • by slovie64,

    slovie64 slovie64 Mar 16, 2016 7:03 AM in response to Linc Davis
    Level 1 (0 points)
    Mar 16, 2016 7:03 AM in response to Linc Davis

    3/16/16 10:01:23.530 AM com.apple.SecurityServer[79]: Killing auth hosts

    3/16/16 10:01:23.532 AM com.apple.SecurityServer[79]: Session 100050 destroyed

    3/16/16 10:01:23.553 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

    3/16/16 10:01:23.580 AM com.apple.SecurityServer[79]: Session 100053 created

    3/16/16 10:01:23.892 AM IMRemoteURLConnectionAgent[3266]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)

    3/16/16 10:01:23.902 AM logind[94]: -[SessionManager getClient:withRole:inAuditSession:]:241: ERROR: No session dictionary for audit session 100053

    3/16/16 10:01:23.902 AM logind[94]: _SMGetSessionAgent:73: ERROR: __SMGetClientForAuditSessionAgent failed 2

    3/16/16 10:01:23.903 AM IMRemoteURLConnectionAgent[3266]: SACShieldWindowShowing:925: ERROR: NULL response

    3/16/16 10:01:23.906 AM identityservicesd[280]: [Warning] FTMessageDelivery failed! (HTTP Status Code: 0) Error (NSURLErrorDomain:-1202): The certificate for this server is invalid. You might be connecting to a server that is pretending to be “query.ess.apple.com” which could put your confidential information at risk. https://query.ess.apple.com/WebObjects/QueryService.woa/wa/query?uri=mailto%3Asa shafed%40mail.com%5Emailto%3Atracyfederico64%40gmail.com

    3/16/16 10:01:23.907 AM identityservicesd[280]: [Warning] FTMessageDelivery failed! (HTTP Status Code: 0) Error (NSURLErrorDomain:-1202): The certificate for this server is invalid. You might be connecting to a server that is pretending to be “query.ess.apple.com” which could put your confidential information at risk. https://query.ess.apple.com/WebObjects/QueryService.woa/wa/query?uri=mailto%3Asa shafed%40mail.com%5Emailto%3Atracyfederico64%40gmail.com

    3/16/16 10:01:23.907 AM identityservicesd[280]: [Warning] Response identities is not what we expected ((null) instead of NSArray) (null), error Error Domain=NSURLErrorDomain Code=-1202 "The operation couldn’t be completed. (NSURLErrorDomain error -1202.)", resultCode 20000

    3/16/16 10:01:25.080 AM com.apple.xpc.launchd[1]: (com.apple.imdmessageservices.IMDMessageServicesAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

    3/16/16 10:01:25.080 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

  • by Linc Davis,

    Linc Davis Linc Davis Mar 16, 2016 7:08 AM in response to slovie64
    Level 10 (207,963 points)
    Applications
    Mar 16, 2016 7:08 AM in response to slovie64

    This could be a complicated problem to solve, as there are several possible causes for it.

    Please back up all data, then take each of the following steps that you haven't already taken. Stop when the problem is resolved.

    Step 1

    From the menu bar, select

               ▹ System Preferences... ▹ Date & Time

    Select the Time Zone tab in the preference pane that opens and check that the time zone matches your location. Then select the Date & Time tab. Check that the date and time shown (including the year) are correct, and correct them if not.

    Check the box marked

              Set date and time automatically

    if it's not already checked, and select one of the Apple time servers from the menu next to it.

    Step 2

    Start up in safe mode and log in to the account with the problem.

    Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.

    The login screen appears even if you usually login 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.

    If the problem is not reproducible in safe mode, then it's caused by third-party "anti-virus" or "security" software. If you know what that software is, remove it as directed by the developer after backing up all data. If you don't know what it is, ask for instructions.

    Step 3

    Triple-click anywhere in the line below on this page to select it:

    /System/Library/Keychains/SystemCACertificates.keychain

    Right-click or control-click the highlighted line and select

              Services Show Info

    from the contextual menu.* An Info dialog should open. The dialog should show "You can only read" in the Sharing & Permissions section.

    Repeat with this line:

    /System/Library/Keychains/SystemRootCertificates.keychain

    If instead of the Info dialog, you get a message that either file can't be found, reinstall OS X.

    *If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combination command-C. Open a TextEdit window and paste into it by pressing command-V. Select the line you just pasted and continue as above.

    Step 4

    Launch the Keychain Access application in any 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.

    In the upper left corner of the window, you should see a list headed Keychains. If not, click the button in the lower left corner that looks like a triangle inside a square.

    In the Keychains list, there should be items named System and System Roots. If not, select

              File Add Keychain

    from the menu bar and add the following items:

    /Library/Keychains/System.keychain
    /System/Library/Keychains/SystemRootCertificates.keychain

    Open the View menu in the menu bar. If one of the items in the menu is

              Show Expired Certificates

    select it. Otherwise it will show

              Hide Expired Certificates

    which is what you want.

    From the Category list in the lower left corner of the window, select Certificates. Look carefully at the list of certificates in the right side of the window. If any of them has a blue-and-white plus sign or a red "X" in the icon, double-click it. An inspection window will open. Click the disclosure triangle labeled Trust to disclose the trust settings for the certificate. From the menu labeled

              Secure Sockets Layer (SSL)

    select

              no value specified

    Close the inspection window. You'll be prompted for your administrator password to update the settings.

    Now open the same inspection window again, and select

              When using this certificate: Use System Defaults

    Save the change in the same way as before.

    Revert all the certificates with non-default trust settings. Never again change any of those settings.

    Step 5

    Select My Certificates from the Category list. From the list of certificates shown, delete any that are marked with a red X as expired or invalid.

    Export all remaining certificates (even if valid), delete them from the keychain, and test. For example, there might be a certificate with a name beginning in "Symantec" or "Verisign."

    For instructions, select

              Help Keychain Access Help

    from the menu bar and search for the term "export" in the help window. Export each certificate as an individual file; don't combine them into one big file.

    If there's no change, you can reimport the certificates that you exported in this step (if any) by double-clicking them.

    Step 6

    From the menu bar, select

              Keychain Access Preferences... Certificates

    There are three menus in the window. Change the selection in the top two to Best attempt, and in the bottom one to  CRL.

    Step 7

    Triple-click anywhere in the line of text below on this page to select it:

    /var/db/crls

    Copy the selected text to the Clipboard by pressing the key combination command-C. In the Finder, select

              Go Go to Folder...

    from the menu bar and paste into the box that opens by pressing command-V. You may not see what you pasted because a line break is included. Press return.

    A folder named "crls" should open. Move all the files in that folder to the Trash. You’ll be prompted for your administrator login password.

    Restart the computer, empty the Trash, and test.

    Step 8

    Triple-click anywhere in the line below on this page to select it:

    open -e /etc/hosts

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

    Launch the built-in Terminal application in the same way you launched Keychain Access.

    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. A TextEdit window should open. At the top of the window, you should see this:

    ##
    # Host Database
    #
    # localhost is used to configure the loopback interface
    # when the system is booting.  Do not change this entry.
    ##
    127.0.0.1                              localhost
    255.255.255.255          broadcasthost
    ::1                                        localhost

    If that's not what you see, post the contents of the window.

  • by slovie64,

    slovie64 slovie64 Mar 16, 2016 7:21 AM in response to Linc Davis
    Level 1 (0 points)
    Mar 16, 2016 7:21 AM in response to Linc Davis

    Unfortunately, half of the instructions you wrote are so far over my head that I feel I can't implement them. Sigh. I need to find an iMessage alternative, which I have officially deemed a totally sucky application.

  • by Linc Davis,

    Linc Davis Linc Davis Mar 16, 2016 8:18 AM in response to slovie64
    Level 10 (207,963 points)
    Applications
    Mar 16, 2016 8:18 AM in response to slovie64

    Click the Support link at the top of this page to contact Apple Support.