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
Hi again,
It looks like I'm loosing a lot of mails on another email account
(gmail). I can see them om my smartphone (and other boxes).
Help! What to do?
On Fri, 2014-06-13 at 08:42 +0200, Svante Signell wrote:
> Hi,
>
> Recently evolution shows the following message when accessing my IMAP
> ac
>
> 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 mo
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 roo
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
> >
>
>
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
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
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 messag
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.
>
> 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 Ev
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 c
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.
___
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 aut
13 matches
Mail list logo
