Re: POP3 critical problem



On 2001.06.20 19:26:39 +0200 Carlos Morgado wrote:
> > i press the icon for balsa and it comes up. i then press
> > check to get my emails. now lets say. balsa gets 13 of 20
> > mails and then a dialog comes up and tell me that i reached
> > a timeout or something that tells me that there was some
> > errors with my mailbox (maybe its timeout or maybe the intern
> > timer for balsa exceeded or whatever)..
> > 
> ok, there is a timeout now to prevent getting stuck. the time out
> needs to be increased as it seems.

ok

> > oki now i have 13 new messages in my mailboxes that i can
> > read. but hey.. i got only 13 of 20 emails and i press check
> > again. but instead of getting the remaining emails. balsa
> > starts over again and get me all 20 emails.
> > 
> do you delete or keep the mails on server ? if you keep the current 
> pop3 code is not very good at handling network problems.

delete. i reviewed to make sure its enabled.

> > this ends in this..
> > 
> > - 13 emails that i got before.
> > - abort due an timeout or error.
> > - 20 emails after i pressed check again.
> > 
> > 13 emails double..
> > 
> odd

yes. maybe you can check yourself ? sent 20 mails
on your own address, leech some longer file e.g.
gcc3.0 or whatever and then while your traffic
is heavily get your emails.

> > this is not good. i would suggest that you get one email
> > after another and delete that one to avoid getting emails
> > 
> this is what balsa does

strange.

> > double. and whenever an error happened and balsa wasnt able
> > to delete the mails on the mailbox then make sure the email
> > (might come here partially) gets deleted too.
> > 
> this is what balsa does

strange.

> > correct behave might be this.
> > 
> this is what happens:
> 
> > 1) connect to pop
> > 2) get 1 email on pop
> > 3) check if no errors happened during transer (timeout)
> 
> 3a) drop message in mailbox or call procmail
> 
> if no error delete on server

and here it might be the bug maybe ?

> > 4) goto 2 until last email reached.
> > 
> 
> i'd say the server is caching message status and not deleting properly when 
> there is a connection problem. either that or you don't have 'delete on server'
> checked :)

never had any of these behaves before. i might talk to the administrator to
clear this unbehave. please review the code. maybe theres a worm inside.

-- 
Name....: Ali Akcaagac
Status..: Student Of Computer & Economic Science
E-Mail..: mailto:ali.akcaagac@stud.fh-wilhelmshaven.de
WWW.....: http://www.fh-wilhelmshaven.de/~akcaagaa




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]