[Evolution] MOVE in imapx and unexpected server response

[Valentin David]

Here is what I get in the logs:

[imapx:C] I/O: 'C00109 UID MOVE 179221 "Commit mseq"'
[imapx:C] I/O: '[COPYUID 35 179221 15912]
* 17915 EXPUNGE
* 17926 EXISTS
C00109 OK MOVE completed.'
[imapx:C] Data read failed with error 'unexpected server response:'

I suppose that the "EXISTS" is not expected. This error happens for 
every move. It makes my filter completely useless when there is more 
than one move.

Tested with evolution-data-server 3.12.4 and 3.13.6.

-- 
Valentin David
This email reflects my own opinion. You have the right to disagree.

___
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] Fast full-text search of e-mails?

[Pete Biggs]

On Wed, 2014-11-05 at 07:35 +0100, Karsten Kloss wrote:
> Am Dienstag, den 04.11.2014, 12:17 -0700 schrieb Michael Barraclough:
> > On Sun, 2014-11-02 at 18:06 +, Pete Biggs wrote: 
> > > but if they are local folders (i.e. for a POP account), then
> > > right-click on the folder select Properties and make sure "Index message
> > > body data" is checked.
> > 
> If I check it or not, nothing changes. When restarting Evolution the
> check box is always not checked. Is something missing?

As others have said in this thread, it's broken.  See

https://mail.gnome.org/archives/evolution-list/2014-November/msg00014.html

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] [Bulk] Fast full-text search of e-mails?

[Adam Tauno Williams]

On Thu, 2014-11-06 at 00:05 +, Patrick O'Callaghan wrote: 
> On Tue, 2014-11-04 at 13:10 -0500, Adam Tauno Williams wrote:
> > IMAP SEARCH doesn't work?
> Why ask me? 

You are the one with a Gmail account;  my question was if their
implementation of IMAP SEARCH works.

> * Using Evo on the IMAP-connected Google account took 70 seconds, giving
> 51 results. I have a fairly fast desktop machine (i7 cpu with 16GB of
> RAM and the root filesystem on an SSD). This is Evo 3.10.4.

I would expect the client not to matter much if it is using IMAP SEARCH
- because then the server does the work. 

> * Using the Gmail web interface on the same account gave the same
> results in under 1 second.

So either 
(a) Evolution did not ask the server to do the search 
  - or - 
(b) their implementation of IMAP search is lame. 

> So yes, having some special-purpose Google API code probably would help.

I don't see why; IMAP implements server-side search.


A variety of IMAP servers provide some mechanism of content indexing.

If an implementation of SEARCH is lame the maintainers should fix it.

-- 
Adam Tauno Williams  GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA

___
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] MOVE in imapx and unexpected server response

[Milan Crha]

On Wed, 2014-11-05 at 13:26 +0100, Valentin David wrote:
> Here is what I get in the logs:
> 
> [imapx:C] I/O: 'C00109 UID MOVE 179221 "Commit mseq"'
> [imapx:C] I/O: '[COPYUID 35 179221 15912]
> * 17915 EXPUNGE
> * 17926 EXISTS
> C00109 OK MOVE completed.'
> [imapx:C] Data read failed with error 'unexpected server response:'
> 
> I suppose that the "EXISTS" is not expected. This error happens for 
> every move. It makes my filter completely useless when there is more 
> than one move.
> 
> Tested with evolution-data-server 3.12.4 and 3.13.6.

Hi,
your IMAP server advertises that it supports UID MOVE, thus the IMAPx 
in Evolution tries to use it. The problem is that the server returns 
something what it might not, according to the IMAPx implementation 
expectations. The '*' at the beginning of the line is fine, it denotes 
untagged responses, which can come anytime. The problem might be with 
the first line, the '[COPYUID...]'.

When I look into an example of the client <-> server communication of 
the UID MOVE IMAP command at RFC 6851 [1], then I see there a 
difference, the "[COPYUID..." in the example is prefixed with "* OK", 
which is missing in your IMAPx log.
Bye,
Milan

[1] https://tools.ietf.org/html/rfc6851#page-4
___
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] [Bulk] Fast full-text search of e-mails?

[Patrick O'Callaghan]

On Thu, 2014-11-06 at 06:39 -0500, Adam Tauno Williams wrote:
> On Thu, 2014-11-06 at 00:05 +, Patrick O'Callaghan wrote: 
> > On Tue, 2014-11-04 at 13:10 -0500, Adam Tauno Williams wrote:
> > > IMAP SEARCH doesn't work?
> > Why ask me? 
> 
> You are the one with a Gmail account;  my question was if their
> implementation of IMAP SEARCH works.

Apologies, I thought you were asking a more general question.

> > * Using Evo on the IMAP-connected Google account took 70 seconds, giving
> > 51 results. I have a fairly fast desktop machine (i7 cpu with 16GB of
> > RAM and the root filesystem on an SSD). This is Evo 3.10.4.
> 
> I would expect the client not to matter much if it is using IMAP SEARCH
> - because then the server does the work. 
> 
> > * Using the Gmail web interface on the same account gave the same
> > results in under 1 second.
> 
> So either 
> (a) Evolution did not ask the server to do the search 
>   - or - 
> (b) their implementation of IMAP search is lame. 

Without tracing Evo, I can't say which of these is the answer, though I
suspect it's probably (a). Google obviously does do search (duh) and
there's no reason why it should do it badly just because it's an IMAP
connection, even if their IMAP implementation is not the best. I don't
know how Evo decides whether the server can do searching.

> > So yes, having some special-purpose Google API code probably would help.
> 
> I don't see why; IMAP implements server-side search.
> 

I was actually thinking of other stuff like support for Gmail labels,
conversation threads, spam filtering etc. See
http://techcrunch.com/2014/06/26/no-the-new-gmail-api-is-not-killing-imap/

poc

___
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] [Bulk] Fast full-text search of e-mails?

[Milan Crha]

On Thu, 2014-11-06 at 21:41 +, Patrick O'Callaghan wrote:
> On Thu, 2014-11-06 at 06:39 -0500, Adam Tauno Williams wrote:
> > So either
> > (a) Evolution did not ask the server to do the search
> >   - or -
> > (b) their implementation of IMAP search is lame.
> 
> Without tracing Evo, I can't say which of these is the answer, 
> though I suspect it's probably (a). Google obviously does do search 
> (duh) and there's no reason why it should do it badly just because 
> it's an IMAP connection, even if their IMAP implementation is not 
> the best. I don't know how Evo decides whether the server can do 
> searching.
> 

Hi,
I tried to trace it (better know than guess). I invoked a simple "body 
contains evolution" search on a GMail Inbox folder from evolution and 
that was done server-side, as can be seen here:
   H02430 UID SEARCH BODY "evolution"
   * SEARCH 112 116 376 468 748
   H02430 OK SEARCH completed (Success)

I think it depends on the search itself, but the IMAPx tries to search 
as much on the server as it can. Searching in summary headers is left 
for a local search, of course.


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