Your message dated Mon, 29 Nov 2010 15:22:03 +0200
with message-id <[email protected]>
and subject line Bug#563176: claws-mail: sent messages are ALWAYS copied to the
"Outbox" folder
has caused the Debian Bug report #563176,
regarding claws-mail: sent messages are ALWAYS copied to the "Outbox" folder
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
563176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563176
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: claws-mail
Version: 3.7.3-1
Severity: important
Hi,
I've configured one accout to put sent messages to another folder than
"Sent Mail" in this account. Still, all sent messages are copied to
designated external folder AND to the "Outbox" folder for this account.
This is a data loss for me because on Gmail they filter for duplicate
messages and my message with all headers is discarded and kept only the
internal crafted message from Claws-Mail.
Please disable this auto-copy-to-Outbox-folder mechanism or provide a
configuration parameter to disable this possible feature.
Thanks
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages claws-mail depends on:
ii libc6 2.10.2-2 GNU C Library: Shared libraries
ii libcairo2 1.8.8-2 The Cairo 2D vector graphics libra
ii libcompfaceg1 1:1.5.2-5 Compress/decompress images for mai
ii libdbus-glib-1-2 0.82-2 simple interprocess messaging syst
ii libenchant1c2a 1.4.2-3.4 a wrapper library for various spel
ii libetpan13 0.58-1 mail handling library
ii libgcrypt11 1.4.4-6 LGPL Crypto library - runtime libr
ii libglib2.0-0 2.22.3-1 The GLib library of C routines
ii libgnutls26 2.8.5-2 the GNU TLS library - runtime libr
ii libgtk2.0-0 2.18.3-1 The GTK+ graphical user interface
ii libice6 2:1.0.6-1 X11 Inter-Client Exchange library
ii libldap-2.4-2 2.4.17-2.1 OpenLDAP libraries
ii libpango1.0-0 1.26.2-1 Layout and rendering of internatio
ii libpisock9 0.12.4-7 library for communicating with a P
ii libsm6 2:1.1.1-1 X11 Session Management library
ii xdg-utils 1.0.2-6.1 desktop integration utilities from
Versions of packages claws-mail recommends:
ii aspell-en [aspell-dictionary] 6.0-0-5.1 English dictionary for GNU Aspell
ii aspell-ro [aspell-dictionary] 3.1-1 The Romanian dictionary for GNU as
ii claws-mail-i18n 3.7.3-1 Locale data for Claws Mail (i18n s
ii xfonts-100dpi 1:1.0.0-4 100 dpi fonts for X
ii xfonts-75dpi 1:1.0.0-4 75 dpi fonts for X
Versions of packages claws-mail suggests:
pn claws-mail-doc <none> (no description available)
ii claws-mail-tools 3.7.3-1 Helper and utility scripts for Cla
ii epiphany-browser [www-browser 2.29.3-1 Intuitive GNOME web browser
ii gedit 2.28.3-1 official text editor of the GNOME
ii iceweasel [www-browser] 3.5.6-1 lightweight web browser based on M
-- no debconf information
--- End Message ---
--- Begin Message ---
notfound 563176 3.7.3-1
stop
Hi,
2010/11/22 Ricardo Mones <[email protected]>:
> So, just to be sure before closing it, this is finally fixed by not
> checking that preference, isn't it?
Okay, I've made more than a dozen of tests in the last 2 hours and the
short summary is the reported problem in this bug is really a problem
elsewhere, but not with saving the sent message to the Outbox folder.
------
I've made several tests with these common settings:
- used a local 'postfix' SMTP server for sending all messages to my
account at work, but the "From" field and account configured in Claws
Mail was the personal account at Gmail.
- the global option from "Configuration -> Preferences -> Mail
Handling -> Sending -> Save sent messages to Sent folder" was
unchecked.
- all the options from the "Account Preferences -> Account -> Advanced
-> Folder" were unchecked, empty values.
The final test was as above almost identical, with only one difference
where I selected the Outbox folder to an IMAP folder from different
account than Gmail. However, this didn't changed the results of both
tests and it only added a new copy of the message generated by Claws
Mail to the custom designated Outbox folder.
The common results of both tests are:
1) there are 3 messages saved in the Gmail account as intermediary
drafts until the final message is sent.
2) the first (draft) message is saved when I clicked on "Draft"
button. This contains at the beginning many X-Claws-* headers.
3) the second (draft) message is saved when I clicked on "Sent later"
button. This has less X-Claws-* than the first but also some strange
headers (AF: NF:0 ..).
4) the third (final) message is saved when I clicked on "Send" button.
The copy with the X-Claws-* and AF: NF:0 headers is present on Gmail
(and to the Outbox folder also in the second test).
All these draft messages appear to be only internal to Claws Mail due
to the X-Claws-* headers that are not present in the message received
at the destination. Also, all these messages have a different time
stamp although are related to a single message. I've specifically
disabled (long time ago) the automatic saving of messages to the Draft
folder so this is not the reason why these are there. However, this
behaviour is only specific to Gmail IMAP account and I cannot
reproduce it on my work IMAP account.
The global configuration "Save sent messages to Sent folder" on Claws
Mail works properly for all accounts. The particular per account
configuration "Put sent message in" works properly too. The only weird
thing that I see now is that the message saved by Claws Mail has many
internal headers and is different from the message arriving at the
destination (probably it would be treated as invalid by another email
client or server).
To conclude, this looks more like a problem with the IMAP server from
Gmail handling intermediate draft messages. Thus, I've closed this bug
report.
Thanks
--- End Message ---
