Re: [Evolution] Unable to retrieve message

2020-01-14 Thread Milan Crha via evolution-list
On Mon, 2020-01-13 at 15:09 -0800, Jonathan Ryshpan wrote:
> Done as GNOME > evolution-data-server > Issues > #182
> Messages on local maildir can't be retrieved

Hi,
thanks. Just for easier access to archive readers:
https://gitlab.gnome.org/GNOME/evolution-data-server/issues/182

Bye,
Milan

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


Re: [Evolution] Unable to retrieve message

2020-01-13 Thread Jonathan Ryshpan
On Mon, 2020-01-13 at 12:37 +0100, Milan Crha via evolution-list wrote:
> On Sat, 2020-01-11 at 07:07 -0800, Jonathan Ryshpan wrote:
> > The setup is simple: ...
> 
> would you mind to file a bug against evolution-data-server [1],
> please?Even there's no reliable reproducer, it'll be better to have
> it filledand investigated later, rather than completely forget of it.
> Aninformation from the initial message of this thread, especially the
> onewith the incorrect path being used, will help too.

Done as GNOME > evolution-data-server > Issues > #182
Messages on local maildir can't be retrieved

jon


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


Re: [Evolution] Unable to retrieve message

2020-01-13 Thread Milan Crha via evolution-list
On Sat, 2020-01-11 at 07:07 -0800, Jonathan Ryshpan wrote:
> The setup is simple: I run a single instance of Evolution and no
> other email clients on any device. Evolution has 4 active accounts:
> 
> Local (On this computer)
> IMAP (imap.mail.att.net)
> IMAP (imap.gmail.com)
> Search Folders

> The message in question arrived from imap.mail.att.net and was
> transferred by a filter to a Local folder. I was able to display the
> message (as I wrote in my original message); after about 5 minutes it
> disappeared; then after about half an hour it reappeared. The problem
> happens infrequently, say about once a month, and typically lasts a
> while, anywhere from 5 minutes to a couple of hours.

Hi,
would you mind to file a bug against evolution-data-server [1], please?
Even there's no reliable reproducer, it'll be better to have it filled
and investigated later, rather than completely forget of it. An
information from the initial message of this thread, especially the one
with the incorrect path being used, will help too.
Thanks and bye,
Milan

[1] https://gitlab.gnome.org/GNOME/evolution-data-server/issues/new

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


Re: [Evolution] Unable to retrieve message

2020-01-13 Thread Milan Crha via evolution-list
On Fri, 2020-01-10 at 14:17 +, Pete Biggs wrote:
> I wouldn't like to point fingers, but multiple Evo clients seem to
> work OK together ...

Hi,
it depends. I recall there are cases where even one Evolution instance
can trick itself. If I recall correctly, it had something to do with
"Synchronize messages for offline use" and local filters. There
happened that the IMAPx provider noticed new messages in a folder and
piled a job to download all the new messages for offline use. At the
same time, or shortly afterwards, local filters had been triggered and
some/all new messages had been moved to their folders. And only after
this move operation the offline download started, realizing the new
messages are not there. You might recall "famous" "Empty cache file"
errors, which showed up quite often not long time ago. The servers I
worked with do not return error when one asks for a content of a
nonexistent message, it rather returns success, with no data
transferred to the caller. This made the cache file empty, because the
server did not return any data.

I do not recall how this had been fixed/worked around, it can be the
"Empty cache file" error is ignored for offline download.

To answer your question:
> > It feels like there is some miss-match of cache syncing policies
> > between devices - or something not checking for changes before
> > syncing. Does that sound possible to you?

Yes, it does sound possible. Updating local cache, even if only the
folder state, before every operation would make things very slow (at
least in some cases). That means that the only viable option is to make
the provider robust, to react on errors gracefully.

It sometimes feels that Evolution is too chatty with error messages. I
believe regular users do not want to see most/majority of them. I think
other clients hide some/few/many errors from the users, pretending
things worked properly (that's only my own guess). The thing is that I
personally prefer to see an error message than to wonder why some thing
should work, but it doesn't, without any clue. Again, that's only me,
others may have other opinion. From the coder's point of view, as the
code is right now, it's close to impossible to distinguish whether the
operation had been run by the user (in which case the error should be
shown always) or whether it was run as part of certain periodical
action (like check for new messages every hour). The second case might
not need to show the errors, it'll retry the next time on its own.

Bye,
Milan

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


Re: [Evolution] Unable to retrieve message

2020-01-11 Thread Jonathan Ryshpan
On Fri, 2020-01-10 at 08:46 +0100, Milan Crha via evolution-list wrote:
> > Can anyone tell me what's going on, how to investigate it, how to
> > prevent it, or how to recover?
> 
> I do not have an answer to any of your question, unfortunately, though
> I've a question for you instead. The only thing I know about this is
> that "it sometimes happens", but whenever I noticed it here and tried
> to investigate, which is months or even years ago, it magically
> disappeared and I didn't move any further. To my question:
> 
> I see from the path that it's an On This Computer folder (as shown in
> Evolution's UI). How is that directory populated? Is it anything like
> "received by POP, then moved to the appropriate folder with filters or
> manually", or "moved manually from another account", or "populated by a
> 3rd-party software not managed by Evolution itself", or...? Even if
> it's the last option it should not matter (in some cases I'd say
> "touching internal Evolution files => expect anything", but not this
> time), because the Maildir structure should adapt appropriately. It can
> be that some part of the provider incorrectly constructs the path and
> causes this error. It may fix on its own when the provider rescans the
> directory, which is usually done the first time the folder is entered
> in the GUI.

