Hello, I recently started using openchange as a client through evolution to connect to an exchange server. It works well, thank you for the hard work! One thing that isn't working is notification of new mail. I began looking into why, but was uncertain how notification was supposed to work, so wasn't sure where the problem lies.
The test program test_asyncnotif that comes with openchange calls RegisterAsyncNotification to receive notifications of new mail, and I do indeed see this function block, then return once new mail arrives, and test_asyncnotif does what I expect. When I run the openchangeclient program as "openchangeclient -m --notifications", the way I read the help, I expect it to dump the mailbox to the console, block until new mail arrives, then do something (looks like just exit from the code), however it doesn't do that. It dumps the contents of the mailbox to the console, then it blocks, but it never unblocks, even when new mail arrives. Looking through the code, I see that it doesn't call RegisterAsyncNotification like test_asyncnotif, but instead calls RegisterNotification/Subscribe/MonitorNotification. Evolution-mapi calls the same sequence of RegisterNotification/Subscribe/MonitorNotification, and has the same problem of not being notified when new mail arrives. So I was wondering what the expected usage is. Are both of these sequences (RegisterAsyncNotification and RegisterNotification/Subscribe/MonitorNotification) valid methods to block a thread until new mail arrives and I should debug into why the second sequence isn't working, or am I misunderstanding what "openchange -m --notifications" is supposed to do, and it isn't really trying to block waiting for new mail? Thank you, Aaron _______________________________________________ devel mailing list devel@lists.openchange.org http://mailman.openchange.org/listinfo/devel
