Gmail accounts chronically unavailable

#855

This report may be closely related to #651 and possibly also #685. Benny, if you delete this report outright I certainly won't be offended. I am trying to help, but fear that I am not offering sufficiently detailed info.

##SETUP I am running MM 4317 with a Gmail account on Mac OS X 10.9.4. Running Google two-factor auth (application-specific passwords).

My Gmail account had been routinely unavailable for about 24 hours but is now fine, at least for the moment. I'll follow up with more info as it becomes available.

The only thing that changed 24 hours ago, of which I'm aware, is that some technicians have been poking at the network, so it may (?) be that the network is somewhat slower or flakier than it was more than 24 hours ago. This is unconfirmed, though.

The Activity window shows:
19:10:41 Error: Time limit (16s) reached while trying to write data (imap.gmail.com)
19:10:41 Error: Failed while trying to connect to “imap.gmail.com” on socket 21.
19:10:41 Error code: 2
19:10:41 Failed action (1000). Reset observed read/write timeouts: 8/8

19:10:41 Clearing connection to imap.gmail.com
19:10:44 Clearing connection to imap.gmail.com
19:10:44 Trying to connect to imap.gmail.com on port 993
19:10:44 Successful connection on socket 21.
19:10:44 Initiating secure connection...
19:11:14 Error: Failed SSL handshake (0/5)..
19:11:14 Clearing connection to imap.gmail.com
19:11:14 Trying to connect to imap.gmail.com on port 143
19:11:30 Error: Time limit (16s) reached while trying to write data (imap.gmail.com)
19:11:30 Error: Failed while trying to connect to “imap.gmail.com” on socket 21.
19:11:30 Error code: 2
19:11:30 Failed action (1000). Reset observed read/write timeouts: 8/8

19:11:30 Error: Failed multiple retries (4). Final error code was 2.

TERMINAL (per report #651):
% openssl s_client -crlf -connect imap.gmail.com:993 CONNECTED(00000003)
depth=2 /C=US/O=GeoTrust Inc./CN=GeoTrust Global CA
verify error:num=20:unable to get local issuer certificate
verify return:0
507:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:/SourceCache/OpenSSL098/OpenSSL098-50/src/ssl/s23_lib.c:182:

(Note: Does this suggest a problem outside MM?)

Per bug report 651, tried:
defaults write com.freron.MailMate MmSkipSSLHandshake -bool NO
defaults write com.freron.MailMate MmUseDirectSSLHandshake -bool YES

...and rebooted.

##Current behavior After reboot, problem appeared for a few minutes to be still in play... then suddenly a ton of FETCHes on Activity Viewer, and suddenly email from the last 24 hours appears in MM.

All appears well.

I will update this report in 12-72 hours to reflect whether it remains fixed.

I would add this info to the appropriate previous report, but I don't know which is most applicable.

Reported by Wes Carroll · July 23rd, 2014 @ 07:33 PM

Activity

benny
What is the status on this?

I recommend updating to the latest test release since some bad bugs in earlier test versions have been fixed: Hold down ⌥ when clicking “Check Now” in the Software Update preferences.

August 15th, 2014 @ 12:21 PM
Wes Carroll
Apologies for not following up earlier.

I am continuing to run 4317 at present, but this behavior has not recurred. I have some anecdotal evidence to suggest that the problem was that MailMate did not handle a bad network connection as well as one might hope: the problem first occurred when technicians introduced some noise on my DSL line. Since that time, the noise has been removed and the problem has not recurred. I cannot say for certain whether the timing is indicative or just coincidental.

Recommend closing bug.

August 15th, 2014 @ 03:39 PM
Wes Carroll
Now upgrading to 4432. Thanks for the tip!

August 15th, 2014 @ 03:39 PM
benny
- State changed from new to closed
August 16th, 2014 @ 07:25 AM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.