The setup is simple: I run a single instance of Evolution and no other
email clients on any device.  Evolution has 4 active accounts:
 * Local (On this computer)
 * IMAP (imap.mail.att.net)
 * IMAP (imap.gmail.com)
 * Search Folders
The message in question arrived from imap.mail.att.net and was
transferred by a filter to a Local folder.  I was able to display the
message (as I wrote in my original message); after about 5 minutes it
disappeared; then after about half an hour it reappeared.  The problem
happens infrequently, say about once a month, and typically lasts a
while, anywhere from 5 minutes to a couple of hours.


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


Re: [Evolution] Unable to retrieve message

2020-01-10 Thread Pete Biggs
On Fri, 2020-01-10 at 08:43 -0500, Adam Tauno Williams wrote:
> On Fri, 2020-01-10 at 12:06 +, Pete Biggs wrote:
> > It feels like there is some miss-match of cache syncing policies
> > between devices - 
> 
> This.  IMAP clients vary **wildly** in their conformance to both the
> protocol requires and best practices.
> 
> The default mail clients on both IOS and Android are pretty dumb-simple 
> in terms of their implementation.
> 
> Concurrent access [moving and deleting] will always result in the
> occasional "message cannot be retrieved".  It should heal quickly. 
> Evolution is one of the best IMAP clients around.
> 
Indeed - the messages don't bother me as I sort of know how they arise
and they don't really cause any issues. I wouldn't like to point
fingers, but multiple Evo clients seem to work OK together ...

P.


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


Re: [Evolution] Unable to retrieve message

2020-01-10 Thread Adam Tauno Williams
On Fri, 2020-01-10 at 12:06 +, Pete Biggs wrote:
> It feels like there is some miss-match of cache syncing policies
> between devices - 

This.  IMAP clients vary **wildly** in their conformance to both the
protocol requires and best practices.

The default mail clients on both IOS and Android are pretty dumb-simple 
in terms of their implementation.

Concurrent access [moving and deleting] will always result in the
occasional "message cannot be retrieved".  It should heal quickly. 
Evolution is one of the best IMAP clients around.

-- 
Highland Park Neighborhood Association
Adam Tauno Williams, Board Chair
Grand Rapids, MI.
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Unable to retrieve message

2020-01-10 Thread Pete Biggs
On Fri, 2020-01-10 at 08:46 +0100, Milan Crha via evolution-list wrote:
> On Thu, 2020-01-09 at 12:51 -0800, Jonathan Ryshpan wrote:
> > Can anyone tell me what's going on, how to investigate it, how to
> > prevent it, or how to recover?
> 
>   Hi,
> I do not have an answer to any of your question, unfortunately, though
> I've a question for you instead. The only thing I know about this is
> that "it sometimes happens", but whenever I noticed it here and tried
> to investigate, which is months or even years ago, it magically
> disappeared and I didn't move any further. To my question:
> 
I hope you'll excuse me adding to this. I see this frequently, but I
use IMAP accounts and I just put it down to multiple devices accessing
the same IMAP store. Other oddities happen as well - like messages
getting undeleted or unread randomly.  It seems particularly prevalent
when iOS devices are involved.

It feels like there is some miss-match of cache syncing policies
between devices - or something not checking for changes before syncing.
Does that sound possible to you?

As I said I just put it down to iOS not playing nicely with other
devices and ignore it!  It doesn't happen reliably enough to really
investigate deeply.

P.


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


Re: [Evolution] Unable to retrieve message

2020-01-09 Thread Milan Crha via evolution-list
On Thu, 2020-01-09 at 12:51 -0800, Jonathan Ryshpan wrote:
> Can anyone tell me what's going on, how to investigate it, how to
> prevent it, or how to recover?

Hi,
I do not have an answer to any of your question, unfortunately, though
I've a question for you instead. The only thing I know about this is
that "it sometimes happens", but whenever I noticed it here and tried
to investigate, which is months or even years ago, it magically
disappeared and I didn't move any further. To my question:

I see from the path that it's an On This Computer folder (as shown in
Evolution's UI). How is that directory populated? Is it anything like
"received by POP, then moved to the appropriate folder with filters or
manually", or "moved manually from another account", or "populated by a
3rd-party software not managed by Evolution itself", or...? Even if
it's the last option it should not matter (in some cases I'd say
"touching internal Evolution files => expect anything", but not this
time), because the Maildir structure should adapt appropriately. It can
be that some part of the provider incorrectly constructs the path and
causes this error. It may fix on its own when the provider rescans the
directory, which is usually done the first time the folder is entered
in the GUI.

