IMAP time out on port 993

Hello,
Since 2 days I have every minute a "time out" pop up on mail app regarding my imaps accounts.
I own the mailserver so i know that the problem doesnt come from there.
What should i do ?
I dont really want to delete the pref & cache because it is huge mailboxes and here in Australia we have some internet quota...
help..

Jerume,
Search this forum for the string ".OfflineCache" and you'll find several messages describing how to fix this problem in the short term.
What has happened, I think, is that at some point you were editing a message (and possibly sent it) and Mail.app thought you were offline so it saved the drafts files and sent message in the .OfflineCache in ~/Library/Mail. The problem I'm having is that when that happens, Mail.app is never able to clear the .OfflineCache once you go online again.
The net result is that every minute it tries to resend the message and fails, in my case with a timeout and INTERNAL ERROR: Keyword hashtable memory corruption:
READ May 19 17:14:13.626 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:mail.spamarrest.com -- port:993 -- socket:0x189d0050 -- thread:0x1d314d10
* BYE Disconnected for inactivity.
* BYE [ALERT] Fatal error: INTERNAL ERROR: Keyword hashtable memory corruption.: Input/output error
I have not been able to figure out how to resolve this from my end. SpamArrest swears it's not their problem.
Chip

Similar Messages

Updated to 10.6.3. Now IMAP times out.

Last week, I installed the update to 10.6.3. Since then, I have been unable to receive gmail or .mac mail into mail.app via IMAP connections. My work email via exchange 2007 still works fine and all accounts are still functional via webmail.
The error message says "There may be a problem with the mail server or network. Verify the settings for account “MobileMe” or try again. The server returned the error: The connection to the server “mail.me.com” on port 993 timed out."
I've tried the following:
- Disabling ssl, but I receive the same message regarding port 143.
- Connecting via a neighbor's wireless, but still receive the same errors.
- Reinstalling the combo update to 10.6.3 rather than the standard update, but still receive the same errors.
Any advice on how get mail downloading again?
Thanks,
Bailey

As an update, I have tried deleting mail.app and reloading it from the Snow Leopard DVD. I then loaded the combo update to 10.6.3. Unfortunately, this did not resolve the issue. Once, there was enough access to the server to download message headers, but not full emails. This happened immediately after restarting mail.
Interestingly, the connections to the servers also time-out in Thunderbird. Could the update to 10.6.3 have had some impact on the usability of ports 993 and 143 that has nothing to do with updates to mail.app?
Thanks,
Bailey

Imap Time Out

Hello,
I reinstall after a HD Crash osx server with mail services, I think some things run because I can see the mail in queue but I can't connect any user !! I have a time out !
For each user I create I have the same problem from a mail client and the webmail.
Someone have an Idea ?
Thks

It was the number of simultaneous connection 0 by default !!

Import Email to Server via IMAP - time out

Hello,
I set up OSX Maverick Server 3.1.2. Everything works quite nicely.
I am having a client which uses the most recent mail.app on OSX Maverick.
This client is connected to the OSX Server which is in the same Gigbit Network.
Now I would like to copy all my emails from my previous account which are stored in my mail.app via IMAP to my OSX Server account.
When I copy the files the copy process ends and the error message is (e.g.):
133 messages could not be moved to the mailbox “Sent — OSX Server”
The connection to the server “server.mydomain.com” on port 143 timed out.
Can someone point me into the right direction on where I should look for a solution?
Help would be very much appreciated!
Kind Regards, Chris

Try breaking the task up into smaller pieces. Either all the messages will be imported, or you'll isolate one (or more) that's causing the failure.

Any advice as to why I'm getting Email Server Timeouts for my 2 email accounts (ports 993 & 110)?

Email Server Timeouts for my two email accounts:
For the time periods April 12-21, 2012 and April 27-present, 2012 I have been unable to access my email account at ***** through the pop server. The server returns them message "The connection to the server “*****” on port 110 timed out."
I have also had the same problem accessing my gmail account via IMAP, receiving the following message: "The connection to the server “imap.gmail.com” on port 993 timed out."
I used the Connection Doctor program connected to Apple Mail and received the following information:
Mail was able to connect to the internet.
Gmail: Could not connect to this Gmail IMAP server. Check your network connection and that you entered the correct information in the Account preferences. Also verify that the server supports SSL. If it does not, deselect the "Use SSL" checkbox in the Advanced tab of Account preferences.
BayanMail: Could not connect to this POP server. Check your network connection and that you entered the correct information in the Account preferences.
SMTP smtp.gmail.com:*****@gmail.com Connection and login to server succeeded.
*****Mail SMTP server: Connection to server succeeded; login not required.
Can you help me with this problem?
I am running OS 10.6.8
Mail 4.5

