Re: Bug#212244: balsa: Balsa keeps downloading old mails

["Russell L. Harris" <rlharris hal-pc org>]

On 10/14/03 23:29:16, Pawel Salek wrote:
> 
> On 10/15/2003 01:13:35 AM, Russell L. Harris wrote:
>> Does this have anything to do with the fact that (even with 2.0.15),  
>> the "state" of  the system appears not to be updated until one exits  
>> Balsa?  For example, I'm running Gnome2 in Debian 3.0 "unstable",  
>> and routinely keep Balsa open.  Now and then, the browser Galeon  
>> crashes, and sometimes the crash causes Gnome2 to freeze.  If I stop  
>> and restart Gnome2, then start Balsa, the messages I trashed in the  
>> aborted session appear again in the IN box.
>> 
>> I have resorted to exiting Balsa several times each day, in order to  
>> cause the new "state" to be saved.
> 
> Is "Mailbox/Commit" a bad name for a menu entry? there is also a  
> "Misc" page in the configuration that allows for periodic "saving" of  
> the session.
> 
> Pawel
> PS. for what is worth, this problem won't exist in 2.2.x, it is  
> already fixed for imap and hopefully can be fixed also for local  
> mailboxes as well: the flag changes are commited immediately.

So THAT'S what "mailbox -> commit" does!  Commit is not a bad name, but
"update status" might be a better term.

Of course, in actuality the problem was that I did not understand that  
it is necessary for the user to command this action.  For about five  
years, I have been using Eudora in the Windows environment, and I chose  
Balsa largely because Balsa has much of the look and feel of Eudora.   
So I assumed---in error---that the mailbox status was updated  
automatically each time a message is transferred.

Thanks for solving the mystery, Pawel!

RLH