Mail Connections Lost After Sleep (Ports Fail)

Question

Level 1

10 points

Mail Connections Lost After Sleep (Ports Fail)

I am having the problem that others are having regarding Mail reconnecting after sleep. Typically, it fails to connect to my Company IMAP server, and the IMAP Gmail server (but connects to the Gmail SMTP server). It looks like this in Connection Doctor:

I have done the following already:

1. Deleted and reinstalled the accounts

2. Reinstalled Mountain Lion from network

3. Reset my SMC

I have searched for any firewall that would mess it up, but have come up with nothing. Here is the readout from Terminal:

ls: /Library/InputManagers: No such file or directory

ls: /Library/Mail/Bundles: No such file or directory

ls: /Users/KyleEssary/Library/Mail/Bundles: No such file or directory

/Library/LaunchAgents:

com.Cvnt.start.plist

com.amazon.sendtokindle.launcher.plist

/Library/LaunchDaemons:

com.Cvnt.daemon.plist

com.adobe.fpsaud.plist

/Library/StartupItems:

/Users/KyleEssary/Library/LaunchAgents:

com.apple.AddressBook.ScheduledSync.PHXCardDAVSource.DB72A0D3-A7F5-42AA-B8C0-B9F DD21F52AE.plist

The CVnt plist is from an app that I added long after I noticed this problem. The problem was the same before and after installing that app.

Whenever I run the Network Utility following a wake from sleep on typical ports, I get this:

Whatever the issue may be, it apparently starts on sleep because Power Nap has yet to work. I have had this issue since installing Mountain Lion and would appreciate any help.

MacBook Air (13-INCH, MID 2011), OS X Mountain Lion (10.8.1)

Posted on Sep 5, 2012 12:36 AM

Reply

Answer 1

Rangeressary Author

Level 1

10 points

Sep 5, 2012 12:40 AM in response to Rangeressary

I should also mention that quitting Mail and the reopening it solves the problem. I would be pleased if it "just worked" though and I didn't have to go through the restart app procedure each time my Air woke from sleep.

Reply

Answer 2

Lukum

Level 1

60 points

Sep 5, 2012 2:47 AM in response to Rangeressary

I'm having a similar issue under Mountain Lion with Mail stalling forever when the internet connection changes during sleep (e.g. from wi-fi to ethernet, or from a wi-fi to another one). Quitting Mail solves the problem randomly only. Yesterday the problem started with Mail, then it extended to Chrome and to the whole system. I need to restart my MacBook way too often because that issue tends to freeze everything at some point.

I'd appreciate to know how to investigate into this issue.

Reply

Answer 3

Bazze

Level 1

9 points

Sep 6, 2012 5:03 AM in response to Rangeressary

The same happens to me. VERY frustrating. Restarting Apple Mail solves the problem sometimes only.

Reply

Answer 4

Rangeressary Author

Level 1

10 points

Sep 9, 2012 3:47 AM in response to Bazze

This is frustrating, and Apple doesn't seem to have any solution. Does anyone have any ideas?

Reply

Answer 5

Rangeressary Author

Level 1

10 points

Sep 9, 2012 4:11 AM in response to Rangeressary

Notice as well on the Connection Doctor pic that I am able to connect to the internet, and when I open Safari there is no problem. For some reason Mail's ports simply don't work after waking up.

Reply

Answer 6

Rangeressary Author

Level 1

10 points

Sep 9, 2012 4:20 AM in response to Rangeressary

I don't know why I hadn't thought of this. I simply turned off the Apple Firewall and now Mail works like a charm after it wakes from sleep. So my advice would be to disable your firewall and use something else until Apple fixes their issues.

Reply

Answer 7

Rangeressary Author

Level 1

10 points

Sep 9, 2012 3:22 PM in response to Rangeressary

Well...it started again, and the firewall is still off...

I guess its not the firewall after all...

Reply

Answer 8

Sep 14, 2012 5:35 AM in response to Rangeressary

Add me to the list. Very frustrating. Def another Mail bug. In addition to the bug where all sounds queue and play continuously after I plug in a headphone it seems that one of the most basic apps of Mt Lion was not tested very well by Apple. Pretty shameful!

Reply

Answer 9

Sep 19, 2012 1:05 PM in response to Rangeressary

Having the exact same problem... thanks for posting Rangeressary. Very frustrating having to restart Mail after every wake!

Reply

Answer 10

Sep 19, 2012 9:38 PM in response to Rangeressary

Change MTU Size to Prevent Dropped Connections

This is a bit geeky but bare with us: MTU stands for Maximum Transmission Unit and controls the largest packet size allowed for transmission over the network. If this setting is greater than network capacity, the computer will experience packet loss and dropped connections. The default setting of 1500 is somewhat aggressive and some networks reject packets of that size, but it turns out that 1453 is just small enough to maintain a consistent connection with most networks but just large enough to not cause any slowdowns, it’s the magic number and an old cisco networking secret.

Open System Preferences from the  Apple menu and select “Network”
Click the “Advanced” button in the lower corner, followed by the “Hardware” tab
Pull down the “Configure” menu and set to “Manually”
Change “MTU” to “Custom” and set the field to “1453″

