Hi, We have been using Dovecot 1.0 to serve Maildir format over IMAPs to a client with an office of around 30 people, and a remote office of 10, all using Outlook 2003. While users in the base office (location of server) are not having issues with the server users in the remote office are often having problems with Outlook freezing, or not being able to connect. The dovecot log shows them logging in, but users report not being able to open any mail. We are having similar problems with 2 users that are often on 3G cards, in that the headers download but when they try to open the file it gives the 'must be online to download the message' error, even though they are still connected to their 3G. The net connection for the server is 2mb sdsl, which I have tested myself (using thunderbird on linux!) and achieved good throughput and reliable mailbox navigation. Is there any Outlook work arounds we could be using? (currently using idle timeout work around) Any help is very much appreciated. Thanks, Mark
I can confirm that I am having the same problem with my Outlook freezing and intermittently not being able to logon, but I don't know how to fix it. If you don't mind, I'd like to ask a few questions to try to isolate the problem. What version are you using? I'm using 1.0-rc6. Are you using SSL? If so, on all connections or just some (i.e. the remote ones)? What are you using for authentication? PAM? What is your dovecot server using for 'ioloop'? What is your dovecot server using for 'notify'? You can get those last two parameters from 'dovecot --build-options' (or something like that; I forget the exact verbage). FYI, I've noticed that turning off the preview/reading pane reduces the number of timeouts, but it does not eliminate the problem. I do not know why this is the case. Perhaps you could try it and see if it helps you. Joseph D. Wagner
On 31/08/06, Jos Chrispijn (jos at webrz.net) wrote:> Mark Adams wrote (31-08-06 10:50): > >Thanks for the note about the preview/reading pane, I have tried this > >and as you say it slightly improves the situation but is not a fix.> Looks like a network problem. Microsoft frequently advises Outlook > clients only sync with Exchange server(s). > I think would be best to install a mailserver on the remote as well, > letting both mailservers sync instantly on new mail arrival (use a > primary and secondary mailserver thru m-records)Are you suggesting it is a network problem or an Outlook problem? If it is the second I would be grateful for some links giving more background to the problem. Regards, Rory -- Rory Campbell-Lange <rory at campbell-lange.net> <www.campbell-lange.net>