On Wed, 2021-04-28 at 14:44 +0200, Eric du Boislouveau via evolution-
list wrote:
> This option has disappeared !
> How can I find it again ?
Hi,
the option is still there, maybe you clicked "Always in current folder
only", since then the prompt goes away. The second option is there are
no
On Wed, 2021-04-28 at 14:44 +0200, Eric du Boislouveau via evolution-
list wrote:
> Hello,
> I have been using evolution for several years and when I was using
> the
> 'Mark as read' option on a folder that contains subfolders I had the
> choice
> to do this action on the subfolders.
> This option
Hello,
I have been using evolution for several years and when I was using the
'Mark as read' option on a folder that contains subfolders I had the choice
to do this action on the subfolders.
This option has disappeared !
How can I find it again ?
Thanks
---
On Tue, 2019-12-03 at 16:04 +, Douglas Summers via evolution-list
wrote:
> > $ flatpak run --cmd sh org.gnome.Evolution
>
> ...
> The command I had to run
> was different, though (Flatpak v1.4.3):
>
> flatpak run --command=sh org.gnome.Evolution
Hi,
I see, that's my fault, I didn
On Tue, 2019-12-03 at 10:13 +0100, Milan Crha via evolution-list wrote:
> On Mon, 2019-12-02 at 19:10 +, Douglas Summers via evolution-list
> wrote:
> > Yes. The option actually only appears if there are messages to be
> > marked read - and it sees the messages in the subfolders - but the
> > m
On Mon, 2019-12-02 at 19:10 +, Douglas Summers via evolution-list
wrote:
> Yes. The option actually only appears if there are messages to be
> marked read - and it sees the messages in the subfolders - but the
> messages beloew the selected folder are ignored. In the previous
> version, I would
On Mon, 2019-12-02 at 20:05 +0100, Andre Klapper wrote:
> On Mon, 2019-12-02 at 18:27 +, Douglas Summers via evolution-list
> wrote:
> > Running Evolution 3.34.2 (by Flathub.org)
> >
> > I recently upgraded to the aformentioned version as the stock
> > version
> > (3.28.5) that comes with Mint
On Mon, 2019-12-02 at 18:27 +, Douglas Summers via evolution-list
wrote:
> Running Evolution 3.34.2 (by Flathub.org)
>
> I recently upgraded to the aformentioned version as the stock version
> (3.28.5) that comes with Mint 19.2 was having issues with white-on-
> white text with dark themes. Now
Running Evolution 3.34.2 (by Flathub.org)
I recently upgraded to the aformentioned version as the stock version
(3.28.5) that comes with Mint 19.2 was having issues with white-on-
white text with dark themes. Now I'm having a minor issue when I try to
mark folder(s) and their subfolders as read; o
hello all,
I'm back in office and I noticed that Evolution version in Linux Mint 19.2
is only 3.28.5 so this is probably the issue - bug was already fixed, but
my Evolution is still too old.
Anyway upgrade is not so easy, 'cause Mint is made from LTS version of
Ubuntu - I tried update via flatpak
It's good to hear that there doesn't appear to be limit on the number
of conditions, thanks for that.
I has to confess to error. It seems some idiot has set up a separate
rule to move messages into that folder without marking them as read.
Unfortunately that would be me :-(
So no, there's no pro
On Tue, 2019-08-20 at 14:13 +0100, Pete Biggs wrote:
> Perhaps it's a bug. Perhaps no one has ever tried to have that many
> conditions before.
>
> Try splitting the conditions into two rules - or better, twelve rules
> (that's assuming the conditions are 'OR'). If it works with fewer
> condition
> > That feels like a lot of conditions,
>
> A lot of people send us sales junk :-/
Sure, but there are better ways of dealing with junk than manually
writing filters within Evolution for it. Both the spamfilters that
Evolution uses have blacklists - in other words everything from those
addres
> OK, so "Set Status Read" *is* working, just not for that particular
> rule.
It would seem so. I'd thought it was all of them, but perhaps not.
> That feels like a lot of conditions,
A lot of people send us sales junk :-/
> do you have other filter rules
> with that many? I don't know if the
>
> > I know you said "Mark as Read" doesn't work on its own, and I'm sorry
> > to press you on it, but are you sure? It certainly works for me and
> > others.
>
> In fact it seems that some of the rules are correctly marking mail as
> read, but certainly one particular one isn't. The delay in
Hi Pete,
Thanks for your reply.
> Both are also in the Evolution Help that comes with every copy of
> Evolution:
Fair point. Now accessing that way (the [forward] links aren't quite
the way you've said, but certainly close enough), I now see the 404 was
just due to a typo in the mail message.
On Sat, 2019-08-17 at 17:22 +0100, Mark @ StantonCentral wrote:
> Thanks for that Andre,
>
> The first link is very useful, I get a 404 with the second one.
Both are also in the Evolution Help that comes with every copy of
Evolution:
Help->Contents (or F1)
Mail Management -> Sorting and Organ
Thanks for that Andre,
The first link is very useful, I get a 404 with the second one.
The first link points out (in effect) that "mark as read" should be
applied before "move to folder", which I didn't know. I have, however,
changed my filters to mark the message read before moving it, and they
On Fri, 2019-08-16 at 21:31 +0200, spermosh via evolution-list wrote:
> for me it's not working either - none of my filters and any order change
> doesn't help. Somebody from this mailing try to help me with analysing
> debug log, but no error or warning there. It looks like Evolution simple
> igno
On Fri, 2019-08-16 at 21:45 +0200, spermosh via evolution-list wrote:
> specific version don't know, I'm not having my laptop right here - anyway
> it is last version in debian/ubuntu/mint repo...
Not useful information for most people on the list. Please cite the
exact version when you can (Help-
On Fri, 2019-08-16 at 19:57 +0100, Mark @ StantonCentral wrote:
> Is there some trick to getting this to work.
>
> I want to move some messages to a folder and then set them as read.
>
> The "Then" part of a few of my rule dialogS has "Move to folder" and
> then "Set Status Read", but the second pa
On 2019-08-16 at 21:45 +0200, spermosh via evolution-list wrote:
> specific version don't know, I'm not having my laptop right here -
> anyway it is last version in debian/ubuntu/mint repo...
Last version in Debian buster (stable) is 3.30.5-1.1
Last version in Debian stretch (oldstable) is 3.22.6-
specific version don't know, I'm not having my laptop right here - anyway
it is last version in debian/ubuntu/mint repo...
and yes, it's not working with only this one action...
Dne pá 16. 8. 2019 21:41 uživatel Pete Biggs napsal:
>
> Please. Please. Always say the version of Evolution you are
Please. Please. Always say the version of Evolution you are using -
things change, bugs get fixed.
On Fri, 2019-08-16 at 19:57 +0100, Mark @ StantonCentral wrote:
> Is there some trick to getting this to work.
>
> I want to move some messages to a folder and then set them as read.
>
> The "The
hello,
for me it's not working either - none of my filters and any order change
doesn't help. Somebody from this mailing try to help me with analysing
debug log, but no error or warning there. It looks like Evolution simple
ignore this action.
If anybody helps with this it will be nice.
regards,
Is there some trick to getting this to work.
I want to move some messages to a folder and then set them as read.
The "Then" part of a few of my rule dialogS has "Move to folder" and
then "Set Status Read", but the second part never works.
I tried changing the order, but that doesn't seem to do i
On Fri, 2019-07-19 at 11:46 +0200, Martin Monperrus wrote:
> - The "mark as read" command was never sent to the server (broken
> connection?)
> - A status is incorrectly cached somewhere.
Hi,
I'd bet on both above, but I've no idea how to reproduce it.
Feel free to file a bug at [1],
Hi all,
Here is a strange behavior. I use evolution-ews to connect to MS Exchange.
After using evolution-ews for some months, I connect to the Exchange Webmail
(aka OWA).
I notice that there are 30 messages marked as unread in OWA, from the past
months, while 1) I read
them all 2) I marked the
On Fri, 2019-03-15 at 14:24 +0100, spermosh wrote:
> version of Evolution is 3.28.5-ubuntu0.18.04.1
>
> Good point with order, I found myself that this could be important
> also, but I checked it and also I tried to change order of actions
> and it's still same...
What is your exact filter rule o
hi,
version of Evolution is 3.28.5-ubuntu0.18.04.1
Good point with order, I found myself that this could be important also,
but I checked it and also I tried to change order of actions and it's still
same...
Anyway I checked that link and there is also something about "stop
processing" action, b
Hi,
On Fri, 2019-03-15 at 10:10 +0100, spermosh via evolution-list wrote:
> I have work mail in Evolution with planty of filters, which move my
> incoming mails to different folders and should "mark mails as read"
> (set status to read), but this is not working at all. Mails are moved
> ok, but se
hello all,
I have this problem, maybe someone of you met with same issue and found
some solution:
I have work mail in Evolution with planty of filters, which move my
incoming mails to different folders and should "mark mails as read" (set
status to read), but this is not working at all. Mails are
Hallo,
I have an annoying effect with Evolution and AOL Imap Servers:
- Read messages turn back to be "unread" after restart of Evolution.
- Effect is independent of folder in use.
- If I create a response on the message or forward it to some one the
message remains "read" after restart of Evolut
Hi All.
For some odd reason messages marked as read aren't remembered after
closing/opening Evo. This only started happening after I moved my mail
from local maildir back to my remote Courier IMAP.
I'm on Evo 2.32.2 from Deb Wheezy.
--
Philippe LeCavalier
_
34 matches
Mail list logo
