On Wed, 2006-05-31 at 21:00 -0400, James White wrote:
> I have to say, since I upgrade both Gnome and Evolution, both of these
> problems have resolved themselves. Large messages are no longer a
> problem, mail sends immediately and the memory leaks are largely
> improved (but still happen with in
On Wed, 2006-05-31 at 17:53 -0400, Igor A. Nesterov wrote:
> On Wed, 2006-05-31 at 14:22 -0700, Derrick MacPherson wrote:
> > > It is SMTP sending mechanism. SMTP server is on corporate intranet with
> > > a good response time. I could understand that the time while a message
> > > stays in Outbox
On Wed, 2006-05-31 at 17:24 -0400, Jeffrey Stedfast wrote:
>
> It queues a send operation on a thread, but if it's busy (has other
> things it's doing), then there will be a delay - how long is dependant
> upon what has been previously queued in the thread.
>
If the thread you mentioned is for
On Wed, 2006-05-31 at 14:22 -0700, Derrick MacPherson wrote:
> > It is SMTP sending mechanism. SMTP server is on corporate intranet with
> > a good response time. I could understand that the time while a message
> > stays in Outbox is actually consumed by the process of establishing SMTP
> > connec
--- Poornima Nayak <[EMAIL PROTECTED]> wrote:
> Yes many of us in Novell use daily Evo 2.6 with Groupwise. Raise a bug
> in bugzilla.gnome.org with stack traces of EDS crash.
> export GROUPWISE_DEBUG=1, launch EDS from same terminal. Paste those
> traces in bugzilla removing sensitive data if any
Today I have received rather big mail. It was of 80,000 text lines,
which gives us about 6MB, but other than that it was pure ASCII text.
It's automatically generated message with some sort of alarms, so
sometimes it happens. This message has practically killed Evolution and
in fact the whole deskt
On Wed, 2006-05-31 at 17:17 -0400, Igor A. Nesterov wrote:
> It's been said enough about delays and slowness in Evolution. Here is
> yet another very annoying one. Documentation says that "Evolution
> normally sends mail as soon as you click Send". Well, it's not really
> true. When I click Send, a
> It's been said enough about delays and slowness in Evolution. Here is
> yet another very annoying one. Documentation says that "Evolution
> normally sends mail as soon as you click Send". Well, it's not really
> true. When I click Send, a message goes to local Outbox and stay there
> for a notic
It's been said enough about delays and slowness in Evolution. Here is
yet another very annoying one. Documentation says that "Evolution
normally sends mail as soon as you click Send". Well, it's not really
true. When I click Send, a message goes to local Outbox and stay there
for a noticeable time
Hi Peter,
Am Mittwoch, den 31.05.2006, 20:22 +0100 schrieb Peter Barnes:
> My problem began yesterday when I clicked on a new mail message just
> arrived in Evolution. What I got was a warning: "The application
> "Evolution" has quit unexpectedly" and the options of "Restart
> Application", "Close
I'm using Evolution 2.4.1 on Ubuntu 5.10 and Gnome 1.12.1.
My problem began yesterday when I clicked on a new mail message just arrived in
Evolution. What I got was a warning: "The application "Evolution" has quit
unexpectedly" and the options of "Restart Application", "Close", or "Inform
Devel
On Wed, 2006-05-31 at 16:00 +1200, Eustace, Glen wrote:
> > Evo deletes messages from the server when you expunge them. Otherwise
> > they're just marked for deletion so you can undelete them if you want.
> > This is how IMAP is supposed to work. IMAP is explicitly *not* meant
> to
> > keep multip
On Wed, 2006-05-31 at 16:00 +1200, Eustace, Glen wrote:
> If a message has been deleted by Client A running evo, I would like it
> to dissappear (be hidden) the next time Evo checks for messages. At
> the
> moment the check would seem to only be for new messages rather than
> changes in state of ol
On Wed, 2006-05-31 at 11:04 +0100, Pete Biggs wrote:
> >
> > If a message has been deleted by Client A running evo, I would like it
> > to dissappear (be hidden) the next time Evo checks for messages. At the
> > moment the check would seem to only be for new messages rather than
> > changes in sta
On Tue, 2006-05-30 at 23:47 -0400, Patrick O'Callaghan wrote:
> Evo deletes messages from the server when you expunge them. Otherwise
> they're just marked for deletion so you can undelete them if you want.
> This is how IMAP is supposed to work. IMAP is explicitly *not* meant to
> keep multiple cl
>
> If a message has been deleted by Client A running evo, I would like it
> to dissappear (be hidden) the next time Evo checks for messages. At the
> moment the check would seem to only be for new messages rather than
> changes in state of old ones.
But there are people (me included) already gr
16 matches
Mail list logo
