From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
upon configuring thunderbird to connect to an imap account on a remote
server, nearly all mail in the Sent folder is deleted. that is, all
mail older than 15 days is inadvertantly deleted with the exception of
the original placeholder message, "DON'T DELETE THIS MESSAGE -- FOLDER
INTERNAL DATA." mail in all other folders intact. evolution and
groupoffice do not produce this error.
ls -l Sent (before connecting to server via imap)
-rw------- 1 will will 79114930 Nov 30 14:28 Sent
ls -l Sent (after connecting to server via imap)
-rw------- 1 will will 1642016 Dec 2 18:50 Sent
Name : thunderbird Relocations: (not relocatable)
Version : 0.9 Vendor: Red Hat, Inc.
Release : 1.fc3 Build Date: Sat 27 Nov
2004 04:28:55 AM EST
Name : dovecot Relocations: (not relocatable)
Version : 0.99.10.5 Vendor: Red Hat, Inc.
Release : 0.FC2 Build Date: Sat 29 May
2004 05:20:29 PM EDT
Version-Release number of selected component (if applicable):
version 0.9 (20041127)
Steps to Reproduce:
1. configure account server settings as seen in screenshot
2. configure account copies & folders as seen in screenshot-1
3. configure account offline & diskspace as seen in screenshot-2
4. examine Sent folder filesize on imap server (excess of 70M)
5. examine Sent folder mail dates on imap server (excess of 15 days old)
6. connect to imap server by clicking on Get Mail
7. examine contents of Sent by clicking on imap Sent folder
8. log into the imap server via ssh and verify filesize change.
Actual Results: *dropped jaw* as i realized all my sent mail from the
past year is gone.
Expected Results: *big smile* as i realize what an awesome product
Created attachment 107804 [details]
Created attachment 107805 [details]
Created attachment 107806 [details]
ack! i accidentally uploaded the screenshots using plain text. sorry.
see screenshots below instead.
Created attachment 107807 [details]
Created attachment 107808 [details]
Created attachment 107809 [details]
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Closing per lack of response to previous request for information.
This bug was originally filed against a much earlier version of Fedora
Core, and significant changes have taken place since the last version
for which this bug is confirmed.
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.