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

List:       kde-bugs-dist
Subject:    Bug#4128: Pine message ist permantly updated
From:       George Staikos <staikos () 0wned ! org>
Date:       2000-05-29 16:16:47
[Download RAW message or body]

On Mon, 29 May 2000, Jason Stephenson wrote:
> On Mon, 29 May 2000, Michael Haeckel wrote:
> > It should stay on the server, but all mailers except pine itself that I know 
> > download it. I don't know why pine can't store it's information somewhere 
> > else. On one mail server I use I managed to configure pine that it does not 
> > store there mails but I don't know any longer how that worked.
> 
> I don't think this is Pine's message. It is stored by the mail server software
> itself. I don't know what mail server software does this, maybe all that run on
> UNIX, but I've seen this message before myself on a POP3 mail server. It's used
> to configure your account.
> 
> > 
> > When I delete it from the server then the rest of the folder on the server 
> > wents away also, but luckily it is usually downloaded as last message.
> 
> OK, I thought something like that might happen. The message does state that it
> will be rebuilt with defaults if you delete the message. That leads me to
> believe that the worst that should happen is you lose any configuration that
> you might have done. It seems dangerous to me that you lose messages when that
> one message is deleted. That's a really poor design, IMHO.
> 
> I'll take a look at the test folder you sent and see if I can reproduce the
> behavior you mentioned. I'm using KMail 1.0.29 right now while KDE 2.0 compiles
> on my machine. I'll try it in KMail 1.1 as soon as the compile is done.

     We could always just honour the Status: RO line in the message..... that
would fix it I think.  We leave it where it is if it's RO.

    It is only used by ipop3d and imapd, BUT it is honoured and obeyed by
Pine as well.

   This is another example of where we can utilitize a  bitfield in the index
entry for a message.  We could have a ReadOnly flag.....

-- 

George Staikos

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