10.11.5 Rackspace mail problem

Question

Level 1

4 points

10.11.5 Rackspace mail problem

I have three mail accounts, two work fine and one, Rackspace, doesn't. I've spoken to Apple Support and they say go to my mail provider (Rackspace) who say the system is fine it's your device. I also use an iPhone and it does work fine with that.

When I try to reply to a mail, the window closes and 2-3 seconds later reappears as if the mail is not sent. Then 2-3 seconds later the window closes and this cycle repeats indefinitely. The only way to stop this is to go to the outbox and delete the mail.

I've deleted the account and re-installed, the same thing happens. I've deleted Rapport and even reset NVRAM, still the same. Any advice would be most welcome.

Posted on Jul 3, 2016 12:40 PM

Reply

Answer 1

Linc Davis

Level 10

209,739 points

Jul 3, 2016 12:45 PM in response to davew42

From the Mail menu bar, please select

Window ▹ Connection Doctor

Click the Show Detail button. A drawer opens. Try to send a test message and post the text that appears.

Anonymize any private information before posting. That means names, email addresses, contents of messages, and anything else that you don't want to make public.

Reply

Answer 2

davew42 Author

Level 1

4 points

Jul 3, 2016 12:51 PM in response to davew42

Is this what you wanted? It is the Munay Medicine account that is the problem

Reply

Answer 3

Linc Davis

Level 10

209,739 points

Jul 3, 2016 1:07 PM in response to davew42

Is this what you wanted?

No. If the instructions are unclear, please specify what you don't understand.

Reply

Answer 4

davew42 Author

Level 1

4 points

Jul 3, 2016 1:29 PM in response to davew42

WROTE Jul 03 15:26:49.227 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f815560b090 -- thread:0x7f8155066650

3.51 AUTHENTICATE XOAUTH2 dXNlcj1kYXZpZEBtdW5heW1lZGljaW5lLmNvbQFhdXRoPUJlYXJlciB5YTI5LkNqa1VBMS0zSnUtRHh 3UG45cW9PUURBU2VGcFRZM2JhUGNwZG1mNjc4RjJHNTlIaldVNUFWZ0dsOFhsVlNOOVI4VkQwRVE0RU9 kZW9ldzgBAQ==

READ Jul 03 15:26:49.506 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f815560b090 -- thread:0x7f8155066650

+ eyJzdGF0dXMiOiI0MDAiLCJzY2hlbWVzIjoiQmVhcmVyIiwic2NvcGUiOiJodHRwczovL21haWwuZ29 vZ2xlLmNvbS8ifQ==

WROTE Jul 03 15:26:49.506 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f815560b090 -- thread:0x7f8155066650

AQ==

READ Jul 03 15:26:50.198 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f815560b090 -- thread:0x7f8155066650

3.51 NO [AUTHENTICATIONFAILED] Invalid credentials (Failure)

WROTE Jul 03 15:26:50.200 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f815560b090 -- thread:0x7f8155066650

10.51 LOGOUT

READ Jul 03 15:27:01.051 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:secure.emailsrvr.com -- port:143 -- socket:0x7f815302b490 -- thread:0x7f8155048fb0

* OK Still here

The same thing happened, a new mail would not send and I had to delete in the outbox and this is the some of text.

Reply

Answer 5

Linc Davis

Level 10

209,739 points

Jul 3, 2016 1:42 PM in response to davew42

That extract shows no evidence that you tried to send a message. Did you?

Reply

Answer 6

davew42 Author

Level 1

4 points

Jul 3, 2016 1:45 PM in response to Linc Davis

Yes, the send window came and went probably a dozen times. I will do it again.

Reply

Answer 7

davew42 Author

Level 1

4 points

Jul 3, 2016 1:48 PM in response to davew42

WROTE Jul 03 15:46:25.609 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

