Closed Bug 223115 Opened 22 years ago Closed 22 years ago

IMAP/Offline problems (Sync is incomplete - silently doesn't complete, or seems to but did not download what it should have.)

Categories

(SeaMonkey :: MailNews: Backend, defect)

x86
Windows XP
defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 142278

People

(Reporter: bugzillaPost120030in, Assigned: Bienvenu)

Details

Offshoot of just-fixed Bug 221023. Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.6a) Gecko/20031020 I just selected "File|Offline|Download/Sync now..." and Mozilla is just sitting there displaying "Connected to mail.messagingengine.com..." It hasn't hung, it just didn't do a sync; network monitoring confirms this. This bug isn't new to this build. I tried "Download/Sync now..." again and this time it started working, but didn't finish - it didn't go offline. Looking for a pattern. There are no errors in the log (a grep (err find, actually - on windows) for "NO" turns up no errors. I tried "Download/Sync now..." a third time and this time it started working, but didn't get far and didn't finish - it didn't go offline. A fourth try worked fine. Will email log (of third attempt)to Bienvenu, as suggested, though it's not too private, and I managed to get a small (2.5MB) log. Severity: Trivial for now - will upgrade if I see [message display, mark unread, delete, or move] silently failing. I then went into the EMD folder and clicked on a 5K email, and got "The body of this message has not been downloaded from the server for reading offline.[...]" even though I have "Do not download messages that are larger than" set to 150K, and I have that folder (and all others but 'user' and the untitled subfolder inside user that keeps reappearing?!?) selected for offline use. This happens for several emails, even after what appears to be a successful sync!
*** This bug has been marked as a duplicate of 142278 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.