| Summary: | Problems with receiving a message notification before a continuation in IMAP. | ||
|---|---|---|---|
| Product: | [Applications] kmail | Reporter: | Daniel James <daniel> |
| Component: | IMAP | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | CLOSED INTENTIONAL | ||
| Severity: | normal | CC: | bjoern |
| Priority: | NOR | ||
| Version: | 1.8 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
Do you still have this problem with a recent version of kmail? I haven't used either hula or kmail for years and hula is pretty much dead. I worked around this in hula at the time, although I was pretty sure it was a bug in kmail's handling of imap and worth fixing. I had a quick try at installing Bongo (http://www.bongo-project.org/), which is a fork of hula, but I had a bit of trouble with some of the dependencies. Looking at their code they've change the append implementation so I don't know how it'll behave now. If it helps here's the relevant thread from the hula list: http://thread.gmane.org/gmane.comp.cms.hula.devel/571 I fear no developer will have the time to investigate this on its own. So I'm closing this. If there is still something wrong with kmail's IMAP implementation, it is surely reported - hopefully with an easy way to reproduce. |
Version: 1.8 (using KDE KDE 3.4.0) Installed from: Unlisted Binary Package OS: Linux When kmail issues an APPEND command, if it receives any response before the continuation it doesn't send the mail but just moves on to the next command. ie. for something along the lines of: 3 APPEND "INBOX" {512} * 10 EXITS * 3 RECENT + Ready for more data 4 APPEND "INBOX" {674} (No, that's not a real protocol dump, but I've already spent enough time on this to be bothered). This was causing problems with hula - a workaround has been checked in there but it could still cause problems. I know I'm not using the most recent version, but I couldn't find any mention of this sort of thing in the changelog or bugzilla. Sorry if it has already been fixed.