The Motorola Droid Razr has a camera that sets up the shot to take a quality picture so its not in an instant. My wife also doesn't like that feature but I believe in the settings you can disable some of those functions. You have to read the owners manual for optimal settings.
Now email sent from the native app that came with the phone is totally useless. If you have a email service like Gmail or Yahoo Mail or Outlook Email go to the google play store and use the stand alone app. I can tell you that when we email photos the best email app is GMail or Microsoft Outlook Mail.
I take a picture and then select Gmail and it attaches and sends with great speed and Outlook works this way also since the attachment size is greater than other email programs. Your local isp or even exchange server will not send such large attachments
And I agree those apps preloaded should be able to be removed. If I buy my phone I should say what I want on it. But alas unless you do some other methods you can find on the web those dumb apps will remain.
Good Luck

Mail (and other mail apps) suddenly giving server time-out error.

...though browser, webmail, iPhone and iPad connections via same router (whether wifi or powerline) are fine. Turning firewall off and disabling anti-virus makes no difference, so it looks like e-mail protocol. ISP has checked their end and no issues. A local expert doesn't know where to turn next - can anyone assist, as I need to have my regular e-mail client working to run my business.
Early 2008 iMac running Mountain Lion regularly updated, 4GB RAM.
Thanks,
Crispin