Bye,
Milan

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


Re: [Evolution] Unable to retrieve message.

2015-11-10 Thread Fedora
On Tue, 2015-11-10 at 12:28 +0530, Ritesh Khadgaray wrote:

> 
> You might want to clear the cache and check -
> https://wiki.debian.org/Evolution
> 
> Cheers
> -ritz

Tried that but it did not work. It created the folders.db files again,
but I still had the same problems.

But I have found a solution, though I don't know why it works. Simply
rename the folder holding the messages that have the problem. Something
happens at this stage, and the messages are found. Then rename it back
to what the folder was named originally.

Don't fully understand why this works but it does.

Thanks for the reply.

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


Re: [Evolution] Unable to retrieve message.

2015-11-09 Thread Ritesh Khadgaray
Hi

On Nov 9, 2015 9:52 PM, "Fedora"  wrote:
>
> I have a problem with Evolution Mail (version 3.16.5) that is steadily
getting worse.
>
> I get lots of (typically) ...
>
> "Unable to retrieve message.
>
> Cannot get message 1445510505.6156_169.ceri from folder
/home/mike/.local/share/evolution/mail/local/.House.BT Bills: No such file
or directory"
>
> If I click away to a different message in a different folder, then come
back to the email giving this message, then the email appears OK. So now
having read the message, if I shut down Evolution, and restart, then an
email that was giving error, appears again as unread, with the "Unable to
retrieve message". Also If I delete one of these messages, it simply
reappears on the next start of Evolution.
>
> I have tried a backup and restore. Makes no difference.
>
> At this point I guess I should say I've got about 15 years worth of
emails here - about 12Gb in ~/.local/share/evolution/mail
>
> Has anyone got any hints or tips for sorting this out ?
>
> Thanks
>

You might want to clear the cache and check -
https://wiki.debian.org/Evolution

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


Re: [Evolution] Unable to retrieve message.

2014-06-26 Thread Svante Signell
On Wed, 2014-06-25 at 09:28 +0200, Milan Crha wrote:
 On Tue, 2014-06-24 at 11:45 +0200, Svante Signell wrote:
  
 Thanks for your help. Unfortunately I did not get anything reasonable
  out of this. gdb is hanging the whole desktop. I have to get out of
  graphic mode and kill gdb each time.
 
 Hi,
 then run gdb from the text terminal instead, like this:
$ export DISPLAY=:0.0
$ gdb evolution ...
 With that the evolution will run in the graphics part of the desktop 
 and whenever it freezes you can switch to the text terminal and do the 
 gdb commands there.

Thanks for your tip. I'll check this ASAP.

BTW: A new thing causing evo to crash:

CAMEL_DEBUG=imapx:io evolution  logfile
tail logfile 

[imapx:Q] I/O: ' UID 10551310)
Q08843 OK FETCH completed.'

(evolution:13072): camel-imapx-CRITICAL **: camel_imapx_command_ref:
assertion 'CAMEL_IS_IMAPX_COMMAND (ic)' failed

(evolution:13072): camel-imapx-WARNING **:
camel_imapx_command_queue_delete_link: Link not found in queue

(evolution:13072): camel-imapx-CRITICAL **:
imapx_server_command_removed: assertion 'command != NULL' failed

(evolution:13072): camel-imapx-CRITICAL **: camel_imapx_command_close:
assertion 'CAMEL_IS_IMAPX_COMMAND (ic)' failed


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


Re: [Evolution] Unable to retrieve message.

2014-06-25 Thread Milan Crha
On Tue, 2014-06-24 at 11:45 +0200, Svante Signell wrote:
 
Thanks for your help. Unfortunately I did not get anything reasonable
 out of this. gdb is hanging the whole desktop. I have to get out of
 graphic mode and kill gdb each time.

Hi,
then run gdb from the text terminal instead, like this:
   $ export DISPLAY=:0.0
   $ gdb evolution ...
With that the evolution will run in the graphics part of the desktop 
and whenever it freezes you can switch to the text terminal and do the 
gdb commands there.
Bye,
Milan


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


Re: [Evolution] Unable to retrieve message.

2014-06-24 Thread Milan Crha
On Mon, 2014-06-23 at 15:07 +0200, Svante Signell wrote:
 
Howe to make gdb stop at the correct thread to get a backtrace?
 Continuing.
 [New Thread 0x7fff56ffd700 (LWP 24666)]
  
 (evolution:24607): GLib-GObject-CRITICAL **: g_closure_unref: 
 assertion
 'closure-ref_count  0' failed
  
 (evolution:24607): GLib-GIO-CRITICAL **: g_output_stream_write_all:
 assertion 'buffer != NULL' failed
 [Thread 0x7fff314c0700 (LWP 24644) exited]
 [Thread 0x7fff56ffd700 (LWP 24666) exited]
 [New Thread 0x7fff56ffd700 (LWP 24679)]

