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

List:       kde-devel
Subject:    Re: kmail
From:       Don Sanders <dsanders () cch ! com ! au>
Date:       1999-11-29 21:16:00
[Download RAW message or body]

Hmm, it is working fine here.

Can you help debug it? Let's just deal with a local mailbox.

If kmail is emptying the incoming mail file after checking then the 
  rc = mailFolder.expunge();
on line 120 of kmacctlocal.cpp must be being run.

It should only be run if all the repetitions of 
      addedOk = processNewMsg(msg);
on line 112 suceed.

Would you be able to put debugging statements in like
debug( "Breakpoint #num" );
before and after the line 120 and 112 to see whether they are being run?

Also put a debug statement before and after line 99
  for (i=0; i<num; i++)
(obviously you'll have to put the debug statement after line 99 two lines after 
99 so that if is inside the { block)

Perhaps somehow num which is assigned a value via the 
  num = mailFolder.count();
statement is assigned the value zero.

I'm going to create a new account here and see if I can reproduce the problem.

BFN,
Don.

On Tue, 30 Nov 1999, dep wrote:
> On Mon, 29 Nov 1999, Bob Bernstein wrote:
> 
> |kmail appears not to be able to write new messages, even from a spool file,
> |into its folders; unless I'm very mistaken, they seem to go into the cosmic
> |byte bucket. 
> |
> |A couple of tests running fetchmail (set to leave messages on the server!),
> |then directly inspecting the spool file, then - in kmail - 'checking' the
> |local spool account, produce this effect. Messages seen in the spool never 
get
> |to a kmail folder, and after kmail checks the spool, it's empty. Ergo -> byte
> |bucket.
> 
> this is true with pop mail in the 11/29 kdenetwork snapshot as well.
> at minimum, seems prudent to set it to leave mail on server and then,
> when kmail gobbles it (or until it doesn't), read, respond, archive,
> whatever, some other way.
> 
> -- 
> dep__________________________________________________________________
>                 2000 is a number that breaks computers.
>                 01-01-01 is when the millennium begins.

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