INITIATING CONNECTION Jun 01 20:21:49.337 -- host:shcp01.hosting.zen.net.uk -- port:995 -- socket:0x0 -- thread:0x7fd8d453f2b0
INITIATING CONNECTION Jun 01 20:21:49.338 -- host:pop3.live.com -- port:995 -- socket:0x0 -- thread:0x7fd8d35cf7f0
INITIATING CONNECTION Jun 01 20:21:49.338 -- host:mailhost.zen.co.uk -- port:25 -- socket:0x0 -- thread:0x7fd8d4300380
INITIATING CONNECTION Jun 01 20:21:49.338 -- host:smtp.live.com -- port:587 -- socket:0x0 -- thread:0x7fd8d424f170
INITIATING CONNECTION Jun 01 20:21:49.338 -- host:shcp01.hosting.zen.net.uk -- port:25 -- socket:0x0 -- thread:0x7fd8d47092e0
INITIATING CONNECTION Jun 01 20:21:49.339 -- host:mail.legacy-link.co.uk -- port:110 -- socket:0x0 -- thread:0x7fd8d4421a40
INITIATING CONNECTION Jun 01 20:21:49.359 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fd8d35cca80
CONNECTED Jun 01 20:21:49.428 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:995 -- socket:0x7fd8d357d8d0 -- thread:0x7fd8d453f2b0
CONNECTED Jun 01 20:21:49.434 [kCFStreamSocketSecurityLevelNone] -- host:mailhost.zen.co.uk -- port:25 -- socket:0x7fd8d3609880 -- thread:0x7fd8d4300380
CONNECTED Jun 01 20:21:49.447 [kCFStreamSocketSecurityLevelNone] -- host:shcp01.hosting.zen.net.uk -- port:25 -- socket:0x7fd8d357e660 -- thread:0x7fd8d47092e0
CONNECTED Jun 01 20:21:49.448 [kCFStreamSocketSecurityLevelNone] -- host:mail.legacy-link.co.uk -- port:110 -- socket:0x7fd8d45475d0 -- thread:0x7fd8d4421a40
READ Jun 01 20:21:49.459 [kCFStreamSocketSecurityLevelNone] -- host:mailhost.zen.co.uk -- port:25 -- socket:0x7fd8d3609880 -- thread:0x7fd8d4300380
220 smarthost03.mail.zen.net.uk ESMTP Exim 4.72 Sat, 01 Jun 2013 19:21:49 +0000
READ Jun 01 20:21:49.466 [kCFStreamSocketSecurityLevelNone] -- host:mail.legacy-link.co.uk -- port:110 -- socket:0x7fd8d45475d0 -- thread:0x7fd8d4421a40
+OK Dovecot ready.
READ Jun 01 20:21:49.468 [kCFStreamSocketSecurityLevelNone] -- host:shcp01.hosting.zen.net.uk -- port:25 -- socket:0x7fd8d357e660 -- thread:0x7fd8d47092e0
220-shcp01.hosting.zen.net.uk ESMTP Exim 4.80 #2 Sat, 01 Jun 2013 20:21:40 +0100
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
WROTE Jun 01 20:21:49.487 [kCFStreamSocketSecurityLevelNone] -- host:mailhost.zen.co.uk -- port:25 -- socket:0x7fd8d3609880 -- thread:0x7fd8d4300380
EHLO [192.168.0.11]
WROTE Jun 01 20:21:49.490 [kCFStreamSocketSecurityLevelNone] -- host:mail.legacy-link.co.uk -- port:110 -- socket:0x7fd8d45475d0 -- thread:0x7fd8d4421a40
CAPA
CONNECTED Jun 01 20:21:49.503 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:pop3.live.com -- port:995 -- socket:0x7fd8d3566de0 -- thread:0x7fd8d35cf7f0
READ Jun 01 20:21:49.510 [kCFStreamSocketSecurityLevelNone] -- host:mail.legacy-link.co.uk -- port:110 -- socket:0x7fd8d45475d0 -- thread:0x7fd8d4421a40
+OK
CAPA
TOP
UIDL
RESP-CODES
PIPELINING
STLS
USER
SASL PLAIN LOGIN
READ Jun 01 20:21:49.511 [kCFStreamSocketSecurityLevelNone] -- host:mailhost.zen.co.uk -- port:25 -- socket:0x7fd8d3609880 -- thread:0x7fd8d4300380
250-smarthost03.mail.zen.net.uk Hello [192.168.0.11] [217.155.46.20]
250-SIZE 134217728
250-ETRN
250-PIPELINING
250-STARTTLS
250 HELP
WROTE Jun 01 20:21:49.511 [kCFStreamSocketSecurityLevelNone] -- host:shcp01.hosting.zen.net.uk -- port:25 -- socket:0x7fd8d357e660 -- thread:0x7fd8d47092e0
EHLO [192.168.0.11]
WROTE Jun 01 20:21:49.531 [kCFStreamSocketSecurityLevelNone] -- host:mail.legacy-link.co.uk -- port:110 -- socket:0x7fd8d45475d0 -- thread:0x7fd8d4421a40
AUTH PLAIN
WROTE Jun 01 20:21:49.536 [kCFStreamSocketSecurityLevelNone] -- host:mailhost.zen.co.uk -- port:25 -- socket:0x7fd8d3609880 -- thread:0x7fd8d4300380
STARTTLS
READ Jun 01 20:21:49.542 [kCFStreamSocketSecurityLevelNone] -- host:shcp01.hosting.zen.net.uk -- port:25 -- socket:0x7fd8d357e660 -- thread:0x7fd8d47092e0
250-shcp01.hosting.zen.net.uk Hello dsl-217-155-46-20.zen.co.uk [217.155.46.20]
250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
READ Jun 01 20:21:49.551 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:995 -- socket:0x7fd8d357d8d0 -- thread:0x7fd8d453f2b0
+OK Dovecot ready.
READ Jun 01 20:21:49.557 [kCFStreamSocketSecurityLevelNone] -- host:mail.legacy-link.co.uk -- port:110 -- socket:0x7fd8d45475d0 -- thread:0x7fd8d4421a40
+
CONNECTED Jun 01 20:21:49.559 [kCFStreamSocketSecurityLevelNone] -- host:smtp.live.com -- port:587 -- socket:0x7fd8d4805720 -- thread:0x7fd8d424f170
READ Jun 01 20:21:49.562 [kCFStreamSocketSecurityLevelNone] -- host:mailhost.zen.co.uk -- port:25 -- socket:0x7fd8d3609880 -- thread:0x7fd8d4300380
220 TLS go ahead
WROTE Jun 01 20:21:49.569 [kCFStreamSocketSecurityLevelNone] -- host:shcp01.hosting.zen.net.uk -- port:25 -- socket:0x7fd8d357e660 -- thread:0x7fd8d47092e0
STARTTLS
WROTE Jun 01 20:21:49.576 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:995 -- socket:0x7fd8d357d8d0 -- thread:0x7fd8d453f2b0
CAPA
WROTE Jun 01 20:21:49.591 [kCFStreamSocketSecurityLevelNone] -- host:mail.legacy-link.co.uk -- port:110 -- socket:0x7fd8d45475d0 -- thread:0x7fd8d4421a40
CONNECTED Jun 01 20:21:49.614 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:p03-imap.mail.me.com -- port:993 -- socket:0x7fd8d43f4a50 -- thread:0x7fd8d35cca80
READ Jun 01 20:21:49.626 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:995 -- socket:0x7fd8d357d8d0 -- thread:0x7fd8d453f2b0
+OK
CAPA
TOP
UIDL
RESP-CODES
PIPELINING
USER
SASL PLAIN LOGIN
READ Jun 01 20:21:49.626 [kCFStreamSocketSecurityLevelNone] -- host:shcp01.hosting.zen.net.uk -- port:25 -- socket:0x7fd8d357e660 -- thread:0x7fd8d47092e0
220 TLS go ahead
READ Jun 01 20:21:49.630 [kCFStreamSocketSecurityLevelNone] -- host:mail.legacy-link.co.uk -- port:110 -- socket:0x7fd8d45475d0 -- thread:0x7fd8d4421a40
+OK Logged in.
READ Jun 01 20:21:49.645 [kCFStreamSocketSecurityLevelNone] -- host:smtp.live.com -- port:587 -- socket:0x7fd8d4805720 -- thread:0x7fd8d424f170
220 BLU0-SMTP45.phx.gbl Microsoft ESMTP MAIL Service, Version: 6.0.3790.4675 ready at Sat, 1 Jun 2013 12:21:49 -0700
WROTE Jun 01 20:21:49.655 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:995 -- socket:0x7fd8d357d8d0 -- thread:0x7fd8d453f2b0
AUTH PLAIN
WROTE Jun 01 20:21:49.677 [kCFStreamSocketSecurityLevelNone] -- host:mail.legacy-link.co.uk -- port:110 -- socket:0x7fd8d45475d0 -- thread:0x7fd8d4421a40
QUIT
READ Jun 01 20:21:49.699 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:995 -- socket:0x7fd8d357d8d0 -- thread:0x7fd8d453f2b0
+
READ Jun 01 20:21:49.705 [kCFStreamSocketSecurityLevelNone] -- host:mail.legacy-link.co.uk -- port:110 -- socket:0x7fd8d45475d0 -- thread:0x7fd8d4421a40
+OK Logging out.
WROTE Jun 01 20:21:49.708 [kCFStreamSocketSecurityLevelNone] -- host:smtp.live.com -- port:587 -- socket:0x7fd8d4805720 -- thread:0x7fd8d424f170
EHLO [192.168.0.11]
WROTE Jun 01 20:21:49.725 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:mailhost.zen.co.uk -- port:25 -- socket:0x7fd8d3609880 -- thread:0x7fd8d4300380
EHLO [192.168.0.11]
WROTE Jun 01 20:21:49.737 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:995 -- socket:0x7fd8d357d8d0 -- thread:0x7fd8d453f2b0
READ Jun 01 20:21:49.781 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:mailhost.zen.co.uk -- port:25 -- socket:0x7fd8d3609880 -- thread:0x7fd8d4300380
250-smarthost03.mail.zen.net.uk Hello [192.168.0.11] [217.155.46.20]
250-SIZE 134217728
250-ETRN
250-PIPELINING
250-AUTH PLAIN LOGIN
250 HELP
WROTE Jun 01 20:21:49.782 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:25 -- socket:0x7fd8d357e660 -- thread:0x7fd8d47092e0
EHLO [192.168.0.11]
READ Jun 01 20:21:49.789 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:995 -- socket:0x7fd8d357d8d0 -- thread:0x7fd8d453f2b0
+OK Logged in.
READ Jun 01 20:21:49.794 [kCFStreamSocketSecurityLevelNone] -- host:smtp.live.com -- port:587 -- socket:0x7fd8d4805720 -- thread:0x7fd8d424f170
250-BLU0-SMTP45.phx.gbl Hello [217.155.46.20]
250-TURN
250-SIZE 41943040
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-TLS
250-STARTTLS
250 OK
WROTE Jun 01 20:21:49.813 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:mailhost.zen.co.uk -- port:25 -- socket:0x7fd8d3609880 -- thread:0x7fd8d4300380
QUIT
READ Jun 01 20:21:49.823 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:25 -- socket:0x7fd8d357e660 -- thread:0x7fd8d47092e0
250-shcp01.hosting.zen.net.uk Hello dsl-217-155-46-20.zen.co.uk [217.155.46.20]
250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-AUTH PLAIN LOGIN
250 HELP
WROTE Jun 01 20:21:49.835 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:995 -- socket:0x7fd8d357d8d0 -- thread:0x7fd8d453f2b0
QUIT
WROTE Jun 01 20:21:49.847 [kCFStreamSocketSecurityLevelNone] -- host:smtp.live.com -- port:587 -- socket:0x7fd8d4805720 -- thread:0x7fd8d424f170
STARTTLS
WROTE Jun 01 20:21:49.874 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:25 -- socket:0x7fd8d357e660 -- thread:0x7fd8d47092e0
AUTH PLAIN (*** 48 bytes hidden ***)
READ Jun 01 20:21:49.882 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:995 -- socket:0x7fd8d357d8d0 -- thread:0x7fd8d453f2b0
+OK Logging out.
READ Jun 01 20:21:49.920 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:25 -- socket:0x7fd8d357e660 -- thread:0x7fd8d47092e0
235 Authentication succeeded
READ Jun 01 20:21:49.935 [kCFStreamSocketSecurityLevelNone] -- host:smtp.live.com -- port:587 -- socket:0x7fd8d4805720 -- thread:0x7fd8d424f170
220 2.0.0 SMTP server ready
WROTE Jun 01 20:21:49.954 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:shcp01.hosting.zen.net.uk -- port:25 -- socket:0x7fd8d357e660 -- thread:0x7fd8d47092e0
QUIT
READ Jun 01 20:21:49.990 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:pop3.live.com -- port:995 -- socket:0x7fd8d3566de0 -- thread:0x7fd8d35cf7f0
+OK BLU0-POP360 POP3 server ready
WROTE Jun 01 20:21:50.016 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:pop3.live.com -- port:995 -- socket:0x7fd8d3566de0 -- thread:0x7fd8d35cf7f0
CAPA
READ Jun 01 20:21:50.085 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:p03-imap.mail.me.com -- port:993 -- socket:0x7fd8d43f4a50 -- thread:0x7fd8d35cca80
* OK [CAPABILITY nk11p00mm-iscream003 1Q49 XAPPLEPUSHSERVICE IMAP4 IMAP4rev1 SASL-IR AUTH=ATOKEN AUTH=PLAIN] iSCREAM ready to rumble (1Q49:17990) nk11p00mm-iscream003
WROTE Jun 01 20:21:50.102 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:p03-imap.mail.me.com -- port:993 -- socket:0x7fd8d43f4a50 -- thread:0x7fd8d3306920
1.239 AUTHENTICATE ATOKEN MTA0MjMxNzgwNgAxMDQyMzE3ODA2AEFRQUFBQUJScEh6Y0NvTngzS1E5bzNOQXJ0WDdHeWxvZ2IwQ0h zYz0=
READ Jun 01 20:21:50.105 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:pop3.live.com -- port:995 -- socket:0x7fd8d3566de0 -- thread:0x7fd8d35cf7f0
-ERR unrecognized command
WROTE Jun 01 20:21:50.135 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:pop3.live.com -- port:995 -- socket:0x7fd8d3566de0 -- thread:0x7fd8d35cf7f0
USER ****
READ Jun 01 20:21:50.221 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:pop3.live.com -- port:995 -- socket:0x7fd8d3566de0 -- thread:0x7fd8d35cf7f0
+OK password required
WROTE Jun 01 20:21:50.236 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:pop3.live.com -- port:995 -- socket:0x7fd8d3566de0 -- thread:0x7fd8d35cf7f0
PASS ******
READ Jun 01 20:21:50.271 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:p03-imap.mail.me.com -- port:993 -- socket:0x7fd8d43f4a50 -- thread:0x7fd8d3306920
1.239 OK [CAPABILITY XAPPLEPUSHSERVICE IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS CHILDREN BINARY UNSELECT SORT CATENATE URLAUTH LANGUAGE ESEARCH ESORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES CONDSTORE ENABLE CONTEXT=SEARCH CONTEXT=SORT WITHIN SASL-IR SEARCHRES XSENDER X-NETSCAPE XSERVERINFO X-SUN-SORT ANNOTATE-EXPERIMENT-1 X-UNAUTHENTICATE X-SUN-IMAP X-ANNOTATEMORE XUM1 ID IDLE] User crispinellison logged in
WROTE Jun 01 20:21:50.317 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:p03-imap.mail.me.com -- port:993 -- socket:0x7fd8d43f4a50 -- thread:0x7fd8d3306920
2.239 ID ("name" "Mac OS X Mail" "version" "6.3 (1503)" "os" "Mac OS X" "os-version" "10.8.3 (12D78)" "vendor" "Apple Inc.")
WROTE Jun 01 20:21:50.361 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.live.com -- port:587 -- socket:0x7fd8d4805720 -- thread:0x7fd8d424f170
EHLO [192.168.0.11]
READ Jun 01 20:21:50.449 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.live.com -- port:587 -- socket:0x7fd8d4805720 -- thread:0x7fd8d424f170
250-BLU0-SMTP45.phx.gbl Hello [217.155.46.20]
250-TURN
250-SIZE 41943040
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-AUTH LOGIN PLAIN
250 OK
WROTE Jun 01 20:21:50.468 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.live.com -- port:587 -- socket:0x7fd8d4805720 -- thread:0x7fd8d424f170
AUTH PLAIN (*** 40 bytes hidden ***)
READ Jun 01 20:21:50.475 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:p03-imap.mail.me.com -- port:993 -- socket:0x7fd8d43f4a50 -- thread:0x7fd8d3306920
* ID NIL
2.239 OK Completed
WROTE Jun 01 20:21:50.525 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:p03-imap.mail.me.com -- port:993 -- socket:0x7fd8d43f4a50 -- thread:0x7fd8d4300380
3.239 LIST "" ""
READ Jun 01 20:21:50.679 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:p03-imap.mail.me.com -- port:993 -- socket:0x7fd8d43f4a50 -- thread:0x7fd8d4300380
* LIST (\Noselect) "/" ""
3.239 OK Completed
WROTE Jun 01 20:21:50.699 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:p03-imap.mail.me.com -- port:993 -- socket:0x7fd8d43f4a50 -- thread:0x7fd8d4300380
4.239 LOGOUT
READ Jun 01 20:21:51.012 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:pop3.live.com -- port:995 -- socket:0x7fd8d3566de0 -- thread:0x7fd8d35cf7f0
+OK mailbox has 1 messages
WROTE Jun 01 20:21:51.029 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:pop3.live.com -- port:995 -- socket:0x7fd8d3566de0 -- thread:0x7fd8d35cf7f0
QUIT
READ Jun 01 20:21:51.045 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.live.com -- port:587 -- socket:0x7fd8d4805720 -- thread:0x7fd8d424f170
235 2.7.0 Authentication succeeded
WROTE Jun 01 20:21:51.066 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.live.com -- port:587 -- socket:0x7fd8d4805720 -- thread:0x7fd8d424f170
QUIT
READ Jun 01 20:21:51.117 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:pop3.live.com -- port:995 -- socket:0x7fd8d3566de0 -- thread:0x7fd8d35cf7f0
+OK mailbox unchanged, POP3 server signing off
<Email Edited By Host>