Hi,
try this:
   $ gdb evolution --ex r --ex b g_logv --ex c
which runs evolution under gdb and just before you will face the 
critical warning from the top (the second, not the first, which comes 
from webkitgtk3 code) press Ctrl+C, which will setup a breakpoint and 
continue in execution. Since then, the gdb will stop on each warning, 
debug message,... anything printed through that g_logv() function. 
Whenever it stops there, do these two gdb commands:
   (gdb) bt
   (gdb) c
which will print the backtrace and continue. Alternatively, you can use
   (gdb) bt full
to see also local variables and so on. Once you get the backtrace of 
the critical warning you wanted, just delete the breakpoint and 
continue
   (gdb) d br 1
   (gdb) c
once you quit evolution quit also gdb
   (gdb) q

The backtrace will show where the 'buffer' was NULL, though it will 
probably not show why. Still, the information might be valuable.
Bye,
Milan


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


Re: [Evolution] Unable to retrieve message.

2014-06-24 Thread Svante Signell
On Tue, 2014-06-24 at 08:05 +0200, Milan Crha wrote:
 On Mon, 2014-06-23 at 15:07 +0200, Svante Signell wrote:
  

 Hi,
 try this:

 The backtrace will show where the 'buffer' was NULL, though it will 
 probably not show why. Still, the information might be valuable.

Thanks for your help. Unfortunately I did not get anything reasonable
out of this. gdb is hanging the whole desktop. I have to get out of
graphic mode and kill gdb each time.

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


Re: [Evolution] Unable to retrieve message.

2014-06-24 Thread Svante Signell
On Tue, 2014-06-24 at 11:45 +0200, Svante Signell wrote:
 On Tue, 2014-06-24 at 08:05 +0200, Milan Crha wrote:
  On Mon, 2014-06-23 at 15:07 +0200, Svante Signell wrote:
   
 
  Hi,
  try this:
 
  The backtrace will show where the 'buffer' was NULL, though it will 
  probably not show why. Still, the information might be valuable.
 
 Thanks for your help. Unfortunately I did not get anything reasonable
 out of this. gdb is hanging the whole desktop. I have to get out of
 graphic mode and kill gdb each time.

A new data point: The messages I have problems to retrieve with version
3.12.2-1 does not show with 3.12.1-1 (Debian versions)


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


Re: [Evolution] Unable to retrieve message.

2014-06-23 Thread Svante Signell
On Wed, 2014-06-18 at 23:42 +0200, Svante Signell wrote:
 On Wed, 2014-06-18 at 16:34 +0100, Pete Biggs wrote:
   Removed folders.db and recerated it from .cache/evolution/mail/.../ and
   recreated it:
   
   (evolution:5139): GLib-GObject-CRITICAL **: g_closure_unref: assertion
   'closure-ref_count  0' failed
  .
  .
   
   (evolution:5139): GLib-GIO-CRITICAL **: g_output_stream_write_all:
   assertion 'buffer != NULL' failed
   [imapx:B] Data read failed with error 'unexpected server response:'
   [imapx:B] I/O: ''
   
  
  Again your email just stopped - was there more you wanted to add
  underneath this? Like some form of explanation, comment or question?
 
 The logfile ended there, no more output with
 CAMEL_DEBUG=imapx:io evolution  logfile 

