Feb 14, 2018 - My passwords, when entered manually work perfectly. But it won't keep the password in the password box. I tell it to save to my keychain, but it. Search for the e-mail service (ie, the server name) of the account you have configured in Outlook. Select the displayed keychain entry, and press the Delete key to remove it. When finished, launch Outlook again, and when prompted, supply your password for the server. After applying the Yosemite 10.10.5 update and Security Update 2015-004 (1.0), my installation of Outlook 2011 prompts me for a password every time I check for mail. I have tried repairing Keychain Access a few times (on Verify, it says there is never a problem) and deleting/recreating the keychain login entries for Outlook, but I continue to be prompted to reenter my credentials: After entering the credentials, I show as connected and can send/receive all my mail. There is also a login entry displayed in Keychain Access. But the prompt still appears on every send/receive. I have seen of adding an additional backslash to the beginning of the domain (i.e. Domain user instead of domain user ) but doing so returns a bad user/pass error. The 10.10.5 update description says it 'improves compatibility with certain email servers when using Mail' - thinking this might be a clue? My coworker's mac (which hasn't been updated) does not have this issue, and my iPhone and Win7/Outlook 2007 installs are receiving mail from the same account with no login problems. Mail server settings have not changed (I manage it). EDIT Reviewing the keychain entry after getting the wrong credentials prompts, I see that the username has been changed from domain username to [email protected] but the prompt keeps coming up suggesting domain username. (Attempting [email protected] fails with bad user/pass error.) The change to the keychain entry occurs when relaunching Outlook or after a period of time. Thanks for the advice - I actually did play around with turning on/off autodiscover but I had a few things wrong (which I will edit in my original post) - my coworker with the same setup did in fact have the same problem with her installation. The connection string changes were a red herring. ![]() The problem had to do with a public mail folder in Exchange that had some permissions issues. Known issue from M$ and they're apparently working on a patch. Only affects Exchange 2013 installs that were migrations from 2010. – Dec 26 '15 at 20:30 •.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |