[Dovecot] Problem moving emails with attachments or HTML links
I recently switched from UW-IMAP to Dovecot (1.0.rc15 on Ubuntu) and am experiencing a weird problem that I haven't been able to figure out yet:
If I try to move a message from one IMAP folder to another, all works fine if the message is plain text. However, *sometimes* the message will not be transferred if it contains either an attachment and/or an HTML link (operation times-out). Not all the time, but just enough to be annoying. I've looked through the logs and for settings in the .conf file and can't find anything obvious that I've overlooked. Can anyone help me with any parameters that might be causing this type of problem? Thanks so much!
Wren Hunt Cambridge, MA
On Fri, 2007-02-09 at 07:48 -0500, J. Wren Hunt wrote:
If I try to move a message from one IMAP folder to another, all works fine if the message is plain text. However, *sometimes* the message will not be transferred if it contains either an attachment and/or an HTML link (operation times-out).
Are you moving the message within the Dovecot, or are you moving between Dovecot and some local mailbox, or to some other IMAP server?
If it's within Dovecot, it's copied using IMAP's COPY command and I can't really think of why it would timeout there. What client are you using?
Timo Sirainen wrote:
On Fri, 2007-02-09 at 07:48 -0500, J. Wren Hunt wrote:
If I try to move a message from one IMAP folder to another, all works fine if the message is plain text. However, *sometimes* the message will not be transferred if it contains either an attachment and/or an HTML link (operation times-out).
Are you moving the message within the Dovecot, or are you moving between Dovecot and some local mailbox, or to some other IMAP server?
If it's within Dovecot, it's copied using IMAP's COPY command and I can't really think of why it would timeout there. What client are you using?
That's a good point Timo and one which I hadn't necessarily thought of! After thinking about it, I realize that these problems happen when I move messages from a commercial IMAP email provider (fastmail.fm) to my own, home server (running Dovecot 1.0.rc15 on Ubuntu). In all cases my client of choice is Thunderbird 1.x & 2.x run from an equal mix of Windows, Mac OS/X and Linux platforms.
Wren
On Thu, 2007-02-15 at 12:33 -0500, J. Wren Hunt wrote:
Are you moving the message within the Dovecot, or are you moving between Dovecot and some local mailbox, or to some other IMAP server?
If it's within Dovecot, it's copied using IMAP's COPY command and I can't really think of why it would timeout there. What client are you using?
That's a good point Timo and one which I hadn't necessarily thought of! After thinking about it, I realize that these problems happen when I move messages from a commercial IMAP email provider (fastmail.fm) to my own, home server (running Dovecot 1.0.rc15 on Ubuntu). In all cases my client of choice is Thunderbird 1.x & 2.x run from an equal mix of Windows, Mac OS/X and Linux platforms.
Well, I've heard this happening with some people, but I've never been able to reproduce it myself. Also I haven't heard of this happening lately.
Do you connect with SSL to Dovecot? By "home server" do you mean it's running in the same computer as your Thunderbird? Or same local network?
Are you able to easily reproduce this? Could you try enabling rawlog (http://dovecot.org/bugreport.html) and check what is the last thing that happens before it hangs?
Timo Sirainen wrote:
After thinking about it, I realize that these problems happen when I move messages from a commercial IMAP email provider (fastmail.fm) to my own, home server (running Dovecot 1.0.rc15 on Ubuntu). In all cases my client of choice is Thunderbird 1.x & 2.x run from an equal mix of Windows, Mac OS/X and Linux platforms.
Well, I've heard this happening with some people, but I've never been able to reproduce it myself. Also I haven't heard of this happening lately.
Do you connect with SSL to Dovecot? By "home server" do you mean it's running in the same computer as your Thunderbird? Or same local network?
Yes, *all* of my IMAP connections use SSL (running on port 993; wrenhunt.com). My local IMAP server is on its own box and separate and different than my clients (Windows and Mac boxes).
Are you able to easily reproduce this? Could you try enabling rawlog (http://dovecot.org/bugreport.html) and check what is the last thing that happens before it hangs?
I've posted the 2 log files here:
http://wrenhunt.homelinux.org/sandbox/20070218-122930-1113.in http://wrenhunt.homelinux.org/sandbox/20070218-122930-1113.out
These logs reflect me moving 2 emails from one IMAP server (fastmail.fm) to my own box (wrenhunt.com). The first 2 work fine, then the 3rd times out. The client in this case was Thunderbird 1.5.0.9 running on Mac OS X 10.4.8
Thanks for your assistance in debugging this sucker!
Wren
On Sun, 2007-02-18 at 12:46 -0500, J. Wren Hunt wrote:
Are you able to easily reproduce this? Could you try enabling rawlog (http://dovecot.org/bugreport.html) and check what is the last thing that happens before it hangs?
I've posted the 2 log files here:
http://wrenhunt.homelinux.org/sandbox/20070218-122930-1113.in http://wrenhunt.homelinux.org/sandbox/20070218-122930-1113.out
I guess you modified the first mail a bit since the byte count doesn't match the actual message's size (18904 vs 18887) but the append succeeded. But did you modify the second mail? The client says it'll send 6597 bytes but there are only 6592 bytes in the message. So 5 bytes are missing, but the email looks complete.
On Sun, 2007-02-18 at 19:57 +0200, Timo Sirainen wrote:
On Sun, 2007-02-18 at 12:46 -0500, J. Wren Hunt wrote:
Are you able to easily reproduce this? Could you try enabling rawlog (http://dovecot.org/bugreport.html) and check what is the last thing that happens before it hangs?
I've posted the 2 log files here:
http://wrenhunt.homelinux.org/sandbox/20070218-122930-1113.in http://wrenhunt.homelinux.org/sandbox/20070218-122930-1113.out
I guess you modified the first mail a bit since the byte count doesn't match the actual message's size (18904 vs 18887) but the append succeeded. But did you modify the second mail? The client says it'll send 6597 bytes but there are only 6592 bytes in the message. So 5 bytes are missing, but the email looks complete.
Attached a patch that may help also figuring this out. Does it still break with it? What do the rawlogs say with it?
participants (3)
-
J. Wren Hunt
-
J. Wren Hunt
-
Timo Sirainen