Email time out

Hi,
We have DSL and a mix of a PC, and a Mac running Leopard, using the router via wireless connection. Internet works fine on both. Outlook works fine on the PC. The Mac mail program worked fine up until a week ago.
The Mac email program will no longer send or receive email. Attempting to take my email accounts on-line gives a rotating pinwheel in the email program and an exclamation mark to the side. Clicking the exclamation mark gives back the message "There may be a problem with the mail server or network. Verify the settings for acount "Gmail" or try again. The server returned the error: The connection to the server imap.gmail.com" on port 993 timed out." My niece brought her Mac laptop over, and connected to the internet fine, but has the same problem with the email program.
This problem did coincide with moving the modem to another location in the house. Unfortunately, Verizon technical assistance was of no help, and transferred me to Apple. However, this seems to be connection related, and not computer related.
Thanks for any help.
DWN

Hello Dwn_Jkm,
I just read your post and I do apologize for any frustration. However, the error that you received "The connection to the server imap.gmail.com" on port 993 timed out." is advising that there was an error when trying to access Google's email server. There could be many reasons that this is not working properly on the program MacMail.
Here is a useful link in regards to email:
https://www22.verizon.com/ForYourHome/VZRepair/vziha/Service.aspx?ihaweb=EmailFix
Thanks,
Shamika_VZ
Verizon Support
Notice: Content posted by Verizon employees is meant to be informational and does not supersede or change the Verizon Forums User Guidelines or Terms or Service, or your Customer Agreement Terms and Conditions or Plan.