AUTH XOAUTH2 dXNlcj1kYXZpZEBtdW5heW1lZGljaW5lLmNvbQFhdXRoPUJlYXJlciB5YTI5LkNqa1VBMmdvZjJoNmc yX1JtQ3BQVHEtdndkZlVKSXdzNWZuY1J4ZWJXTnEzUlRzTl9uMzE2djNFS2VsZVIyX24yMUo5VDhPVzc tN1pSVjgBAQ==

READ Jul 03 15:46:25.682 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150464960 -- thread:0x7f8153419a30

* OK Gimap ready for requests from 191.97.50.244 u184mb123514190ywg

WROTE Jul 03 15:46:25.682 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150464960 -- thread:0x7f8153419a30

1.93 CAPABILITY

READ Jul 03 15:46:25.847 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

334 eyJzdGF0dXMiOiI0MDAiLCJzY2hlbWVzIjoiQmVhcmVyIiwic2NvcGUiOiJodHRwczovL21haWwuZ29 vZ2xlLmNvbS8ifQ==

WROTE Jul 03 15:46:25.847 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

AQ==

READ Jul 03 15:46:25.879 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150464960 -- thread:0x7f8153419a30

* CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER AUTH=XOAUTH

1.93 OK Thats all she wrote! u184mb123514190ywg

WROTE Jul 03 15:46:25.880 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150464960 -- thread:0x7f8153419a30

2.93 ID ("name" "Mac OS X Mail" "version" "9.3 (3124)" "os" "Mac OS X" "os-version" "10.11.5 (15F34)" "vendor" "Apple Inc.")

READ Jul 03 15:46:26.054 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

535-5.7.8 Username and Password not accepted. Learn more at

535 5.7.8 https://support.google.com/mail/answer/14257 8sm2408725ywa.28 - gsmtp

WROTE Jul 03 15:46:26.056 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

AUTH LOGIN

READ Jul 03 15:46:26.103 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150464960 -- thread:0x7f8153419a30

* ID ("name" "GImap" "vendor" "Google, Inc." "support-url" "http://support.google.com/mail" "remote-host" "191.97.50.244" "connection-token" "u184mb123514190ywg")

2.93 OK Success u184mb123514190ywg

WROTE Jul 03 15:46:26.104 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150464960 -- thread:0x7f8153419a30

3.93 AUTHENTICATE XOAUTH2 dXNlcj1kYXZpZEBtdW5heW1lZGljaW5lLmNvbQFhdXRoPUJlYXJlciB5YTI5LkNqa1VBMmdvZjJoNmc yX1JtQ3BQVHEtdndkZlVKSXdzNWZuY1J4ZWJXTnEzUlRzTl9uMzE2djNFS2VsZVIyX24yMUo5VDhPVzc tN1pSVjgBAQ==

READ Jul 03 15:46:26.255 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

334 VXNlcm5hbWU6

WROTE Jul 03 15:46:26.255 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

ZGF2aWRAbXVuYXltZWRpY2luZS5jb20=

READ Jul 03 15:46:26.455 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

334 UGFzc3dvcmQ6

WROTE Jul 03 15:46:26.456 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

*

READ Jul 03 15:46:26.502 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150464960 -- thread:0x7f8153419a30

+ eyJzdGF0dXMiOiI0MDAiLCJzY2hlbWVzIjoiQmVhcmVyIiwic2NvcGUiOiJodHRwczovL21haWwuZ29 vZ2xlLmNvbS8ifQ==

WROTE Jul 03 15:46:26.502 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150464960 -- thread:0x7f8153419a30

AQ==

READ Jul 03 15:46:26.654 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

501 5.5.2 Cannot Decode response 8sm2408725ywa.28 - gsmtp

WROTE Jul 03 15:46:26.655 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

AUTH LOGIN

READ Jul 03 15:46:26.698 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150464960 -- thread:0x7f8153419a30

3.93 NO [AUTHENTICATIONFAILED] Invalid credentials (Failure)

WROTE Jul 03 15:46:26.700 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150464960 -- thread:0x7f8153419a30

10.93 LOGOUT

READ Jul 03 15:46:26.854 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

334 VXNlcm5hbWU6

