[Evolution] Failed to refresh folder INBOX

2014-06-13 Thread Svante Signell
Hi,

Recently evolution shows the following message when accessing my IMAP
account or expunging the folder:
Failed to refresh folder INBOX.
The reported error was Error syncing changes: Command Argument Error.
11

What to do? The problem is stuck on this particular box, and is not
present on other boxes I use to access that email account with evo.

Installed packages (Debian):
ii  evolution 3.12.2-1 amd64  
ii  evolution-common 3.12.2-1 all
ii  evolution-data-server 3.12.2-1 amd64
ii  evolution-data-server-common 3.12.2-1 all
ii  evolution-plugins 3.12.2-1 amd64
ii  evolution-plugins-experimental 3.12.2-1 amd64
ii  libebackend-1.2-7 3.12.2-1 amd64
ii  libebook-1.2-14 3.12.2-1 amd64
ii  libebook-contacts-1.2-0 3.12.2-1 amd64
ii  libecal-1.2-16 3.12.2-1 amd64
ii  libedata-book-1.2-20 3.12.2-1 amd64
ii  libedata-cal-1.2-23 3.12.2-1 amd64
ii  libedataserver-1.2-18 3.12.2-1 amd64
ii  libevolution 3.12.2-1 amd64


___
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] unwanted information disclosure

2014-06-13 Thread Milan Crha
On Thu, 2014-06-12 at 13:18 -0400, Eugene Kanter wrote:
 https://bugzilla.gnome.org/show_bug.cgi?id=702703
 
 Almost a year later, are there any plans to address the problem?
 I am tired of applying my dirty patch every time a new 
 evolution-data-server package comes out.

Hi,
well, I'm sorry, but almost a year old bug report and the only person
interested in it (according to CC, where is me and Andre) is you.

I do not know, did you ever check what for example Google does? I did
try it right now, I sent an email from their web UI to myself and guess
what, the header looks like this:

   Message-ID: 
CAP0iMMiCt_c113w3yZFeGBzrp=ky8j_h1cu2j2-s5mrbpbr...@mail.gmail.com

Is it wrong that they exposed the mail.gmail.com in the message ID?
No, I do not think so. I would not worry about it.

I didn't try anything like thunderbird, clawsmail, mutt, geary, ..., but
I would not be surprised if they do the same - following the RFC.

On the other hand, I agree that there can be valid reasons why you want
to be hidden, but that didn't strike any huge attention by anyone else
security aware, thus your bug report has a pretty low priority.
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] Failed to refresh folder INBOX

2014-06-13 Thread Pete Biggs

 
 Recently evolution shows the following message when accessing my IMAP
 account or expunging the folder:
 Failed to refresh folder INBOX.
 The reported error was Error syncing changes: Command Argument Error.
 11
 

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

Basically you need to find out what command (and arguments) is causing
that error.

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] evolution freezes on some xml attachments

2014-06-13 Thread Milan Crha
On Thu, 2014-06-12 at 13:27 -0400, Eugene Kanter wrote:
 A complete application freeze is a serious problem and IMHO should be 
 addressed officially.

Hi,
I do not think a backport will be possible, the other parts of the code
changed significantly. There is a workaround, run this as root:
   $ rm /usr/lib64/evolution/3.10/modules/module-text-highlight.so
(correct path accordingly, for example 'lib' instead of 'lib64'). That
will get rid of the failing part and you'll get a proper behaviour
again.
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] Failed to refresh folder INBOX

2014-06-13 Thread Svante Signell
On Fri, 2014-06-13 at 10:53 +0100, Pete Biggs wrote:
  
  Recently evolution shows the following message when accessing my IMAP
  account or expunging the folder:
  Failed to refresh folder INBOX.
  The reported error was Error syncing changes: Command Argument Error.
  11
  
 
 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
 
 Basically you need to find out what command (and arguments) is causing
 that error.

With   CAMEL_DEBUG=imapx:io evolution  logfile  I get
(evolution:30280): GLib-GObject-CRITICAL **: g_closure_unref: assertion
'closure-ref_count  0' failed
[imapx:D] I/O: 'D00037 UID STORE 10496159 +FLAGS.SILENT (JUNK)'
[imapx:D] I/O: 'D00037 BAD Command Argument Error. 11'


___
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] Failed to refresh folder INBOX

2014-06-13 Thread Svante Signell
On Fri, 2014-06-13 at 12:16 +0200, Svante Signell wrote:
 On Fri, 2014-06-13 at 10:53 +0100, Pete Biggs wrote:
   
   Recently evolution shows the following message when accessing my IMAP
   account or expunging the folder:
   Failed to refresh folder INBOX.
   The reported error was Error syncing changes: Command Argument Error.
   11
   
  
  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
  
  Basically you need to find out what command (and arguments) is causing
  that error.
 
 With   CAMEL_DEBUG=imapx:io evolution  logfile  I get
 (evolution:30280): GLib-GObject-CRITICAL **: g_closure_unref: assertion
 'closure-ref_count  0' failed
 [imapx:D] I/O: 'D00037 UID STORE 10496159 +FLAGS.SILENT (JUNK)'
 [imapx:D] I/O: 'D00037 BAD Command Argument Error. 11'
