Your message dated Thu, 25 Dec 2008 22:50:40 +0100
with message-id <20081225225040.22bff...@busgosu>
and subject line closing sylpheed-gtk1 bugs (removed package)
has caused the Debian Bug report #208139,
regarding sylpheed: silently fails to delete mail over imap if no Trash found
on server
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.)
--
208139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=208139
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sylpheed
Version: 0.9.4-2
Severity: minor
Tags: sid
Running sylpheed against dovecot-imap, with maildirs. After a server
rebuild, mail was lost; standard local mail delivery recreated the INBOX.
Sylpheed may have created the Trash folder in a previous incarnation; since
the account was not recreated inside sylpheed, any initialization that
happens only during account creation did not take place. However, the
folder tree showed a "Trash" folder for the account.
Deleted trash (preferences set to expunge on command, delete trash on exit
(or from the menu option)) failed to get deleted. Pointing the account's
"trash" (in the advanced tab) to another account's Trash folder did not
succeed. Setting it to the non-existent Trash folder for the current
account was always permitted, but always failed silently.
Watching in tcpdump, nothing happens during a delete; when an expunge is
attempted, sylpheed ignores the setting of the "put deleted mail" folder and
tries to use Trash. It received an error message from the server, which it
did not report (no such directory).
Because the folder "exists" (in some Platonic sense), at least in sylpheed's
folder tree, it cannot be created normally via sylpheed. Interestingly
enough, though, it is possible to create a subfolder of the Trash folder,
which created the Trash folder as well (but it was not possible to copy mail
to the (nonexistent) Trash folder).
The case of the undeletable mail. Until I got irritated enough to snoop the
connection, the workaround was to use a different mail client to delete
mail.
Amy!
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux ythgin 2.4.21-ac4 #1 Wed Jul 9 00:46:44 EDT 2003 i686
Locale: LANG=en_US, LC_CTYPE=en_US
Versions of packages sylpheed depends on:
ii libc6 2.3.2-3 GNU C Library: Shared libraries an
ii libcompfaceg1 1989.11.11-24 Compress/decompress images for mai
ii libgdk-pixbuf2 0.22.0-2.0.1 The GdkPixBuf image library, gtk+
ii libglib1.2 1.2.10-9 The GLib library of C routines
ii libgpgme6 0.3.15-1 GPGME - GnuPG Made Easy
ii libgtk1.2 1.2.10-16 The GIMP Toolkit set of widgets fo
ii libldap2 2.1.22-1 OpenLDAP libraries
ii libncurses5 5.3.20030719-1 Shared libraries for terminal hand
ii libpisock8 0.11.8-3 Libraries for communicating with a
ii libreadline4 4.3-5 GNU readline and history libraries
ii libssl0.9.7 0.9.7b-2 SSL shared libraries
ii metamail 2.7-45.1 An implementation of MIME
ii xlibs 4.2.1-10 X Window System client libraries
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi there,
You're receiving this mail because time ago (probably years) filed a
bug against sylpheed-gtk1 package in Debian's Bug Tracking System (or
against sylpheed package before it was a GTK2 application which ended
assigned to sylpheed-gk1 package).
Anyway, the sylpheed-gtk1 package has been removed from Debian now, hence
I'm closing all the bugs related to it. Most of them are old, but, it may
be possible some of these are still within modern sylpheed.
If you're using sylpheed package right now, would be very helpful to check
if the bug being closed now still applies to sylpheed. If not using
sylpheed, well, you can still check it anyway if you want... :)
If bug doesn't apply to current sylpheed you're done.
If the current sylpheed package (2.6.0, in experimental) still has the bug,
please, file a _NEW_ bug report for sylpheed (unless you have already done
so in the past, of course). You may refer the old bug number if you want in
the description, but error details and reproduction method must be relevant
for sylpheed.
Sorry for the long mail and thanks for reporting.
Seasonal greetings where applicable,
--
Ricardo Mones
http://people.debian.org/~mones
«Don't relax! It's only your tension that's holding you together.»
signature.asc
Description: PGP signature
--- End Message ---
