Skip navigation

Apple Mail in 10.7.4 with Mac OS X Server 10.6.8

8755 Views 18 Replies Latest reply: Nov 14, 2012 8:14 AM by silverdoc RSS
1 2 Previous Next
Michael_Lehn Calculating status...
Currently Being Moderated
May 14, 2012 2:18 AM

Can it be that Mail in Mac OS X 10.7.4 is broken?  While the Mail client (Version 5.2 (1278)) works fine with most IMAP servers it does not with the IMAP on my Mac OS X Server 10.6.8.  Other clients from iOS devices and older versions of Mail still work fine.  Alos, if I use Postbox I can perfectly use my IMAP account on the Xserve.

 

Looking at the log-file it seems that the server doesn't get certain information like the login-name.  Here a snippet from the log-file (one connection from an iOS is working another fails):

 

May 14 07:15:52 apfel com.apple.securityproxy_mail[364]: V1:IMAP:ACCESS[client:xx.xx.xx.xx:49577, proxy:xxx.xx.xx.xx:999, server:xxxxx.xxxxxxxx.xxxxx.xx:993, connected_secs:1, user:xxxxx, client-authmethod:IMAP-LOGIN, proxy-authmethod:CRAM-MD5, client-transport:ssl, server-transport:ssl, state:server-authorized, result:OK. Connection was closed cleanly.]

May 14 07:20:52 apfel com.apple.securityproxy_mail[364]: V1:IMAP:ACCESS[client:xx.xx.xx.xx:52652, proxy:xxx.xx.xx.xx:999, server:xxxxx.xxxxxxxx.xxxxx.xx:993, connected_secs:180, user:, client-authmethod:, proxy-authmethod:, client-transport:ssl, server-transport:ssl, state:proxy-connected, result:BAD. User not authorized by proxy server. No valid auth method from client. Verify that client and server are configured for mobile access. Connection was closed cleanly.]

 

 

Note that I am using the mobile access server so that users from outside connect (e.g.) to port 999 and it gets internally forwarded to the IMAP port 993.  This is certainly not the problem.   I get the same problem when I directly connect with 993.  And anyway, no other mail cleint has a problem!

 

 

Edit:  A year a ago I had a smiliar problem.  However, it was the way around.  The mail client on the iPhone caused exactly this problem while the mail clients on Mac OS X worked fine.  So just lookup the guy who was fixing the mail client on iOS recently ;-)