Server timed out on part 993

My wife and I have an iMac. I am the administrator. Her mail works just fine. I can neither mail out nor receive messages. In the Doctor window on my side is says server timed out on port 993. I have repaired permissions and reset the preferences and nothing has helped. Please help. I have a Leopard install disk if that would take care of my problem. Things look right under accounts on my side.
Thank you,
Carl

Do either you or your wife have any other accounts which use port 993? If not (ie, this is the only account which uses it, and it's not working for you), I'd suspect that your ISP may be blocking that port, which can happen.
Non-SSL email sends your username and password "in the clear" to your mail server. This means that, in theory, a man-in-the-middle attack (someone listening in on your traffic) could intercept and find your login information. SSL encrypts the login between you and your server. You should use SSL whenever your mail providers and ISP allow it.
Matt

Mail 5.1 port 993 time out

Hi
since 2 days ago , I face problems in my mail 5.1
mail can't connect to prt 993 , $ get me time out error , I try to recreate my account & mail get me "The Google IMAP server “imap.gmail.com” is not responding. Try checking the network connection, and that the server name is correct. Otherwise, the server might be temporarily unavailable. If you continue, you might not be able to receive messages."
What should I do?

gmail imap won't import new emails.
i've tried port 143, and 993.
checked ssl and not ssl.
checked password and settings.
went through connection doctor, and it's all green.
gmail account imap settings are right.
i am able to sent out a test email, which reaches my account on the gmail website. but it won't load on apple mail 4.2.
running snow leopard 10.6.2
sigh read through a few forums and all anyone can say is to reload the account.
there must be an easier way.

The connection to the server on port 993 times out...

When I attempt to delete mail or move mail to my trash I receive the following error message:
"""The message could not be moved to the mailbox “Trash — iCloud”
the connection to the server :p01-map.mailme.com” on port 993 times out"""
I have never seen this before, anyway to correct it?

Regarding the iPhone (5 in my case) it works relatively well with charter.net IMAP and smtp functions at mobile.charter.well. But does occassionally have sync problems as well.
To fix the problem with my MacBook Pro Mail app, the Apple senior tech could not determine the problem, so he told me to reinstall the app. To do this I had to run the Archive and Install feature of the recovery disk (hold down cmd-r on reboot). Of course this two two hours to complete, as well as run software updates. And it did not fix the sync problem.
So??? This one has me stymied!
Oh, one other input. The email app "Thunderbird" works perfectly with charter.net IMAP and its smtp, syncs every time!

Port 993 time out server

Im already sick and tired on this subject - called my ISP the ysay i need to talk to apple
I called apple and all they tell me is to look at the email set up walk through as if I was a total idiot I told them I done that already, ok then delete your email acount (mac account) and set up again - I've done that already many times as well - theres no solution really here from apple and this has been going on for 3 weeks now -
Why can't apple come up with A SOLUTION to this man - Iam using an apple email and still the crap doesn't work
this is really frustrating
AND STOP SENDING ME BACK TO THOSE STUPID TUTORIALS ON HOW TO SET UP AN EMAIL ACCOUNT OK THE THING IS THAT I NEVER MADE ANY CHANGES IN THE FIRST PLACE THE STUPID ERROR MESSAGES JUST SHOWED UP ON MY IMAC AND MACBOOK
NOT A HAPPY APPLE CUSTOMER HERE !!!!

cisco911 wrote:
Im using an Imac with email 4.5
Could Mail 4.5 be the problem? For over a year I use a G-Mail account and always noticed that it takes ages to send mail from my iMac with Snow Leopard (uses Mail 4.5). On my MacBook with (Mountain) Lion and my Android tablet, the mail is send instantly.
This week I started using my own mailserver in my private network. Mail 4.5 reads the IMAP structure perfectly but when transfering a file to it, I also get the timeout error for port 993. My two other computers that are running now under Marverics give no problem.
So two accounts giving problems on the same computer, rules out a wrong mail setup.

Out Going Mail issue - Port 993 Time connecting to Exchange Server 2007

Help Needed,
Issue: Outgoing mail stalls receiving 993 timeout issue

Outgoing mail shouldn't be using port 993, that's an incoming mail port (IMAPS). Outgoing should be using either port 25, 587, or in some cases, 465.

Thunderbird email client times out making IMAP and POP3 connections to gmail and hotmail.

After autoconfiguring several gmail accounts with Thunderbird, and then using them, they stopped working after I switched to Verizon High Speed DSL. All of the accounts time out while trying to get email.   Non list an error. While trying to auto configure a hotmail account, it failed during password loggin.
Disabled Windows Firewall
Disabled Norton Firewall
Disabled modem-router firewall
checked IMAP settings in Thunderbird.
deleted and then reautoconfigured the accounts to reset the passwords.
enabled IMAP manually in gmail and POP3
checked SMTP ports and IMAP default port numbers
checked for normal password
checked for SSL/TSL text
Checked with Verizon support who said that they don't help Thunderbird clients.
Tried logging in manually to all of the accounts to make sure the passwords and usernames were correct ...works.
help! "connection to server timed out"

Not exactly the same, but I am pretty sure the fix will be the same.
give it a whirl and let us know.
Solution for sending MS Outlook and SMTP e-mail through Verizon FIOS for GoDaddy e-mail
The FIX...I had to log onto the xxxxxxxx(at)verizon.net e-mail account via the WEBMAIL version for Verizon.
I then went to Options-->More Options on the top, right menu.
Go to the Accounts menu on the left.
Click Add Account button toward the top.
I only entered information for Sending Mail.
     Account name (any name you like...I called it GoDaddy)
     From Name = my display name
     e-mail address = my GoDaddy e-mail address
     I then moved my cursor to the username field in the Receiving Mail just so my cursor wasn't in the e-mail address field anymore.
Verizon couldn't even help me with this. This should be a standard check for them whenever they receive a call for SMTP issues. I think they are trying to get everyone to use their (at)verizon.net e-mail account as their primary account. This will help them retain or gain future business. I think it's bad for business overall.
==========
Note the "Test Account Settings..." button failed on the test send of a message, but all other tests passed fine. My messages are sent fine even with this part of the tests failing.
The above is true for a lot of third party email providers (not programs but email providers)

Imap server times out

Ever since I updated to Mavericks on one of my imap email server accounts I occasionally get this popup:
I notice when I open Mail an exclamation mark next to the name of my imap email account and upon clicking on it I get above popup. Which is in Dutch but translated roughly to:
[name email account] cannot be opend.
Time out of the connection with server 'imap.emailaccount.com' through port 143.
The exclamation mark generally goes away when I click the 'receive email' button or restart Mail.
I deleted the account and set it up again to reset it. All the values are correct as checked with my ISP.
What is this message about and how can it be fixed? It doesn't always does it. Most of the time it just works. Then every now and then I get this exclamation mark so I know something is wrong and when I click on it above screenshot. Then it goes away upon clicking on the 'receive email' button or when restarting and it continues to work again. So it's not all the time.

I am getting the same error occassional also and I am running OSX server 10.9. When I checked the mail log there is nothing that points me to a possible cause.
This is my Mail Server log:
Nov 14 09:21:22 imap-login: Info: Disconnected (client didn't finish SASL auth, waited 90 secs): user=<>, method=PLAIN, rip=192.168.10.1, lip=192.168.10.201, TLS
Nov 14 09:21:22 imap(pid 51947 user courtney.currie): Info: Connection closed in=0 out=432
Nov 14 09:22:29 imap-login: Info: Disconnected: Inactivity during authentication (disconnected while authenticating, waited 163 secs): user=<>, method=CRAM-MD5, rip=::1, lip=::1, TLS
Nov 14 09:22:42 imap-login: Info: ID sent: name=Mac OS X Mail, version=7.0 (1822), os=Mac OS X, os-version=10.9 (13A603), vendor=Apple Inc.: user=<>, rip=192.168.10.136, lip=192.168.10.201, TLS
Nov 14 09:22:48 imap-login: Info: Disconnected (no auth attempts in 5 secs): user=<>, rip=::1, lip=::1, TLS: Disconnected
Nov 14 09:22:49 imap: Info: Server shutting down. in=1896 out=278534
What I have been doing is to restart the mini-mac server and then the matter is resolved, but it keeps re-occuring.

Time out function in VISA configure serial port vi

I have some doubts regarding the time out functionality of "VISA configure serial port vi":
1) I have set the time out value as 10s while initializing the port using this vi. Does this mean that for any Rx operation happening on the serial port, it will wait for 10s for the data to be received?
2) Is this waiting functionality also valid on "bytes at port" vi which I am using before reading the port data?
Because in my application, the control at serial port is actually not waiting for 10s and is coming out before the desired time out (10s). Do I need to set this time out anywhere else apart from initialization at "VISA configure serial port vi"??
Can anyone please tell the steps to set this timeout for the serial port?
Thanks in advance!

1. A read will return when the first of the following is satisfied:
a. The number of bytes at byte count has been received.
b. The termination character (if enabled) has been received.
c. An error is detected.
d. The timeout time has elapsed.
I am not sure what happens if handshaking is enabled and the other device pauses communication.
2. No. Bytes at port returns immediately. This is a status check and it would not make sense for a timeout to apply.
Without seeing your code and the data the remote device is sending, we can only guess. My first guess would be that you have termination characters enabled (default) and a termination character appears in your data.
Lynn

IMAP time out on port 993

Similar Messages

Maybe you are looking for