307044 - Autosave should not use server based folders for saving

Status: RESOLVED DUPLICATE of bug 304026

(Thunderbird :: Message Compose Window, defect)

Description

[Ravi]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050903 Firefox/1.6a1
Build Identifier: version 1.6a1 (20050902)


Autosave currently uses the drafts folder of the respective account from which
the new message is being cocmposed. This leads to delays and wasted bandwidth
when the drafts is on an IMAP server.


Reproducible: Always

Steps to Reproduce:
1. Compose a new message on an IMAP account and wait for autosave to kick in


Actual Results:  
1. Message is saved to the drafts folder of IMAP server
2. User is terribly annoyed if he is over a slow link and/or multiple compose
windows open


Expected Results:  

Local drafts folder could have been used as it satisfies the purpose of
auto-save just as well (to recover from crashes, accidental closing etc). This
would avoid having to post to server everytime autosave happens.

Comment 1

[zug_treno]

Related to bug 304026?

Comment 2

[Magnus Melin [:mkmelin]]

*** This bug has been marked as a duplicate of 304026 ***

Comment 3

[Ravi]

Re-opening this bug based on my additional comments on the original duplicate
bug - reproduced below -

Also increasing severity to normal as this can cause data loss due to
composition window locking up indefinitely when network is erratic, as I
experienced today.

-----
> If you are having connectivity issues with your mail server, modify your account
> preferences store your Drafts as a local folder.

This is an issue. I would like drafts to be on server so that I can access them
from anywhere. However auto-save is purely a local mechanism for saving
temporary work - just because the implementation chose to club this with drafts
for simplification should not force a user to change his drafts folder!!

Is there a reason why autosave cannot use local drafts folder always?

Also, its just not connection reliability, this ties up bandwidth and can be
exceedingly annoying on a slow connection.

So please reopn this bug for additional comments bassed on above.
----

Comment 4

[Magnus Melin [:mkmelin]]

Ravi: how does this bug differ from bug 304026 (in any significant way)? You
both want (at least an option for) autosave to save mails locally.

Do resolve this bug back as dupe of 304026 in case you cannot state any
significant differences.

Comment 5

[Ravi]

(In reply to comment #4)

I reopened this here as I was not able to reopen bug 304026 since I was not the
author and the reopen request was pending for a long time. I see now that the
other bug is reopened, so we can follow it up there. Resolving this as dupe.


*** This bug has been marked as a duplicate of 304026 ***