[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sylpheed
Subject:    [sylpheed:28368] Re: Lost mail if no space left on device
From:       "Joel Sinor" <joel.sinor () gmail ! com>
Date:       2006-08-24 15:59:36
Message-ID: e3b17aa0608240859q7690e4e2hde12180dec048f0 () mail ! gmail ! com
[Download RAW message or body]

This is just a guess, but turning on the logging feature may be
sufficient as I have noted that the commands exchanged with mail
servers and most errors seem to show up when you do that....
Just close sylpheed, open up an xterm or something, and type:

sylpheed --debug 2>&1 | tee -a ./sylpheed-delete-mail.out

you should see output in the xterm when sylpheed does things like get
your mail and that output will be put into the
sylpheed-delete-mail.out file.

But for this output to be useful you'd have to run out of space saving
an email and I would hate for you to lose more mail...
It sounds like others are onto the problem and have data for a test
case... though you could go ahead with the above and if you end up
seeing the problem again you would have potentially useful output...

On 8/24/06, Serhii Piddubchak <dusoft@developingcentral.com> wrote:
> On Wed, 23 Aug 2006 21:49:27 -0400
> Seth Kurtzberg <seth@cql.com> wrote:
>
> > On Wed, 23 Aug 2006 21:20:28 -0400
> > "Steven M. Bellovin" <smb@cs.columbia.edu> wrote:
> >
> > > On Thu, 24 Aug 2006 09:39:39 +0900, Hiroyuki Yamamoto <hiro-y@kcn.ne.jp>
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > On Wed, 23 Aug 2006 11:33:06 -0400
> > > > "Steven M. Bellovin" <smb@cs.columbia.edu> wrote:
> > > >
> > > > > > It might be smarter if the program checked for space before deleting
> > > > > > the message from the server.  However, letting a hard disk fill up
> > > > > > is a bad idea and can lead to other problems.  It is also smarter
> > > > > > to provide adequate storage for your needs.  If Hiroyuki can add
> > > > > > that test without to much degradation in performance then it would
> > > > > > be an improvement but I wouldn't label it as a bug and wouldn't
> > > > > > want to take a day in and day out performance hit to protect me
> > > > > > from something I should avoid anyway.  It's not like disk storage
> > > > > > is a major cost these days.
> > > > > >
> > > > > It is most definitely a bug.  The check is cheap enough -- look for
> > > > > ENOSPC after a write has failed.  However, even if the check were
> > > > > expensive it still has to be done.
> > > >
> > > > I've added such error checking long time ago. POP3 session will stop
> > > > immediately if any I/O error (including ENOSPC) occurred (see
> > > > libsylph/{session.c, pop.c, recv.c}, src/inc.c).
> > >
> > > Great.
> > > >
> > > > But it could be possible that some bugs creeped in after that. It will
> > > > be appreciated if someone take a look at what is going on when no disk
> > > > space left. I'll also look into it.
> > > >
> > > Bugs can always happen, even in the best code.
> >
> > Indeed.  This isn't a creeping bug, I believe.  It just requires an additional patch for the IMAP client case.
> >
> > Seth Kurtzberg
> >
>
> In my case it is a POP3 session. What should i do to help? Should i run
> sylpheed through gdb to see what is going on? Or maybe i should just
> recompile sylpheed with some debugging options turned on?
>
> --
> Serhii Piddubchak
>
> e-mail: dusoft@developingcentral.com
> JID:    dusoft@jabber.org.ua
>
>

[prev in list] [next in list] [prev in thread] [next in thread]