| Summary: | Intermittent stream error on IMAP TCP connection | ||
|---|---|---|---|
| Product: | Claws Mail (GTK 2) | Reporter: | Miguel Telleria de Esteban <miguel> |
| Component: | Folders/IMAP | Assignee: | users |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.7.6 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Attachments: | |||
Created attachment 894 [details]
Network log from claws-mail showing that it cannot fetch all new messages
Created attachment 895 [details]
network log for the successfull old message retrieval
Created attachment 896 [details]
--debug output (including network log) for the unsuccessful INBOX update
Created attachment 897 [details]
--debug output (including network log) for the successful oldmessage retrieval
I can't reproduce that at all, marking WORKSFORME. (err 4 is a stream error for libetpan) |
Created attachment 893 [details] stderr output that shows the problem THE CIRCUNSTANCES I have an IMAP account (not MS-Exchanged based if that matters) shared between 3 client machines. On these 3 client machines I run claws-mail as the IMAP client: * One has a Ubuntu Gutsy (2007) version (3.2 or 3.3 I guess) and works fine. * Another one has a 3.7.5 version and works fine. * The third one is the one causing problems running that started when I switched from 3.7.5 to 3.7.6 with a Debian Squeeze update. THE PROBLEM On this third machine, when I log into my IMAP account after a period on which I have received lots of new emails and done some modifications (with respect to the latest successful login), I experience the following behaviour: - Claws-mail stays some time with a message "Scanning <account/INBOX>" - After this time the cached version of the INBOX is shown. - Previous emails (body not cached) can be accessed through IMAP - New emails don't show up. Accessig from the same computer and location with an alternate IMAP client (e.g. thunderbird) works fine. FURTHER DETAILS I attached the stderr output message. Other logging/debug info such as: network log, --debug output and wireshark capture will be attached later.