[sylpheed:33629] Re: can't save message to outbox
usselmann.m at icg-online.de
Tue Feb 9 19:56:42 JST 2010
On Tue, 9 Feb 2010 10:21:46 +0100
richard lucassen <mailinglists at lucassen.org> wrote:
> On Tue, 9 Feb 2010 15:18:30 +0900
> Hiroyuki Yamamoto <hiro-y at kcn.ne.jp> wrote:
> > > Just an additional question Hiroyuki: I have used this very IMAP
> > > server and complex folder structure for a number of years now
> > > using Sylpheed 1.06 and these problems never occured when using
> > > the old Sylpheed-1 version.
> > >
> > > I understand that this is a rather complex matter, but do you have
> > > an explanation why this occurs using Sylpheed-3? I skipped
> > > Sylpheed-2 (Sylpheed-1 worked too well ;-) so I'm not able to tell
> > > you how Sylpheed-2 behaved in this situation.
> > Because Sylpheed 3.0 is multi-threaded. Sylpheed 1.x/2.x was
> > single-threaded, and IMAP communication blocked the user interface.
> > You can do nothing while IMAP folders are checked, so it was never a
> > problem.
> Ok, thanks for your reply, Hiroyuki! Just a wishlist thing: wouldn't
> it be nice then to block "auto check new mail" when a compose window
> is opened, or, at least, have the option to block it, in order to
> avoid things like "can't save message to outbox"?
I find it useful that I can write emails while Sylpheed is checking
for new mails (Which takes quite some time here since I have several
remote IMAP accounts with a lot of folders).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 0 bytes
Desc: not available
Url : http://www.sraoss.jp/pipermail/sylpheed/attachments/20100209/1220b9a3/attachment.bin
More information about the Sylpheed