Hi all, I encountered a bug, that prevents me from moving mail and as a side effect it messes up all thunderbird/mozilla mail clients (they won't do any message copy/move until I restart them). Here is the info and the header of the mail that produces the error (a spam mail): Dovecot version: 1.0.0 Mail header: Return-Path: <xxdwwu at boboakes.com> Delivered-To: bgs-hu-bgs at bgs.hu Received: (qmail 10895 invoked from network); 7 Jun 2007 16:51:21 -0000 Received: from unknown (HELO 86.109.208.58.broad.sz.js.dynamic.163data.com.cn) (58.208.109.86) by 0 with SMTP; 7 Jun 2007 16:51:21 -0000 Received: from [58.208.109.86] by INBOUND.BOBOAKES.COM.NETSOLMAIL.NET; Tue, 15 May 2085 16:51:38 -0800 From: Nigel <xxdwwu at boboakes.com> To: <bgs at bgs.hu> Subject: explore this offer Date: Tue, 15 May 2085 16:51:38 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_021F0ADE.78E00150" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: Aca6Q09K1THIO7J1RUMI4LVVDU6VQF=X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 . Message-ID: <021f0a9b$6abcc150$566dd03a at xxdwwu> Attached is the error window with the actual error message. It seems that the year 2085 date is not handled but dovecot. Regards Bgs PS: Probably unrelated but here are the other infos: Linux, local XFS, AMD Athlon XP, clients Seamonket 1.1.1 and Thunderbird 2.0.0.0 -------------- next part -------------- A non-text attachment was scrubbed... Name: dovecot.jpg Type: image/jpeg Size: 9315 bytes Desc: not available URL: <http://dovecot.org/pipermail/dovecot/attachments/20070612/3391cb12/attachment-0002.jpg>
On Tue, 2007-06-12 at 10:26 +0200, Bgs wrote:> I encountered a bug, that prevents me from moving mail and as a side > effect it messes up all thunderbird/mozilla mail clients (they won't do > any message copy/move until I restart them)...> Date: Tue, 15 May 2085 16:51:38 -0800The error message says "Invalid internal date". I see two problems here: 1. Date: header isn't the same as internal date. Internal date is the date when the message was saved. 2. COPY command doesn't do anything special with Date: header. It especially doesn't try to put it to internal date field. So it looks like when copying/moving a message Thunderbird goes and uploads the message with APPEND command and moves Date: header to INTERNALDATE. If it really does this, it's pretty bad behavior. Anyway, it still is a Dovecot bug that it doesn't accept such internal dates. Fixed: http://hg.dovecot.org/dovecot-1.0/rev/2460c70d1ffb (and http://hg.dovecot.org/dovecot-1.0/rev/12631f82e897 but that's only a comment change) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20070612/c2d305cd/attachment-0002.bin>
Thanks for the quick actions! We will try the patch first time tomorrow. We are testing dovecot, we will probably migrate to it ;) Bye Bgs Timo Sirainen wrote:> On Tue, 2007-06-12 at 10:26 +0200, Bgs wrote: >> I encountered a bug, that prevents me from moving mail and as a side >> effect it messes up all thunderbird/mozilla mail clients (they won't do >> any message copy/move until I restart them). > .. >> Date: Tue, 15 May 2085 16:51:38 -0800 > > The error message says "Invalid internal date". I see two problems here: > > 1. Date: header isn't the same as internal date. Internal date is the > date when the message was saved. > > 2. COPY command doesn't do anything special with Date: header. It > especially doesn't try to put it to internal date field. > > So it looks like when copying/moving a message Thunderbird goes and > uploads the message with APPEND command and moves Date: header to > INTERNALDATE. If it really does this, it's pretty bad behavior. > > Anyway, it still is a Dovecot bug that it doesn't accept such internal > dates. Fixed: http://hg.dovecot.org/dovecot-1.0/rev/2460c70d1ffb > > (and http://hg.dovecot.org/dovecot-1.0/rev/12631f82e897 but that's only > a comment change) >