Yosemite Server Mail GSSAPI Error

I'm seeing the same thing. You'll find some information here.

http://blog.smalleycreative.com/administration/fixing-openldap-authentication-on -os-x-lion/

One thing I've noticed is the users configured on the server v4, that came along in the upgrade to 10.10, behave like imported contacts. I can't reset their passwords, for example. So my next step is to create a new user on the server and check to see if the error under discussion occurs. If not, I guess we'll have to rebuild out OpenDirectory database, which sounds like a drag.

Alan,

One thing I have noticed, you can not change the users passwords for OD users through the Server v4 interface unless you use the filter at the top and select "Local Network Users" then you will be able to change passwords. This is an odd behavior that caused me to rebuild more than a couple of times.

Also, once the "Local Network Users" is selected, you may need to unlock the lock a the bottom of that screen that appears with the diradmin password.

Dan

Hi,

maybe it helps or not, I solve a other performance problem which is more related to the mailbox speed but this error on client side is gone afterwards:

In Yosemite there is still also a problem with the automatic settings detection in Mail.

That means that the application try's to find a working authentication mechanism in combination with different ports and encryption.

So far so good, this feature would be okay but the application never stops to do that. So we are shortly connected but the connection becomes invalid again.

This leads to performance issues and the application becomes very slow!

If you refer your client log file maybe you can see some "Failed to start the SASL connection" issues (coming from Mail.app).

In case that you are running a OS X Server which is used by Mail you will see in /var/log/mail* /Library/Logs/mail* various login failures. In case that you have enabled the Adaptive Firewall it can be happen that your IP is blocked for 15 minutes.

Of course this must not be a issue for everyone I believe it strongly depends on your email server / provider which auth. stuff is supported or enabled.

To solve it:

1.) Open the Mail Preferences

2.) Goto "Accounts" and select your Provider/Account

3.) Klick Enhanced (the last right tab)

4.) Disable the automatic settings detection (first checkbox)

5.) In case you didn't enable "MailDrop" 😀

This works in Mail 8.1 on Yosemite 10.10.1

Hi,

I also saw a lot of "Failed to start the SASL connection" messages in the log.

After disabling the automatic settings detection in Mail 8.1 (Yosemite 10.10.1) as proposed they are gone.

In addition some other strange mail problems with "intelligent folders" also disappeared.

Thanks for the solution.

Wolfgang

Just to add to Powercores good advice, in OS X 10.10.1 (and I'd image 10.9.x) you may find these log messages and more in the OS X mail.application by enabling the mail logging in the applications (see next) that will write diagnostics to ~/Library/Containers/com.apple.mail/Data/Library/Logs/Mail/20yy-mm-dd_mail_component_name.log

These logs can be (and ought to be) cleaned out also. These logs are very verbose to disable the logging when you don't need to see.

To enable the mail.app logging is very straight forward using the mail.app application menus/Window/Connection Doctor. In the pane, click on Log connection Activity.

You might utilise the "Show Logs"button to navigate to the mail component log files.

Use /applications/utilities/console.app to view.

Post your results for other to see.

HTH

Warwick

Hong Kong