Another unreadable message (there are plenty of them):
tail -50l logfile:
email message
+#endif /* ! GRUB_TYPES_CPU_HEADER */
diff --git a/i386/grub/err.h b/i386/grub/err.h
new file mode 100644
index 000..1590c68
--- /dev/null
+++ b/i386/grub/err.h
@@ -0,0 +1,96 @@
+/* err.'
[imapx:D] I/O: ' UID 9965782)
D00041 OK FETCH completed.'
[imapx:D] I/O: 'D00047 UID FETCH 9965782 (BODY.PEEK[]102400.20480)'
[imapx:D] I/O: 'D00046 UID FETCH 9965782 (BODY.PEEK[]81920.20480)'
[imapx:D] I/O: 'D00045 UID FETCH 9965782 (BODY.PEEK[]61440.20480)'
[imapx:D] I/O: '* 50558 FETCH (BODY[]102400  UID 9965782)'

(evolution:20130): GLib-GIO-CRITICAL **: g_output_stream_write_all:
assertion 'buffer != NULL' failed
[imapx:D] Data read failed with error 'unexpected server response:'
[imapx:D] I/O: ''


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


Re: [Evolution] Unable to retrieve message.

2014-06-23 Thread Andre Klapper
On Mon, 2014-06-23 at 11:13 +0200, Svante Signell wrote:
 Another unreadable message (there are plenty of them):
 tail -50l logfile:
 email message
 +#endif /* ! GRUB_TYPES_CPU_HEADER */
 diff --git a/i386/grub/err.h b/i386/grub/err.h
 new file mode 100644
 index 000..1590c68
 --- /dev/null
 +++ b/i386/grub/err.h
 @@ -0,0 +1,96 @@
 +/* err.'

Evolution hanging when parsing patches reminds me of
https://bugzilla.gnome.org/show_bug.cgi?id=724909 but that's on a
rendering level, not on a fetching mail level... :-/

andre
-- 
Andre Klapper  |  ak...@gmx.net
http://blogs.gnome.org/aklapper/

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


Re: [Evolution] Unable to retrieve message.

2014-06-23 Thread Svante Signell
On Mon, 2014-06-23 at 12:23 +0200, Andre Klapper wrote:
 On Mon, 2014-06-23 at 11:13 +0200, Svante Signell wrote:
  Another unreadable message (there are plenty of them):
  tail -50l logfile:
  email message
  +#endif /* ! GRUB_TYPES_CPU_HEADER */
  diff --git a/i386/grub/err.h b/i386/grub/err.h
  new file mode 100644
  index 000..1590c68
  --- /dev/null
  +++ b/i386/grub/err.h
  @@ -0,0 +1,96 @@
  +/* err.'
 
 Evolution hanging when parsing patches reminds me of
 https://bugzilla.gnome.org/show_bug.cgi?id=724909 but that's on a
 rendering level, not on a fetching mail level... :-/

Howe to make gdb stop at the correct thread to get a backtrace?
Continuing.
[New Thread 0x7fff56ffd700 (LWP 24666)]

(evolution:24607): GLib-GObject-CRITICAL **: g_closure_unref: assertion
'closure-ref_count  0' failed

(evolution:24607): GLib-GIO-CRITICAL **: g_output_stream_write_all:
assertion 'buffer != NULL' failed
[Thread 0x7fff314c0700 (LWP 24644) exited]
[Thread 0x7fff56ffd700 (LWP 24666) exited]
[New Thread 0x7fff56ffd700 (LWP 24679)]


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


Re: [Evolution] Unable to retrieve message.

2014-06-18 Thread Pete Biggs
On Tue, 2014-06-17 at 20:51 +0200, Svante Signell wrote:
 ping

Ah, the old subtle hint that you want a reply because you think you are
being ignored - and I thought the correct form these days was bump.


  CAMEL_DEBUG=imapx:io evolution  logfile
  ...
  HTML CODE
  /div
  /body'
  [imapx:A] I/O: '/html
  
  --0616-0715-21-03-PART_BREAK--'
  [imapx:A] I/O: ' UID 10496318)
  A00029 OK FETCH completed.'
  [imapx:A] I/O: '* 52197 FETCH (BODY[]20480  UID 10496318)'
  
  (evolution:7521): GLib-GIO-CRITICAL **: g_output_stream_write_all: 
  assertion 'buffer != NULL' failed
  [imapx:A] Data read failed with error 'unexpected server response:'
  [imapx:A] I/O: ''
  
I thought there was more info to come since your email just ended
abruptly at that point.

The problem looks like you are getting a null response when requesting
the body of a message.  Try removing the local mail folder summary as
before.  If that doesn't work, then you need to look at the server logs
to see what's happening.

P.

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


Re: [Evolution] Unable to retrieve message.

2014-06-18 Thread Svante Signell
On Wed, 2014-06-18 at 09:35 +0100, Pete Biggs wrote:
 On Tue, 2014-06-17 at 20:51 +0200, Svante Signell wrote:
  ping
 
 Ah, the old subtle hint that you want a reply because you think you are
 being ignored - and I thought the correct form these days was bump.

Never seen that.

 
   CAMEL_DEBUG=imapx:io evolution  logfile
   ...
   HTML CODE
   /div
   /body'
   [imapx:A] I/O: '/html
   
   --0616-0715-21-03-PART_BREAK--'
   [imapx:A] I/O: ' UID 10496318)
   A00029 OK FETCH completed.'
   [imapx:A] I/O: '* 52197 FETCH (BODY[]20480  UID 10496318)'
   
   (evolution:7521): GLib-GIO-CRITICAL **: g_output_stream_write_all: 
   assertion 'buffer != NULL' failed
   [imapx:A] Data read failed with error 'unexpected server response:'
   [imapx:A] I/O: ''
   
 I thought there was more info to come since your email just ended
 abruptly at that point.

No more info came out.

 The problem looks like you are getting a null response when requesting
 the body of a message.  Try removing the local mail folder summary as
 before.  If that doesn't work, then you need to look at the server logs
 to see what's happening.

Which file, folders.db?
INBOX.ibex.index.data
INBOX.ibex.index
folders.db
INBOX.cmeta


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


Re: [Evolution] Unable to retrieve message.

2014-06-18 Thread Pete Biggs

 
  The problem looks like you are getting a null response when requesting
  the body of a message.  Try removing the local mail folder summary as
  before.  If that doesn't work, then you need to look at the server logs
  to see what's happening.
 
 Which file, folders.db?
 INBOX.ibex.index.data
 INBOX.ibex.index
 folders.db
 INBOX.cmeta
 
 

folders.db - make sure evolution is closed down first before you do it
though.

P.


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


Re: [Evolution] Unable to retrieve message.

2014-06-18 Thread Svante Signell
On Wed, 2014-06-18 at 10:03 +0100, Pete Biggs wrote:
  
   The problem looks like you are getting a null response when requesting
   the body of a message.  Try removing the local mail folder summary as
   before.  If that doesn't work, then you need to look at the server logs
   to see what's happening.
  
  Which file, folders.db?

 folders.db - make sure evolution is closed down first before you do it
 though.

Removed folders.db and recerated it from .cache/evolution/mail/.../ and
recreated it:

(evolution:5139): GLib-GObject-CRITICAL **: g_closure_unref: assertion
'closure-ref_count  0' failed
[imapx:B] I/O: 'B00259 UID FETCH 10496485 (BODY.PEEK[]0.20480)'
[imapx:B] I/O: 'B00260 UID FETCH 10496485 (BODY.PEEK[]20480.20480)'
[imapx:B] I/O: '* 52360 FETCH (BODY[]0 {17082}
Received: from smtp-4.sys.kth.se (130.237.48.193) by EXHUB1.ug.kth.se
mail headers
Content-Type: multipart/signed; protocol=application/pkcs7-signature;
micalg=sha1; boundary=ms060004010806040304050106
X-MS-stuff
MIME-Version: 1.0

--ms060004010806040304050106
Content-Type: multipart/alternative;
 boundary=020707070807050403060807

This is a multi-part message in MIME format.
--020707070807050403060807
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
...

 Original Message 
...

--020707070807050403060807
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
html
...
/html

--020707070807050403060807--

--ms060004010806040304050106
Content-Type: application/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename=smime.p7s
Content-Description: S/MIME Cryptographic Signature
...
--ms060004010806040304050106--'
[imapx:B] I/O: ' UID 10496485)
B00259 OK FETCH completed.'
[imapx:B] I/O: '* 52360 FETCH (BODY[]20480  UID 10496485)'

(evolution:5139): GLib-GIO-CRITICAL **: g_output_stream_write_all:
assertion 'buffer != NULL' failed
[imapx:B] Data read failed with error 'unexpected server response:'
[imapx:B] I/O: ''


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


Re: [Evolution] Unable to retrieve message.

2014-06-18 Thread Svante Signell
On Wed, 2014-06-18 at 16:34 +0100, Pete Biggs wrote:
  Removed folders.db and recerated it from .cache/evolution/mail/.../ and
  recreated it:
  
  (evolution:5139): GLib-GObject-CRITICAL **: g_closure_unref: assertion
  'closure-ref_count  0' failed
 .
 .
  
  (evolution:5139): GLib-GIO-CRITICAL **: g_output_stream_write_all:
  assertion 'buffer != NULL' failed
  [imapx:B] Data read failed with error 'unexpected server response:'
  [imapx:B] I/O: ''
  
 
 Again your email just stopped - was there more you wanted to add
 underneath this? Like some form of explanation, comment or question?

The logfile ended there, no more output with
CAMEL_DEBUG=imapx:io evolution  logfile 

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


Re: [Evolution] Unable to retrieve message.

2014-06-17 Thread Svante Signell
ping

On Mon, 2014-06-16 at 10:34 +0200, Svante Signell wrote:
 On Mon, 2014-06-16 at 09:22 +0100, Pete Biggs wrote:
  On Mon, 2014-06-16 at 09:57 +0200, Svante Signell wrote:
   Now I'm getting problems with some emails on one of my imapx accounts:
   
   Unable to retrieve message.
   Error fetching message: unexpected server response:
   
  
  That error message doesn't exactly give any clues as to where the
  problem is, so, as I said in a message further up the thread you've
  hijacked:
 
 Sorry, I edited an old email, should have created a new thread.
 
   
   Try running Evolution from the command line, that should give a bit more
   info.  If it doesn't, then run it with debugging enabled - see 
   
 https://wiki.gnome.org/Apps/Evolution/Debugging
  
 CAMEL_DEBUG=imapx:io evolution  logfile
 ...
 HTML CODE
 /div
 /body'
 [imapx:A] I/O: '/html
 
 --0616-0715-21-03-PART_BREAK--'
 [imapx:A] I/O: ' UID 10496318)
 A00029 OK FETCH completed.'
 [imapx:A] I/O: '* 52197 FETCH (BODY[]20480  UID 10496318)'
 
 (evolution:7521): GLib-GIO-CRITICAL **: g_output_stream_write_all: assertion 
 'buffer != NULL' failed
 [imapx:A] Data read failed with error 'unexpected server response:'
 [imapx:A] I/O: ''
 
 


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


Re: [Evolution] Unable to retrieve message.

2014-06-17 Thread Ralf Mardorf
On Tue, 2014-06-17 at 20:51 +0200, Svante Signell wrote:
 ping

A short advice. IMHO even man ping is hard to understand, at least for
using it to troubleshoot the issue the OP is experiencing. Please reply
more detailed, IOW how to use ping to troubleshoot this particular
problem. I'm using ping to ensure that a website is really off, e.g.

$ ping startpage.com

How could the OP use ping for troubleshooting? My Linux domain for
example is Linux audio userspace and not Linux Internet userspace, some
people perhaps have completely no experiences, no domain.

No offence ;), your hint likely is useful, but please be reply more
elaborate.

TIA,
Ralf

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


Re: [Evolution] Unable to retrieve message.

2014-06-16 Thread Pete Biggs
On Mon, 2014-06-16 at 09:57 +0200, Svante Signell wrote:
 Now I'm getting problems with some emails on one of my imapx accounts:
 
 Unable to retrieve message.
 Error fetching message: unexpected server response:
 

That error message doesn't exactly give any clues as to where the
problem is, so, as I said in a message further up the thread you've
hijacked:

 
 Try running Evolution from the command line, that should give a bit more
 info.  If it doesn't, then run it with debugging enabled - see 
 
   https://wiki.gnome.org/Apps/Evolution/Debugging
 

P.

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


Re: [Evolution] Unable to retrieve message.

2014-06-16 Thread Svante Signell

On Mon, 2014-06-16 at 09:22 +0100, Pete Biggs wrote:
 On Mon, 2014-06-16 at 09:57 +0200, Svante Signell wrote:
  Now I'm getting problems with some emails on one of my imapx accounts:
  
  Unable to retrieve message.
  Error fetching message: unexpected server response:
  
 
 That error message doesn't exactly give any clues as to where the
 problem is, so, as I said in a message further up the thread you've
 hijacked:

Sorry, I edited an old email, should have created a new thread.

  
  Try running Evolution from the command line, that should give a bit more
  info.  If it doesn't, then run it with debugging enabled - see 
  
https://wiki.gnome.org/Apps/Evolution/Debugging
 
CAMEL_DEBUG=imapx:io evolution  logfile
...
HTML CODE
/div
/body'
[imapx:A] I/O: '/html

--0616-0715-21-03-PART_BREAK--'
[imapx:A] I/O: ' UID 10496318)
A00029 OK FETCH completed.'
[imapx:A] I/O: '* 52197 FETCH (BODY[]20480  UID 10496318)'

(evolution:7521): GLib-GIO-CRITICAL **: g_output_stream_write_all: assertion 
'buffer != NULL' failed
[imapx:A] Data read failed with error 'unexpected server response:'
[imapx:A] I/O: ''


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


Re: [Evolution] Unable to retrieve message

2009-11-08 Thread Patrick O'Callaghan
On Sat, 2009-11-07 at 20:03 +0100, Felix Koop wrote:
 
 Am Samstag, den 07.11.2009, 11:15 -0500 schrieb Philippe LeCavalier:
  On Sat, 2009-11-07 at 17:09 +0100, Felix Koop wrote: 
   I don't have an IMAP server. The INBOX is on local storage and I get all
   of my mail from POP servers.
   
   ---
   Kind regards, Felix
   
  The same can be done with POP just google 'pop3 command line'.
  
  P.S. you responded to me and not the list.
  
  Cheers,
  Phil
 
 Just to be sure: The folder in which I get this message is not on any
 server, but on the local machine. But I looked up all servers and there
 is no message in the inbox of any server (not anything that resembles
 this dead message by any means).

The only other thing I can think of is a corrupted mbox file. You might
try passing it through formail (part of the procmail package) which can
clean up problems like this. Or even looking at it with an editor (e.g.
if there's a non-ASCII character in there somewhere it could cause
problems).

poc

___
Evolution-list mailing list
Evolution-list@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Unable to retrieve message

2009-11-08 Thread Felix Koop


Am Sonntag, den 08.11.2009, 10:09 -0430 schrieb Patrick O'Callaghan:
 On Sat, 2009-11-07 at 20:03 +0100, Felix Koop wrote:
  
  Just to be sure: The folder in which I get this message is not on any
  server, but on the local machine. But I looked up all servers and there
  is no message in the inbox of any server (not anything that resembles
  this dead message by any means).
 
 The only other thing I can think of is a corrupted mbox file. You might
 try passing it through formail (part of the procmail package) which can
 clean up problems like this. Or even looking at it with an editor (e.g.
 if there's a non-ASCII character in there somewhere it could cause
 problems).
 
 poc
 

That didn't help. But I found another solution that did work: deleting
folders.db. When deleting index files, I only deleted *.cmeta, *.index,
*.index.data, *.ev-summary and *.ev-summary-meta. Now that I deleted
folders.db the mail seemed to go away.

---
Kind regards, Felix


___
Evolution-list mailing list
Evolution-list@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Unable to retrieve message

2009-11-08 Thread Philippe LeCavalier
On Sun, 2009-11-08 at 18:51 +0100, Felix Koop wrote:

 
 Am Sonntag, den 08.11.2009, 10:09 -0430 schrieb Patrick O'Callaghan:
  On Sat, 2009-11-07 at 20:03 +0100, Felix Koop wrote:
   
   Just to be sure: The folder in which I get this message is not on any
   server, but on the local machine. But I looked up all servers and there
   is no message in the inbox of any server (not anything that resembles
   this dead message by any means).
  
  The only other thing I can think of is a corrupted mbox file. You might
  try passing it through formail (part of the procmail package) which can
  clean up problems like this. Or even looking at it with an editor (e.g.
  if there's a non-ASCII character in there somewhere it could cause
  problems).
  
  poc
  
 
 That didn't help. But I found another solution that did work: deleting
 folders.db. When deleting index files, I only deleted *.cmeta, *.index,
 *.index.data, *.ev-summary and *.ev-summary-meta. Now that I deleted
 folders.db the mail seemed to go away.
 

I remember once I had to do that. Can't remember why but that had fixed
my problem at the time as well.

Glad to hear you're in the clear!

Cheers,
Phil
___
Evolution-list mailing list
Evolution-list@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Unable to retrieve message

2009-11-08 Thread Patrick O'Callaghan
On Sun, 2009-11-08 at 18:51 +0100, Felix Koop wrote:
 
 Am Sonntag, den 08.11.2009, 10:09 -0430 schrieb Patrick O'Callaghan:
  On Sat, 2009-11-07 at 20:03 +0100, Felix Koop wrote:
   
   Just to be sure: The folder in which I get this message is not on any
   server, but on the local machine. But I looked up all servers and there
   is no message in the inbox of any server (not anything that resembles
   this dead message by any means).
  
  The only other thing I can think of is a corrupted mbox file. You might
  try passing it through formail (part of the procmail package) which can
  clean up problems like this. Or even looking at it with an editor (e.g.
  if there's a non-ASCII character in there somewhere it could cause
  problems).
  
  poc
  
 
 That didn't help. But I found another solution that did work: deleting
 folders.db. When deleting index files, I only deleted *.cmeta, *.index,
 *.index.data, *.ev-summary and *.ev-summary-meta. Now that I deleted
 folders.db the mail seemed to go away.

You should probably report this to Bugzilla. It means that even
vacuuming the database didn't fix the problem.

poc

___
Evolution-list mailing list
Evolution-list@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Unable to retrieve message

2009-11-07 Thread Felix Koop


Am Freitag, den 06.11.2009, 19:40 -0430 schrieb Patrick O'Callaghan:
 On Fri, 2009-11-06 at 23:56 +0100, Felix Koop wrote:
 You could try vacuuming the SQL database files (shutting down Evo first
 of course):
 
 #!/bin/sh
 
 cd ~/.evolution/mail/
 for i in `find . -name folders.db`
 do
 echo Rebuilding Table $i
 sqlite3 $i vacuum;
 done
 
 If that doesn't work, I'm out of ideas.
 
 poc

Very strange. If I delete all of the index files and vacuum the database
files, then restart evoilution, the message is not there. I can try and
get all of my mails and the message will not appear. If I then shut down
evolution and restart it, then the message is back. :-(

Additionally, when I try to visualize the message, then change message
folders, then come back to the Inbox, then the message is no longer
visible, not even in the listing where I did see it before.

Anyone with any ideas?

---
Kind regards,

Felix

___
Evolution-list mailing list
Evolution-list@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Unable to retrieve message

2009-11-07 Thread Felix Koop


Am Samstag, den 07.11.2009, 09:32 -0430 schrieb Patrick O'Callaghan:
 On Sat, 2009-11-07 at 08:59 +0100, Felix Koop wrote:
  
  Very strange. If I delete all of the index files and vacuum the database
  files, then restart evoilution, the message is not there. I can try and
  get all of my mails and the message will not appear. If I then shut down
  evolution and restart it, then the message is back. :-(
 
 Did you shut down Evo *before* removing the index files and vacuuming
 the database?
 
 poc
 

Sure. I executed evolution --force-shutdown, then cleaned all of the
index files, then vacuumed the database and then restarted evolution.

---
Kind regards, Felix

___
Evolution-list mailing list
Evolution-list@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Unable to retrieve message

2009-11-07 Thread Felix Koop


Am Samstag, den 07.11.2009, 11:15 -0500 schrieb Philippe LeCavalier:
 On Sat, 2009-11-07 at 17:09 +0100, Felix Koop wrote: 
  I don't have an IMAP server. The INBOX is on local storage and I get all
  of my mail from POP servers.
  
  ---
  Kind regards, Felix
  
 The same can be done with POP just google 'pop3 command line'.
 
 P.S. you responded to me and not the list.
 
 Cheers,
 Phil

Just to be sure: The folder in which I get this message is not on any
server, but on the local machine. But I looked up all servers and there
is no message in the inbox of any server (not anything that resembles
this dead message by any means).

---
Kind regards, Felix

___
Evolution-list mailing list
Evolution-list@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-list