[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#315645: marked as done (IMAP: move message won't move attachments)

Your message dated Tue, 27 Mar 2007 10:08:45 -0400
with message-id <9f694b820703270708p7805913en741ad60e11443068@mail.gmail.com>
and subject line Very old bug, do you still have the problem ?
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kmail
Version: 4:3.3.2-3
Severity: normal


When I move a message that has an attachment from an IMAP box
(imap.club-internet.fr, haven't tried on anoter IMAP server) to a local
folder, kmail doesn't move the attachment. It always happen when the
attachment is big (let's say more than 2 MB) or when there are several
attachments that sums up to a "big" size. However, I can copy it to a local
folder and I have no problem... Maybe it's an option, but I haven't seen it.
Thank you for your hard work :)
Gilles.
P.S. : (this was copied from reportbug tool because my exim is not correctly 
configured)

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.31
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=locale: Cannot set 
LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968) (ignored: LC_ALL set to fr_FR@euro)

Versions of packages kmail depends on:
ii  kdelibs4                 4:3.3.2-6.1     KDE core libraries
ii  libc6                    2.3.2.ds1-22    GNU C Library: Shared libraries 
an
ii  libgcc1                  1:3.4.3-13      GCC support library
ii  libice6                  4.3.0.dfsg.1-14 Inter-Client Exchange library
ii  libkcal2a                4:3.3.2-3       KDE calendaring library
ii  libkdenetwork2           4:3.3.2-3       KDE Network library
ii  libkdepim1               4:3.3.2-3       KDE PIM library
ii  libkleopatra0a           4:3.3.2-3       KDE GnuPG interface libraries
ii  libkpimidentities1       4:3.3.2-3       KDE PIM user identity information
ii  libksieve0               4:3.3.2-3       KDE mail/news message filtering 
li
ii  libmimelib1a             4:3.3.2-3       KDE mime library
ii  libpng12-0               1.2.8rel-1      PNG library - runtime
ii  libqt3c102-mt            3:3.3.4-3       Qt GUI Library (Threaded runtime 
v
ii  libsm6                   4.3.0.dfsg.1-14 X Window System Session 
Management
ii  libstdc++5               1:3.3.5-13      The GNU Standard C++ Library v3
ii  libx11-6                 4.3.0.dfsg.1-14 X Window System protocol client 
li
ii  libxext6                 4.3.0.dfsg.1-14 X Window System miscellaneous 
exte
ii  perl                     5.8.4-8         Larry Wall's Practical Extraction
ii  xlibs                    4.3.0.dfsg.1-14 X Keyboard Extension (XKB) 
configu
ii  zlib1g                   1:1.2.2-4       compression library - runtime

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = "fr_FR@euro",
        LC_ALL = "fr_FR@euro",
        LANG = "fr_FR@euro"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

--- End Message ---
--- Begin Message --- 
Submitter was asked to provide more information about this bug
( http://bugs.debian.org/315645 ) four weeks ago.

Since more info was not provided, we are closing the bug.
Feel free to reopen this bug if you are still experiencing this issue
and you have extra information on how reproduce the issue.

Thanks,
Olivier

--- End Message ---
Reply to: