[Evolution] Evolution 3.0.2 routinely fails to fetch mail

2011-06-28 Thread Andrew Cowie
Upgrading to Evolution 3.0 has been quite unpleasant. Now on 3.0.2, the
problem is that mail checks intermittently fail, resulting in a horrid
red bar appearing on the screen. After Dismiss this ugly error message
to get out of the way, and then Send/Receive again, which fails
silently but immediately. Then a third Send/Receive then works.

Although apparently not the same problem that others have been
reporting, this falls into the same general networking is broken
category. Anyone have any idea what's going on?

AfC
Sydney



signature.asc
Description: This is a digitally signed message part
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
http://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Evo 3.0.2 won't download mail

2011-06-28 Thread Milan Crha
On Tue, 2011-06-28 at 09:59 +1000, Rick Phillips wrote:
 I have been doing that but it is still a huge nuisance.  Evo for me is
 used in a corporate situation and it means I have to do this pretty
 much all day unless I can remember to close it quickly to save the
 caching.

Hi,
you can always ask your distribution to include that patch in a release,
which can be done independently from the upstream release.

There's a Fedora 15 update in updates-testing now:
https://admin.fedoraproject.org/updates/evolution-3.0.2-3.fc15
Bye,
Milan

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
http://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Evolution 3.0.2 routinely fails to fetch mail

2011-06-28 Thread Pete Biggs
On Tue, 2011-06-28 at 16:40 +1000, Andrew Cowie wrote:
 Upgrading to Evolution 3.0 has been quite unpleasant.

I haven't had any problems with 3.0

  Now on 3.0.2, the
 problem is that mail checks intermittently fail, resulting in a horrid
 red bar appearing on the screen.

Yeah, a bit in your face isn't it.  But I only see it when there are
actual network problems - mostly with gmail.

  After Dismiss this ugly error message
 to get out of the way, and then Send/Receive again, which fails
 silently but immediately. Then a third Send/Receive then works.
 
 Although apparently not the same problem that others have been
 reporting, this falls into the same general networking is broken
 category. Anyone have any idea what's going on?
 
It's difficult without more information.  Is this POP or IMAP or MAPI or
EWS or local mail retrieval?  Have you done any other investigation?
Like run Evolution from the command line? Enabled the verbose/debugging
flags?  If so, any clues?  Any error messages?

What about your service provider? Network?  Are they reliable? 

P.

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
http://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Evo 3.0.2 won't download mail

2011-06-28 Thread Rick Phillips
Milan,

 you can always ask your distribution to include that patch in a release,
 which can be done independently from the upstream release.
 
 There's a Fedora 15 update in updates-testing now:
 https://admin.fedoraproject.org/updates/evolution-3.0.2-3.fc15

That seems to have fixed things - for me at least.  Thank you very much
for your help and courtesy.

Regards,

Rick

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
http://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] [EWS] RPC over HTTP connection problem

2011-06-28 Thread David Woodhouse
On Fri, 2011-06-24 at 11:57 +0200, Patryk Benderz wrote:
 
 Windows proxy address: 192.168.0.246
 Exchange Server name:  server01.domain.net
 Exchange User name:patben 

I would guess that the URL you need is
https://server01.domain.net/EWS/Exchange.asmx

Can forget the 'Fetch URL' button, which evidently isn't working for
you, and enter that URL manually?

Run Evolution from the command line with EWS_DEBUG=2 and you'll see all
its attempts to communicate with the server. Using tcpdump is also
useful if you get *nowhere*; it'll show you exactly what it was trying
(and if it's using the proxies or not, etc.).

-- 
dwmw2

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
http://mail.gnome.org/mailman/listinfo/evolution-list