WROTE Jul 03 15:46:26.854 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

ZGF2aWRAbXVuYXltZWRpY2luZS5jb20=

READ Jul 03 15:46:27.053 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

334 UGFzc3dvcmQ6

WROTE Jul 03 15:46:27.053 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

*

READ Jul 03 15:46:27.252 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

501 5.5.2 Cannot Decode response 8sm2408725ywa.28 - gsmtp

WROTE Jul 03 15:46:27.252 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.gmail.com -- port:587 -- socket:0x7f8153133520 -- thread:0x7f81505a6f70

QUIT

INITIATING CONNECTION Jul 03 15:46:29.124 host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7f8155384900

CONNECTED Jul 03 15:46:29.627 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150602d80 -- thread:0x7f8155384900

READ Jul 03 15:46:30.138 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150602d80 -- thread:0x7f8155384900

* OK Gimap ready for requests from 191.97.50.244 h128mb55613776yxh

WROTE Jul 03 15:46:30.138 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150602d80 -- thread:0x7f8155384900

1.94 CAPABILITY

READ Jul 03 15:46:30.326 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150602d80 -- thread:0x7f8155384900

* CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER AUTH=XOAUTH

1.94 OK Thats all she wrote! h128mb55613776yxh

WROTE Jul 03 15:46:30.326 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150602d80 -- thread:0x7f8155384900

2.94 ID ("name" "Mac OS X Mail" "version" "9.3 (3124)" "os" "Mac OS X" "os-version" "10.11.5 (15F34)" "vendor" "Apple Inc.")

READ Jul 03 15:46:30.515 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150602d80 -- thread:0x7f8155384900

* ID ("name" "GImap" "vendor" "Google, Inc." "support-url" "http://support.google.com/mail" "remote-host" "191.97.50.244" "connection-token" "h128mb55613776yxh")

2.94 OK Success h128mb55613776yxh

WROTE Jul 03 15:46:30.516 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150602d80 -- thread:0x7f8155384900

3.94 AUTHENTICATE XOAUTH2 dXNlcj1kYXZpZEBtdW5heW1lZGljaW5lLmNvbQFhdXRoPUJlYXJlciB5YTI5LkNqa1VBX0hDT3lRdTB 2NnA1QkFFYmJ3QU9OeDdQRE5yYVVZSVJqMGFWc20yaTAyazM1dkdfbjV3VV85b1BzZmRLQlBhYVF6UkN mbExCQTQBAQ==

READ Jul 03 15:46:30.855 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150602d80 -- thread:0x7f8155384900

+ eyJzdGF0dXMiOiI0MDAiLCJzY2hlbWVzIjoiQmVhcmVyIiwic2NvcGUiOiJodHRwczovL21haWwuZ29 vZ2xlLmNvbS8ifQ==

WROTE Jul 03 15:46:30.855 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150602d80 -- thread:0x7f8155384900

AQ==

READ Jul 03 15:46:31.043 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150602d80 -- thread:0x7f8155384900

3.94 NO [AUTHENTICATIONFAILED] Invalid credentials (Failure)

WROTE Jul 03 15:46:31.044 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:imap.gmail.com -- port:993 -- socket:0x7f8150602d80 -- thread:0x7f8155384900

10.94 LOGOUT

WROTE Jul 03 15:46:31.362 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:secure.emailsrvr.com -- port:143 -- socket:0x7f8155a4e100 -- thread:0x7f81507a56d0

DONE

READ Jul 03 15:46:31.560 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:secure.emailsrvr.com -- port:143 -- socket:0x7f8155a4e100 -- thread:0x7f81507a56d0

18.53 OK Idle completed.

WROTE Jul 03 15:46:31.560 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:secure.emailsrvr.com -- port:143 -- socket:0x7f8155a4e100 -- thread:0x7f81507a56d0

19.53 EXPUNGE

READ Jul 03 15:46:31.763 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:secure.emailsrvr.com -- port:143 -- socket:0x7f8155a4e100 -- thread:0x7f81507a56d0

