Description of problem: After installed new version evolution-data-server from here http://koji.fedoraproject.org/koji/taskinfo?taskID=3858571 when I try refer to my global address book on Exchange server my Domain account is blocked. This morning I rolled back to to 3.3.91 version, and the whole day is not account locks.
That build contains patch from bug #799820, otherwise is the same as 3.3.91. Below is currently my last comment there. Could you try to ask your admins for the below answer, please? I really do not see a reason why your domain account should be locked, but if they give us a clue, then we can follow-up with investigation. > > Hmm, how do you "refer to your GAL"? > Two ways: > 1) Open contacts. > 2) When fill "To:" field name in new letter. > > Seems this is another issue. With downgraded evolution-data-server my account > block's too. And at the time of block coincides with the moments when I reffer > to GAL. I agree, it should be just a coincidence, because this change doesn't influence your address books, at least not directly. Do you know the reason why they blocked your account? The access to GAL is all changed in evolution-mapi 3.3.91 (and few versions below), same as for contacts, but it would surprise me if they block you only because of NSPI searches in GAL. The interesting part is that the NSPI connection is always done, together with EMSDB connection, thus this might not be due to connection itself. I prefer to open a new bug report for this, to not steal the original report.
Problems occurs also with downgraded evolution-data-server. Seems problems starts since 3.3.91 version. And the account is locked immediately after login. Evolution connect with my password in the background immediately after login?
Can I save it to log file?
It can connect after login within evolution-alarm-notify process, where it probably opens your calendar (those chosen to, in Edit->Preferences->Calendars and Tasks, tab Reminders). Apart of it it may not connect to your MAPI server, maybe only if gnome-shell tries to gather your current appointments and tasks. Check which processes are running after login, namely any with 'evolution' in its name. For example, you can run evolution itself with more detailed debugging by invoking it like this: $ LIBMAPI_DEBUG=15 evolution &>/tmp/evo.log Note such log contains pretty much private information and should not be shared in public. What I was looking for was a notice from your server admins what the reason to lock your account is. It may help the most, probably, as it's what server thinks about that what evolution-mapi does.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.