and:
(evolution:30280): evolution-mail-WARNING **: Failed to refresh folder
'srs@kth.
se: INBOX': Error syncing changes: Command Argument Error. 11

I have not requested to sync when working off-line!

___
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] Failed to refresh folder INBOX

2014-06-13 Thread Milan Crha
On Fri, 2014-06-13 at 12:16 +0200, Svante Signell wrote:
 [imapx:D] I/O: 'D00037 UID STORE 10496159 +FLAGS.SILENT (JUNK)'
 [imapx:D] I/O: 'D00037 BAD Command Argument Error. 11'

Hi,
it seems like you marked one of the messages as Junk, but the server
rejects to store this flag there. As you mentioned GMail, I suppose it's
the GMail server which rejected it. Probably the easiest would be to
remove local folder summary for that account. That is usually stored at
   ~/.cache/evolution/mail/some-account-uid/folders.db
Closing evolution and removing that file will lead to its recreate from
scratch the next evolution's start.
Hope it helps,
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] Failed to refresh folder INBOX/lost emails

2014-06-13 Thread Svante Signell
On Fri, 2014-06-13 at 16:02 +0200, Svante Signell wrote:
 On Fri, 2014-06-13 at 12:43 +0200, Milan Crha wrote:
  On Fri, 2014-06-13 at 12:16 +0200, Svante Signell wrote:
   [imapx:D] I/O: 'D00037 UID STORE 10496159 +FLAGS.SILENT (JUNK)'
   [imapx:D] I/O: 'D00037 BAD Command Argument Error. 11'
  
  Hi,
  it seems like you marked one of the messages as Junk, but the server
  rejects to store this flag there. As you mentioned GMail, I suppose it's
  the GMail server which rejected it. Probably the easiest would be to
  remove local folder summary for that account. That is usually stored at
 ~/.cache/evolution/mail/some-account-uid/folders.db
  Closing evolution and removing that file will lead to its recreate from
  scratch the next evolution's start.

Did not work for my gmail account. Still emails are lost! Another issue
is that deleted email just disappear regularly, even if I chose to keep
deleted emails until expunging the folder???

___
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] Failed to refresh folder INBOX/lost emails

2014-06-13 Thread Pete Biggs

 
 Did not work for my gmail account. Still emails are lost! Another issue
 is that deleted email just disappear regularly, even if I chose to keep
 deleted emails until expunging the folder???
 

The default for Gmail is to auto-expunge deleted messages (independently
of what you have set Evolution to do).  To change it in Gmail go to
Settings - Forwarding and POP/IMAP and the setting is in the IMAP
section.

But in general the IMAP bit of Gmail always feels like a bit of
cobbled-on after thought and some of the IMAP features do not map
cleanly on to Gmail - and deleting is one of those.  After all the
mantra of Gmail has always been Why delete it when you have so much
space

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] Recognizing Junk Header from ISP

2014-06-13 Thread Jonathan Ryshpan
On Thu, 2014-06-12 at 22:15 +0100, Patrick O'Callaghan wrote:
 On Thu, 2014-06-12 at 09:47 -0700, Jonathan Ryshpan wrote:
  I'm pleased to have a couple of replies to my posting, but still no
  answers to the question: how to recognize junk on the existence of a
  particular header without concern for its content.
 
 Define a filter (On Specific Header) with the action Set Status to Junk.

This appears to work; incoming messages are recognized correctly.

Oddly similar searches on mail already in Inbox don't work.  Quoting
from my earlier postings:

 ... when I try to select messages from Inbox which
 have a header line starting X-YahooFilteredBulk: by clicking
 Search-Advanced Search-Add Condition
 to get a choice box in which I enter:
 Specific Header  :  X-YahooFilteredBulk  :  Exists  :  Empty Field
 nothing is selected, despite the fact that many such messages are in Inbox

Alternately (editing the above for a new test)

 ... when I try to select messages from Inbox which
 have a header line starting X-YahooFilteredBulk: by clicking
 Search-Advanced Search-Add Condition
 to get a choice box in which I enter:
 Specific Header  :  X-YahooFilteredBulk  :  does not contain  : xx
 all messages are selected.

Thanks - 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] Recognizing Junk Header from ISP

2014-06-13 Thread G.W. Haywood

Hi there,

On Fri, 13 Jun 2014, Pete Biggs wrote:


The issue is that when you reject mail at smtp time you are
explicitly relying on the accuracy of an automated system to
determine what is, or is not, junk. ...


Why is this an issue?

--

73,
Ged.
___
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] Recognizing Junk Header from ISP

2014-06-13 Thread Zan Lynx
On 06/13/2014 01:10 PM, G.W. Haywood wrote:
 On Fri, 13 Jun 2014, Pete Biggs wrote:

 The issue is that when you reject mail at smtp time you are
 explicitly relying on the accuracy of an automated system to
 determine what is, or is not, junk. ...

 Why is this an issue?

Because the automated systems are bad at it?

I have to recover 5 or 6 messages every day from my spam trap. For some
reason a lot of sci-fi author's mailing list messages land in there.
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list