19.53 OK Expunge completed.

WROTE Jul 03 15:46:31.764 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:secure.emailsrvr.com -- port:143 -- socket:0x7f8155a4e100 -- thread:0x7f8156614ab0

20.53 IDLE

READ Jul 03 15:46:31.955 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:secure.emailsrvr.com -- port:143 -- socket:0x7f8155a4e100 -- thread:0x7f8156614ab0

+ idling

READ Jul 03 15:47:00.627 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:secure.emailsrvr.com -- port:143 -- socket:0x7f815302b490 -- thread:0x7f81507a56d0

* OK Still here

Reply

Answer 8

Linc Davis

Level 10

209,739 points

Jul 3, 2016 2:46 PM in response to davew42

Please take each of the following steps that you haven't already tried, testing after each one. Back up all data before making any changes.

Step 1

From the Mail menu bar, select

Window ▹ Connection Doctor

Double-click the problem SMTP (outgoing mail) account in the window that opens. it. Another window will open, showing a list of all the outgoing mail accounts. The one you clicked will be selected.

Select the Advanced tab in the settings for the account and check the box marked

Automatically detect and maintain account settings

if it's not already checked.

If there's more than one problem account, repeat. Close the window and save the changes.

Step 2

Open the SMTP server list again. Make a note of the settings of the problem server, then click the minus-sign button to delete it, and confirm. Click the plus-sign button and recreate the account with the same settings.

If you're using Gmail, delete the account completely in the Internet Accounts preference pane and recreate it. The "detect and maintain" option must be selected in the Advanced settings for the incoming mail account.

The messages will be resynchronized with the server automatically. That may take hours if the mailboxes are very large.

Step 3

Quit Mail if it's running. Launch the Keychain Access application and enter the name of the outgoing mail server in the search box. For example, if you use Gmail, enter

smtp.gmail.com

Make a note of the password, then delete the keychain item(s). The next time Mail connects to the server, it will prompt for the password. Enter it and save the password in the keychain.

Step 4

This step appliies only if you're using Gmail.

Log in to your account on the website and, in the account settings, click the link to "Sign-in and security". There should be a option somewhere on the page to "Allow less secure apps". Enable that option and save the change. Note: I don't use Gmail and I haven't tested this solution myself. If it doesn't work, either go to the Google user forums for help, stop trying to use Gmail with Mail, or just stop using Gmail altogether (highly recommended.)

Step 5

This step doesn't apply to Gmail.

The mail server may be using a weak, obsolete form of encryption to secure its communications with the clients. Recent versions of OS X changed the behavior of Mail and other applications so that they no longer tolerate weak security.

Log into the mail account on the website and see whether there is a security setting you can change. I can't be more specific. Refer to the service provider's documentation.

If there is no setting, persuade the server administrator to upgrade the server's security. He or she should do that anyway. Weak security affects all clients, not just Mac users.

Otherwise, you don't have any good options for continuing use Mail with the service. You could disable SSL in the advanced account settings, but that's very unsafe and may not work at all.

You might be able to get a more flexible mail client, such as "Thunderbird," to accept the weak security, or maybe you can access the account via webmail.

Ideally you should switch to a better mail service provider. You wouldn't have this problem with a well-run service. The risks of weak SSL have been known for a long time, and competent server administrators have already taken the simple steps needed to avoid those risks.

Reply

Answer 9

davew42 Author

Level 1

4 points

Jul 6, 2016 6:27 AM in response to davew42

I received a lot of help and I am thankful for that, however the problem was never solved and I had to load a third party mail App that works fine. Disappointed at the outcome but I can now see why PC freaks laugh at Apple.

Reply

Answer 10

ron_13

Level 1

28 points

Oct 1, 2016 10:41 PM in response to davew42

I had a similiar problem and it was caused by me setting the username and password in Mail, but it didn't sync to System Preferences --> Internet Accounts. Once I went into System Preferences --> Internet Accounts and updated username and password everything started working.

Reply