Re: [Evolution] IMAP issues

[Superduck <superduck itsaduck com>]

Whoops...forgot to export...

Reasonable messages give us:
        
        Single click
        emitting cursor changed signal, for uid 1439
        selecting uid 1439 (direct)
        Release
        selecting uid 1439 (delayed)
        got message in dispatch thread
        sending : A00066 UID FETCH 1439 RFC822.PEEK
        setting msg Retrieving message 1439
        received: * 18 FETCH (RFC822 {1212}
        received:  UID 1439)
        received: A00066 OK UID FETCH completed
        redisplaying
        clearing msg

while culprit messages give us this:

        Single click
        emitting cursor changed signal, for uid 1434
        selecting uid 1434 (direct)
        Release
        selecting uid 1434 (delayed)
        got message in dispatch thread
        sending : A00067 UID FETCH 1434 BODY.PEEK[0]
        setting msg Retrieving message 1434
        received: * 17 FETCH (BODY[0] {1643}
        received:  UID 1434)
        received: A00067 OK UID FETCH completed
        sending : A00068 UID FETCH 1434 BODY.PEEK[1.MIME]
        received: * 17 FETCH (BODY[1.MIME] NIL UID 1434)
        received: A00068 OK UID FETCH completed
        
        camel-WARNING **: shared_is_of_type: trying to cast NULL to instance of `CamelObject'
        
        camel-WARNING **: shared_is_of_type: trying to cast NULL to instance of `CamelObject'
        
        camel-CRITICAL **: file camel-object.c: line 467 (camel_object_unref): assertion `CAMEL_IS_OBJECT 
(obj)' failed.
        redisplaying
        clearing msg


On Tue, Mar 13, 2001 at 05:13:19PM +1030, Not Zed wrote:
> Try the CAMEL_VERBOSE_DEBUG=1 thing, it will provide a lot more detail
> on what is happening.
>
>
> On 13 Mar 2001 01:27:40 -0500, Superduck wrote:
> > Ah.
> >
> > This explains everything! Well, maybe after some reading...
> >
> > Anyway, reasonable messages give us:
> >
> >       Single click
> >       emitting cursor changed signal, for uid 1439
> >       selecting uid 1439 (direct)
> >       Release
> >       selecting uid 1439 (delayed)
> >       got message in dispatch thread
> >       setting msg Retrieving message 1439
> >       redisplaying
> >       clearing msg
> >
> > while culprit messages give us this:
> >
> >       Single click
> >       emitting cursor changed signal, for uid 1434
> >       selecting uid 1434 (direct)
> >       Release
> >       selecting uid 1434 (delayed)
> >       got message in dispatch thread
> >       setting msg Retrieving message 1434
> >       
> >       camel-WARNING **: shared_is_of_type: trying to cast NULL to instance of `CamelObject'
> >       
> >       camel-WARNING **: shared_is_of_type: trying to cast NULL to instance of `CamelObject'
> >       
> >       camel-CRITICAL **: file camel-object.c: line 467 (camel_object_unref): assertion `CAMEL_IS_OBJECT 
> > (obj)' failed.
> >       redisplaying
> >       clearing msg
> >
> > Unfortunately, I don't have much information on the imap server.
> > I am attempting to connect via a tunnel over https. This works
> > perfectly with Netscape mail, mutt, and several other email clients,
> > none of which are quite as cool...well, mutt's pretty cool...
> >
> >
> > On Tues, Mar 13, 2001 at 03:53:36PM +1030, Not Zed wrote:
> > > If there was a timeout problem, you would get error boxes about it
> > > timing out.
> > >
> > > Try setting CAMEL_VERBOSE_DEBUG=1 in the same shell as you run
> > > evolution-mail, and then running evolution in another shell, and see
> > > what output you get trying to download the messages.
> > >
> > > What imap server are you using, etc?  (version etc)
> > >
> > >  !Z
> > >
> > > On 12 Mar 2001 23:12:13 -0500, Superduck wrote:
> > > > I am currently getting daily snapshot buiids via apt-get. A month ago
> > > > when I played with Evolution this was much much worse, i.e. most of
> > > > my mail would not open. It seems to be much better, but not gone. As far
> > > > as I can tell, this affects messages with attachments over 5k or larger
> > > > messages without attachments...some kind of timeout problem?
> > > >
> > > >       llama:~$ evolution --version
> > > >       Gnome Evolution 0.9
> > > >       llama:~$ uname -a
> > > >       Linux llama 2.4.2 #3 Mon Mar 5 17:54:40 EST 2001 i586 unknown
> > > >
> > > > On Tue, Mar 13, 2001 at 07:20:10AM +0500, Dan Winship wrote:
> > > > > What version are you using? This bug is supposed to be fixed in both
> > > > > HEAD and 0.9.
> > > > >
> > > > > -- Dan
> > > >
> > > > -- 
> > > > Pete Gaulin
> > > >
> > > > _______________________________________________
> > > > evolution maillist  -  evolution helixcode com
> > > > http://lists.helixcode.com/mailman/listinfo/evolution
> > >
> > >
> > > _______________________________________________
> > > evolution maillist  -  evolution helixcode com
> > > http://lists.helixcode.com/mailman/listinfo/evolution
> >
> > -- 
> > Pete Gaulin
>
>
> _______________________________________________
> evolution maillist  -  evolution helixcode com
> http://lists.helixcode.com/mailman/listinfo/evolution

-- 
Pete Gaulin