XServe, iMac, MacBook Pro, ..., Mac OS X (10.6.2)
  • MrHoffman Level 6 Level 6 (11,745 points)
    Currently Being Moderated
    May 14, 2012 10:56 AM (in response to Michael_Lehn)

    I'm using 10.7.4 clients with 10.6.8 server and with port forwarding (though not TCP to 999 to 993), and it works fine.   

     

    Keep digging. 

     

    With SSL involved, I always check the certificates, but that's not the trigger here. 

     

    What authentication mechanisms are implemented on the client and on the server, and what's in the authentication logs? 

     

    Did you possibly end up with a bogus entry in the keychain?  (Sometimes removing the passwords and re-adding them will clear this.)

  • Henry Mac Level 1 Level 1 (0 points)

    I have exactly the same problem. It was ok before but with the latest update something broke. Older osx clients and ios clients work ok. If I bypass the proxyserver when I am on the local network and go directly to the server ip address it works again. So something with authenticating to the mobile access server doesn't work anymore. I go from port 5993 to 993.

     

    May 15 00:16:35 soundbox com.apple.securityproxy_mail[4574]: V1:IMAP:ACCESS[client:xx.xx.xxx.xxx:56449, proxy:xxx.xxx.x.xx:5993, server:xxx.xxx.x.xx:993, connected_secs:0, user:, client-authmethod:, proxy-authmethod:, client-transport:ssl, server-transport:ssl, state:proxy-connected, result:BAD. User not authorized by proxy server. No valid auth method from client. Verify that client and server are configured for mobile access. Connection was closed cleanly.]

     

    Message was edited by: Henry Mac

  • MrHoffman Level 6 Level 6 (11,745 points)
    Currently Being Moderated
    May 14, 2012 4:09 PM (in response to Henry Mac)

    Y'all are running mail through a proxy server?  If so, can that be eliminated?

  • Henry Mac Level 1 Level 1 (0 points)
    Currently Being Moderated
    May 14, 2012 4:28 PM (in response to MrHoffman)

    Ah sorry, when talking about the proxy server I mean the mobile access server. So yes, the mail app can connect directly to the imap server but not through the mobile access server anymore.

  • Henry Mac Level 1 Level 1 (0 points)
    Currently Being Moderated
    May 14, 2012 5:24 PM (in response to MrHoffman)

    I turned off the firewall on the client, router and server. No difference. Also routed from 993 to 993 and that didn't work. If I open port 993 on the firewall I can connect from an external ip address directly to the imap server. Also connecting from the local network to the mobile access server I get the BAD result.

  • David Tschudi Level 1 Level 1 (10 points)

    Same symptom in our School.

    We have a kerio connect mail server behind a proxy Mobile Access 10.6.8.

    IMAP mail account with Mail.app doesn't work with 10.7.4.

    Worked if I bypass the Mobile Access server and connect the IMAP account directely to the Kerio connect server.

     

    Opened a call the 10 mai to Apple.

    No news since there…

     

    I called first the server Help Desk.

    I explained twice my problem during 15 minutes.

    After that the Apple agent told me that he can't register my problem because Mobile Access Services was not an Apple products…

    Don't know if I had to laugh or cry…

     

    After that redirect me to the OS X client Help Desk because it was not a server problem for him…

  • pamadeo Calculating status...

    Well, after suffering through this same problem for quite a while, I started doing some digging to see what I could find.

     

    I went to Terminal, and used openssl to see if I could get any error messages that would help.  So, the Terminal command is:

     

    openssl s_client -connect <mobile access server>:993

     

    This actually connects, gives a bunch of info about the server, and ends up returning "* OK Dovecot ready."

     

    Wow!  We're actually connecting through the Mobile Access Server to the internal IMAP server.  Good so far.

     

    So, issue the IMAP login:  "a login <username> <password>"

     

    And it just hangs.....  I terminated the openssl session, VPN'd in to the internal network and checked the Mobile Access Server mail logs.  Same error - the user and authmethods are blank.

     

    No error messages on the client side, so being stuck, I tried to find anyone with a similar issue just generically with dovecot and openssl.

     

    I found an article through Google where someone had the exact same problem trying to connect to GMail.  http://superuser.com/questions/134924/manually-accessing-gmail-via-imap

     

    The answer to the problem was that the IMAP server only responds to lines ending with <CRLF>.  Trying that article's suggestion, I issued in Terminal this command:

     

    openssl s_client -crlf -connect <mobile access server>:993

     

    Same information about the server as before, and the same "* OK Dovecot ready." message.

     

    Tried the login command again, "a login <username> <password>", and this time got "a OK Logged in."

     

    And from there, I could select the Inbox, etc.

     

    So it looks like the CRLF is the source of the issue, but I have no idea how to make Mail.app do this correctly.  I also don't know why it's only a problem when going through the Mobile Access server; if I openssl while I'm on the internal network, I don't need the -crlf switch for it to work.

     

    Hopefully this gets someone with more experience onto the right track to fixing the problem.

  • David Tschudi Level 1 Level 1 (10 points)
    Currently Being Moderated
    Jul 19, 2012 12:35 AM (in response to Michael_Lehn)

    My case opened the 10 may about this subject is always open.

    In fact I don't know if he is always open.

    No news since there… Sent an email the 27 june to have some news, but no answer.

    I have also little hope that the 10.7.5 will correct it.

     

    So Apple what have we to do now:

    – Staying in the 10.7.3 for the rest of our life?

    – Remove our Mobile Access Server?

     

    We are waiting for answer.

     

    Is there somebody who tested the Mail.app 10.8 with Mobile Access?

  • David Tschudi Level 1 Level 1 (10 points)

    Tested it with Mail 6.0 under 10.8, same results, doesn't work…

1 2 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.