From: http://osxdaily.com/2012/08/02/fix-os-x-mountain-lion-wireless-connection-proble ms/

Reply

Answer 11

Sep 30, 2012 1:23 AM in response to Rangeressary

I'm also experiencing this problem, but have never had firewall switched on to begin with, so that does noet seem to be the solution.

Reply

Answer 12

Sep 30, 2012 3:47 AM in response to Fancytricks

Thanks Fancytricks. I tried your solution but the problem persists.

I too tried disabling the firewall but to no avail.

Is there a way to remove the 'solved' status from this thread?

Reply

Answer 13

Oct 3, 2012 2:57 AM in response to Rangeressary

What does appear to work with me (in ways I do not fully understand): I deleted the Google Drive application from my system and the problem seemed to have vanished. This was at home, but this morning at work it reappeared. So I also quit dropbox, and put my mac to sleep, and lo & behold: on wake-up from sleep the problem seemed to have gone (no exclamation marks next to my IMAP accounts). I started dropbox again, put mac to sleep, and theproblem reappeared again. I also have an Exchange account, which does not suffer from the problem either.

Reply

Answer 14

Oct 3, 2012 1:45 PM in response to Rangeressary

Hmm, even with dropbox and google drive turned off the problem reappeared when going from work to home again. This is the log from the connection doctor. The offending accounts (red dots) are imap.gmail.com and imap.hubrussel.be:

INITIATING CONNECTION Oct 03 22:27:22.097 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fd3ace292b0

INITIATING CONNECTION Oct 03 22:27:22.098 -- host:in.base.be -- port:110 -- socket:0x0 -- thread:0x7fd3ace7eac0

INITIATING CONNECTION Oct 03 22:27:22.098 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fd3af30c610

INITIATING CONNECTION Oct 03 22:27:22.098 -- host:imap.hubrussel.be -- port:143 -- socket:0x0 -- thread:0x7fd3af3ca170

INITIATING CONNECTION Oct 03 22:27:22.098 -- host:in.base.be -- port:110 -- socket:0x0 -- thread:0x7fd3af4a3120

INITIATING CONNECTION Oct 03 22:27:22.098 -- host:out.base.be -- port:25 -- socket:0x0 -- thread:0x7fd3ac5406c0

CONNECTED Oct 03 22:27:22.173 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3af524e90 -- thread:0x7fd3ace7eac0

CONNECTED Oct 03 22:27:22.176 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3acc96d10 -- thread:0x7fd3af4a3120

CONNECTED Oct 03 22:27:22.179 [kCFStreamSocketSecurityLevelNone] -- host:out.base.be -- port:25 -- socket:0x7fd3aae11320 -- thread:0x7fd3ac5406c0

CONNECTED Oct 03 22:27:22.186 [kCFStreamSocketSecurityLevelNone] -- host:smtp.gmail.com -- port:587 -- socket:0x7fd3acb4ccc0 -- thread:0x7fd3af30c610

READ Oct 03 22:27:22.207 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3af524e90 -- thread:0x7fd3ace7eac0

+OK Dovecot ready.

WROTE Oct 03 22:27:22.214 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3af524e90 -- thread:0x7fd3ace7eac0

CAPA

READ Oct 03 22:27:22.218 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3acc96d10 -- thread:0x7fd3af4a3120

+OK Dovecot ready.

READ Oct 03 22:27:22.232 [kCFStreamSocketSecurityLevelNone] -- host:smtp.gmail.com -- port:587 -- socket:0x7fd3acb4ccc0 -- thread:0x7fd3af30c610

220 mx.google.com ESMTP f1sm11105266wiy.2

WROTE Oct 03 22:27:22.249 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3acc96d10 -- thread:0x7fd3af4a3120

CAPA

READ Oct 03 22:27:22.254 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3af524e90 -- thread:0x7fd3ace7eac0

+OK

CAPA

TOP

UIDL

RESP-CODES

PIPELINING

STLS

USER

SASL PLAIN LOGIN

.

WROTE Oct 03 22:27:22.276 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3af524e90 -- thread:0x7fd3ace7eac0

AUTH PLAIN

WROTE Oct 03 22:27:22.278 [kCFStreamSocketSecurityLevelNone] -- host:smtp.gmail.com -- port:587 -- socket:0x7fd3acb4ccc0 -- thread:0x7fd3af30c610

EHLO [192.168.1.86]

READ Oct 03 22:27:22.284 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3acc96d10 -- thread:0x7fd3af4a3120

+OK

CAPA

TOP

UIDL

RESP-CODES

PIPELINING

STLS

USER

SASL PLAIN LOGIN

.

WROTE Oct 03 22:27:22.315 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3acc96d10 -- thread:0x7fd3af4a3120

AUTH PLAIN

READ Oct 03 22:27:22.317 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3af524e90 -- thread:0x7fd3ace7eac0

+

READ Oct 03 22:27:22.333 [kCFStreamSocketSecurityLevelNone] -- host:smtp.gmail.com -- port:587 -- socket:0x7fd3acb4ccc0 -- thread:0x7fd3af30c610

250-mx.google.com at your service, [94.108.227.48]

