Hi
I had problems with timeouts in IMAP. Everything was working fine with Outlook 2000, Courier-Imap and FC2 running the Courier-Imap.
Suddenly, now I get frequent timeouts. No matter what client I use (outlook, outlook xpress, thunderbird, mozilla) I get timeouts after downloading around 20 headers. When Outlook express tells me about it, I tell it to stop and then the client download some more messages.
I thought It had to do with the mailserver and I switch courier for dovecot, but I get the same result
I think maybe it is something with the wrappper service or something like that.
How canI troubleshoot this? Not much info left on /var/log/messages and /var/log/maillog.
Here is what Outlook expess sees
Microsoft Internet Messaging API 6.00.2800.1441 IMAP Log started at 08/05/2004 04:49:37 IMAP: 04:49:37 [db] Connecting to '192.168.0.5' on port 143. IMAP: 04:49:37 [db] OnNotify: asOld = 0, asNew = 4, ae = 0 IMAP: 04:49:37 [db] OnNotify: asOld = 4, asNew = 5, ae = 2 IMAP: 04:49:37 [db] OnNotify: asOld = 5, asNew = 5, ae = 4 IMAP: 04:49:38 [db] OnNotify: asOld = 5, asNew = 5, ae = 3 IMAP: 04:49:38 [rx] * OK dovecot ready. IMAP: 04:49:38 [tx] 003B CAPABILITY IMAP: 04:49:38 [db] OnNotify: asOld = 5, asNew = 5, ae = 3 IMAP: 04:49:38 [rx] * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED STARTTLS AUTH=PLAIN IMAP: 04:49:38 [rx] 003B OK Capability completed. IMAP: 04:49:38 [tx] LOGIN command sent IMAP: 04:49:38 [db] OnNotify: asOld = 5, asNew = 5, ae = 3 IMAP: 04:49:38 [rx] 003C OK Logged in. IMAP: 04:49:38 [tx] 003D IDLE IMAP: 04:49:38 [db] OnNotify: asOld = 5, asNew = 5, ae = 3 IMAP: 04:49:38 [rx] + idling IMAP: 04:49:38 [tx] DONE IMAP: 04:49:38 [db] OnNotify: asOld = 5, asNew = 5, ae = 3 IMAP: 04:49:38 [rx] 003D OK Idle completed. IMAP: 04:49:38 [tx] 003E SELECT "Lists.Computer.Fedora_List" IMAP: 04:50:38 [db] OnNotify: asOld = 5, asNew = 5, ae = 7 IMAP: 04:50:41 [tx] Dropping connection, LOGOUT sent IMAP: 04:50:41 [db] Connection to '' closed. IMAP: 04:50:41 [db] OnNotify: asOld = 5, asNew = 0, ae = 5
Thanks for helping me solve this problem
Am Do, den 05.08.2004 schrieb Javier Perez um 12:00:
I had problems with timeouts in IMAP. Everything was working fine with Outlook 2000, Courier-Imap and FC2 running the Courier-Imap.
Suddenly, now I get frequent timeouts.
And what did you change when first time the timeouts occur? You must have changed either on server side or client side.
No matter what client I use (outlook, outlook xpress, thunderbird, mozilla) I get timeouts after downloading around 20 headers. When Outlook express tells me about it, I tell it to stop and then the client download some more messages.
And from a different client host?
I thought It had to do with the mailserver and I switch courier for dovecot, but I get the same result
I think maybe it is something with the wrappper service or something like that.
Which wrapper service?
Alexander
P.S. No HTML formatted list mails please, just plain text only. Thanks.
On Thu, 2004-08-05 at 05:30, Alexander Dalloz wrote:
Am Do, den 05.08.2004 schrieb Javier Perez um 12:00:
I had problems with timeouts in IMAP. Everything was working fine with Outlook 2000, Courier-Imap and FC2 running the Courier-Imap.
Suddenly, now I get frequent timeouts.
And what did you change when first time the timeouts occur? You must have changed either on server side or client side.
Server side I do not remember changing anything. I checked my changelog and there are no program installations or conf file changes.
Client Side, I applied the latest windows security updates with the Cumulative Security Update for IE Service Pack 1 (KB867801)
No matter what client I use (outlook, outlook xpress, thunderbird, mozilla) I get timeouts after downloading around 20 headers. When Outlook express tells me about it, I tell it to stop and then the client download some more messages.
And from a different client host?
I thought It had to do with the mailserver and I switch courier for dovecot, but I get the same result
I think maybe it is something with the wrappper service or something like that.
Which wrapper service?
I remember that Courier had a daemon called couriertcp which called the imap program each time someone logged on port 143. I just learning dovecot and I am not sure if there is some sort of play like this for the dovecot imap to work. I am still learning how it works. But at least, I know that inside the server it is working fine because Evolution does not have any problem. The problem is in the communication between an external client and the server. I already changed the client and the server, therefore whatever problem is left should be on the link connecting them both.
Alexander
P.S. No HTML formatted list mails please, just plain text only. Thanks.
Am Do, den 05.08.2004 schrieb Javier Perez um 20:46:
I had problems with timeouts in IMAP. Everything was working fine with Outlook 2000, Courier-Imap and FC2 running the Courier-Imap.
Suddenly, now I get frequent timeouts.
And what did you change when first time the timeouts occur? You must have changed either on server side or client side.
Server side I do not remember changing anything. I checked my changelog and there are no program installations or conf file changes.
Client Side, I applied the latest windows security updates with the Cumulative Security Update for IE Service Pack 1 (KB867801)
Such security updates were often cause for trouble by side effects in the past. Even updates were taken back because of causing problems.
Maybe it is an anti-virus tool on the client or a "personal firewall"; the usual suspects.
No matter what client I use (outlook, outlook xpress, thunderbird, mozilla) I get timeouts after downloading around 20 headers. When Outlook express tells me about it, I tell it to stop and then the client download some more messages.
And from a different client host?
Try it from a different client host. I bet it will confirm that it is your Windows[tm] host after the update causing the timeouts.
I thought It had to do with the mailserver and I switch courier for dovecot, but I get the same result
I think maybe it is something with the wrappper service or something like that.
Which wrapper service?
I remember that Courier had a daemon called couriertcp which called the imap program each time someone logged on port 143. I just learning dovecot and I am not sure if there is some sort of play like this for the dovecot imap to work. I am still learning how it works. But at least, I know that inside the server it is working fine because Evolution does not have any problem. The problem is in the communication between an external client and the server. I already changed the client and the server, therefore whatever problem is left should be on the link connecting them both.
Ok, I understand. Dovecot runs as it's own daemon, without a wrapper in front or (x)inetd controlled.
Alexander
On Thu, 2004-08-05 at 14:52, Alexander Dalloz wrote:
Am Do, den 05.08.2004 schrieb Javier Perez um 20:46:
I had problems with timeouts in IMAP. Everything was working fine with Outlook 2000, Courier-Imap and FC2 running the Courier-Imap.
Suddenly, now I get frequent timeouts.
And what did you change when first time the timeouts occur? You must have changed either on server side or client side.
Server side I do not remember changing anything. I checked my changelog and there are no program installations or conf file changes.
Client Side, I applied the latest windows security updates with the Cumulative Security Update for IE Service Pack 1 (KB867801)
Such security updates were often cause for trouble by side effects in the past. Even updates were taken back because of causing problems.
Maybe it is an anti-virus tool on the client or a "personal firewall"; the usual suspects.
No matter what client I use (outlook, outlook xpress, thunderbird, mozilla) I get timeouts after downloading around 20 headers. When Outlook express tells me about it, I tell it to stop and then the client download some more messages.
And from a different client host?
Try it from a different client host. I bet it will confirm that it is your Windows[tm] host after the update causing the timeouts.
I thought It had to do with the mailserver and I switch courier for dovecot, but I get the same result
I think maybe it is something with the wrappper service or something like that.
Which wrapper service?
I remember that Courier had a daemon called couriertcp which called the imap program each time someone logged on port 143. I just learning dovecot and I am not sure if there is some sort of play like this for the dovecot imap to work. I am still learning how it works. But at least, I know that inside the server it is working fine because Evolution does not have any problem. The problem is in the communication between an external client and the server. I already changed the client and the server, therefore whatever problem is left should be on the link connecting them both.
Ok, I understand. Dovecot runs as it's own daemon, without a wrapper in front or (x)inetd controlled.
Alexander
Hi I can confirm it now. KB867801 broke my system. I inserted Knoppix on the same machine and Kmail worked perfectly as a client with the IMAP server. Therefore, something in KB867801 is causing the timeouts.