250-SIZE 35882577

250-8BITMIME

250-STARTTLS

250 ENHANCEDSTATUSCODES

READ Oct 03 22:27:22.348 [kCFStreamSocketSecurityLevelNone] -- host:out.base.be -- port:25 -- socket:0x7fd3aae11320 -- thread:0x7fd3ac5406c0

220 relay03ant.iops.be ESMTP

READ Oct 03 22:27:22.351 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3acc96d10 -- thread:0x7fd3af4a3120

+

WROTE Oct 03 22:27:22.357 [kCFStreamSocketSecurityLevelNone] -- host:smtp.gmail.com -- port:587 -- socket:0x7fd3acb4ccc0 -- thread:0x7fd3af30c610

STARTTLS

WROTE Oct 03 22:27:22.367 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3af524e90 -- thread:0x7fd3ace7eac0

************************

WROTE Oct 03 22:27:22.378 [kCFStreamSocketSecurityLevelNone] -- host:out.base.be -- port:25 -- socket:0x7fd3aae11320 -- thread:0x7fd3ac5406c0

EHLO [192.168.1.86]

WROTE Oct 03 22:27:22.386 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3acc96d10 -- thread:0x7fd3af4a3120

****************************

READ Oct 03 22:27:22.408 [kCFStreamSocketSecurityLevelNone] -- host:smtp.gmail.com -- port:587 -- socket:0x7fd3acb4ccc0 -- thread:0x7fd3af30c610

220 2.0.0 Ready to start TLS

READ Oct 03 22:27:22.426 [kCFStreamSocketSecurityLevelNone] -- host:out.base.be -- port:25 -- socket:0x7fd3aae11320 -- thread:0x7fd3ac5406c0

250-relay03ant.iops.be

250-PIPELINING

250-SIZE 20480000

250-ETRN

250-ENHANCEDSTATUSCODES

250-8BITMIME

250 DSN

WROTE Oct 03 22:27:22.433 [kCFStreamSocketSecurityLevelNone] -- host:out.base.be -- port:25 -- socket:0x7fd3aae11320 -- thread:0x7fd3ac5406c0

EHLO [192.168.1.86]

READ Oct 03 22:27:22.486 [kCFStreamSocketSecurityLevelNone] -- host:out.base.be -- port:25 -- socket:0x7fd3aae11320 -- thread:0x7fd3ac5406c0

250-relay03ant.iops.be

250-PIPELINING

250-SIZE 20480000

250-ETRN

250-ENHANCEDSTATUSCODES

250-8BITMIME

250 DSN

WROTE Oct 03 22:27:22.492 [kCFStreamSocketSecurityLevelNone] -- host:out.base.be -- port:25 -- socket:0x7fd3aae11320 -- thread:0x7fd3ac5406c0

QUIT

WROTE Oct 03 22:27:22.630 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.gmail.com -- port:587 -- socket:0x7fd3acb4ccc0 -- thread:0x7fd3af30c610

EHLO [192.168.1.86]

READ Oct 03 22:27:22.692 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.gmail.com -- port:587 -- socket:0x7fd3acb4ccc0 -- thread:0x7fd3af30c610

250-mx.google.com at your service, [94.108.227.48]

250-SIZE 35882577

250-8BITMIME

250-AUTH LOGIN PLAIN XOAUTH XOAUTH2

250 ENHANCEDSTATUSCODES

WROTE Oct 03 22:27:22.701 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.gmail.com -- port:587 -- socket:0x7fd3acb4ccc0 -- thread:0x7fd3af30c610

AUTH PLAIN (*** 56 bytes hidden ***)

READ Oct 03 22:27:23.213 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.gmail.com -- port:587 -- socket:0x7fd3acb4ccc0 -- thread:0x7fd3af30c610

235 2.7.0 Accepted

WROTE Oct 03 22:27:23.220 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.gmail.com -- port:587 -- socket:0x7fd3acb4ccc0 -- thread:0x7fd3af30c610

QUIT

READ Oct 03 22:27:26.729 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3af524e90 -- thread:0x7fd3ace7eac0

+OK Logged in.

WROTE Oct 03 22:27:26.740 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3af524e90 -- thread:0x7fd3ace7eac0

QUIT

READ Oct 03 22:27:26.774 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3af524e90 -- thread:0x7fd3ace7eac0

+OK Logging out.

READ Oct 03 22:27:30.698 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3acc96d10 -- thread:0x7fd3af4a3120

+OK Logged in.

WROTE Oct 03 22:27:30.708 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3acc96d10 -- thread:0x7fd3af4a3120

QUIT

READ Oct 03 22:27:30.748 [kCFStreamSocketSecurityLevelNone] -- host:in.base.be -- port:110 -- socket:0x7fd3acc96d10 -- thread:0x7fd3af4a3120

+OK Logging out.

Reply

Answer 15

Oct 4, 2012 11:55 AM in response to Rangeressary

Another element of the puzzle: no problem when MBP is connected to the internet with ethernet cable and wakes from sleep. Problem re-emerges on wifi at work with gmail, not work mail, not always at home, except when switching from work wifi to home wifi.

Reply